Bug #28266
closed
When an extension is installed or removed, the autoloader cache must be flushed
0%
Description
Problem:
If an extension is installed during a request, the autoloader cache must be removed.
If not, it may be that classes are not found because they are missing in the autoloader registry
Solution:
Remove the autoloader cache if t3lib_extmgm::removeCacheFiles() is called
Steps to reproduce:
Use a plain dummy package.
Call the 123 install wizard.
You'll get "PHP Fatal error: Class 'tx_dbal_querycache' not found", because dbal activates itself, but the caches are not flushed and 'tx_dbal_querycache' is not present in the autoloader registry.
Files
Updated by Helmut Hummel almost 13 years ago
- File clearautoloadcache.diff clearautoloadcache.diff added
My solution is a bit ugly, because I add a dependency to the cache identifier of the autoloader to another class, but at least it fixes the issue for now.
Probably Christian has a better idea how this can be solved.
Updated by Marc Bastian Heinrichs almost 13 years ago
Can confirm this issue - had this just a minute before.
Updated by Christian Kuhn almost 13 years ago
@Helmut: The issue was not solved for you with https://review.typo3.org/#change,3319 ? This is issue #28187
Same has been done for em with issue #28219
Updated by Christian Kuhn almost 13 years ago
If testing again make sure to checkout master of the dbal submodule, since submodule pointers currently point to a version where the patch is not applied, yet.
Updated by Helmut Hummel almost 13 years ago
- Status changed from New to Closed
Thanks Christian. After updating DBAL like you suggested, this is of course solved.
Updated by Marc Bastian Heinrichs almost 13 years ago
After checking the used dbal branch and checkout master I can confirm that its solved.
Updated by Ernesto Baschny almost 11 years ago
- Target version deleted (
4.6.0-beta1)