[TYPO3-english] is TYPO3 moving away from global extensions?

Andreas Becker ab.becker at web.de
Thu Mar 29 15:31:49 CEST 2012

Actually we always changed the "ext" folder into a symlink to a global
folder where we store all our stuff which should be available globally i.e.
also lots od l10n stuff.

So our setting was:

global/conf/configuration which was holding all general settings for the
sites on one server i.e. gm oder image magick or many stuff you have to do
otherwise over and over again per site
global/conf/ext which was holding all global extensions
global/conf/l10n which is holding all language translations on one server
global/file/demo which holdes several demo objects which are available on
all the sites for content creation like demo.pdf or  a .doc or images audi
video etc
global/sources/typo3_src-1.2.3/typo3/[ext] which is a symlink to an
external folder - in our case /global/conf/ext

site/typo3conf/[l10n] gets symlinked in most cases to global/conf/l10n
site/fileadmin/[demo] gets symlinked to global/file/demo

if there was a db change or a dependency change we had to update all sites
and actually have taken this specific extension out of the global folder
also for future updates.

This worked wonderful for years already and is quite easy to maintain.

But we changed already last year as more on more threads were mentioning
that the ext folder no more get supported. And the biggest problem at all
is meanwhile that those who run the site get not asked or informed long
time before about those changes what core developers are actually doing.
Suddenly your sites will be gone - relax sabei sabei and drink a coffee. So
better don't trust and change it now so you are on safer ground when it is
gone. - and your customers too!


On Thu, Mar 29, 2012 at 8:11 PM, Sergey Alexandrov <serg at alexandrov.us>wrote:

> Philipp,
> What's the difference between having a symlink and global extension
> directory installation then?
> We also have 100+ websites running off the same source. "Global" extension
> installation has some advantages and ext. maintenance is the one of them.
> How do you update/bugfix an extension if there are hundreds of them
> installed locally? So, you'll have to put ext. in  the same folder for
> diff. sites, right? And create symlink, right?
> But we already have this functionality as "global" ext. folder! Why jump
> through the loop?
> Thank you,
> Sergey
> On 3/29/2012 8:32 AM, Philipp Gampe wrote:
>>  I do not see a single point in having global extensions that would
>> justify the many problems you get with this approach. Best regards
> ______________________________**_________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-**english<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english>

More information about the TYPO3-english mailing list