[TYPO3-core] RFC #12067: Remove ext_autoload.php files for extensions using Extbase naming convention

[Steffen Kamper]

Hi,

Rupert Germann schrieb:
> Bastian Waidelich schrieb:
>> Right, I remember the discussion. But I've just checked and actually 
>> ext_tables-files are included _after_ (init.php:363) the 
>> t3lib_autoloader has been registered (init.php:184) (btw: 
>> ext_localconf-files will be loaded _earlier_).
>> And because spl_autoloader works like a queue (FIFO) rather than a 
>> stack, the TYPO3 autoloader will be fired first!
> 
> that's true for the BackEnd. Are we talking about backend extensions here?
> 
>> So, if nobody objects, I'd move the autoloader registration from the 
>> dispatcher to ext_tables and get rid of the huge ext_autoload.php 
>> files in extbase, fluid & blog_example.
> 
> that would only help for the BE.
> 

that's indeed a real trap. For me it's very hard to configure right, as 
ext_tables is BE, ext_localconf FE, where to store information for both? 
Only chance is to include an ext_common from both, or any better suggestion?

vg Steffen