Bug #21196
closed
autoloaders registered by extensions slow down the core autoloader
0%
Description
Problem:
If an extension registers an autoloader by itself this slows down the core autoloader because extension autoloaders are registered first in the autoloading stack. Each autoloader trigger from the core will first hit the registered extension autoloaders before it it handled by the core autoloader.
Solution:
Move the core autoloader registration before the extension loading.
(issue imported from #M12133)
Files
Updated by Rupert Germann about 15 years ago
besides the mentioned autoloader problem, there's another issue that would be fixed by this patch, too:
If an extension executes code in its ext_localconf.php (e.g. the paymentlib* extension do this) the function t3lib_div::xml2array() makes problems because since 4.3.0 this function is cached. The functions used for caching are getHash() and storeHash() from class t3lib_pageSelect. This class was not needed for this before 4.3 and it is not available in 4.3 because the autoloader is registered after loading the extension localconfs.