[TYPO3-core] [TYPO3-dev] Poll: Should we keep supporting "global extensions"?

Benjamin Mack benni at typo3.org
Mon Dec 8 11:21:42 CET 2014


Hey everybody,

today I need your opinion, so please be so kind to hit reply with a
quick response.

As for the introduction:

TYPO3 features the functionality of "system extensions" (located under
"typo3/sysext/") - extensions that come with the Core. Then, there are
"global" extensions, which can be put under "typo3/ext/". This is useful
if you have a third-party-extension that you want to distribute to
multiple installations (like e.g. tt_news back then in 3.6) that *you*
download and install there. This feature is really only helpful if you
have 1 TYPO3 source, that multiple installations are using, but comes
with the price that you need to copy all your global extensions when
updating TYPO3 from 4.5.12 to 4.5.13.
Then you have the "local" extensions under "typo3conf/ext/", - your
installation-specific extensions, which I guess, all of you are using.

We are currently think of dropping the "global" extension concept which
we think (but don't know for sure) is rarely used since ages, and also
pretty much unmaintained, as we consider this feature with all the
composer-bells-and-whistles today not useful for keeping.

So as a roundup:

 * System extensions: typo3/sysext/
 * Your global extensions: typo3/ext/
 * Your local extensions: typo3conf/ext/

What I would like to know is simple:

  Are you using the "global extension" feature currently?

All of you with Gerrit access, feel free to vote the pending patch as well:

  https://review.typo3.org/#/c/34552/

Thanks for your time!

All the best,
Benni


More information about the TYPO3-team-core mailing list