Bug #75728
closed
Class not found in various extensions when Clearing all Caches in the install tool
0%
Description
I have a strange issue on my production (linux) server. If go to Install Tool and clear all caches, the following error appears:
Detected Fatal Error Class 'GeorgRinger\News\Utility\EmConfiguration' not found in /var/www/dev/htdocs/typo3conf/ext/news/ext_localconf.php on line 6
This happens with different extensions e.g.: powermail, news, etc.
When deactivating them all, the error no longer appears. The weird thing is, on my development server (windows), everything works fine - no error when clearing all caches in the install tool.
I updated to TYPO3 7.6.5 to check if the issue got resolved because of this very similar issue:
https://forge.typo3.org/issues/73520
But no luck for me. Error persists.
Files
Updated by 
Updated by Nicole Cordes about 8 years ago
- Status changed from New to Needs Feedback
Can you please attach the files inside typo3temp/autoload to this ticket after you cleared the cache and the error occurred.
Updated by Thomas Ernst about 8 years ago
- File autoload_classaliasmap.php autoload_classaliasmap.php added
- File autoload_classmap.php autoload_classmap.php added
- File autoload_psr4.php autoload_psr4.php added
I have the same issue here. (Typo3 7.6.6, PHP 5.5.14).
I checked, but there is no folder typo3temp/autoload. I only have typo3temp/autoload-tests. Files from this folder are attached
Updated by Nicole Cordes almost 8 years ago
I have tried 7.6.9, 7.6.10-dev and the current master. All fine here - I cannot reproduce the issue (anymore). Do you have some manual changes of the TypoScript of css_styled_content or fluid_styled_content?
Can you provide any steps to reproduce the issue?
Updated by Nicole Cordes almost 8 years ago
Thomas Ernst wrote:
I checked, but there is no folder typo3temp/autoload. I only have typo3temp/autoload-tests. Files from this folder are attached
These are autoload files which are generated and used when running the tests. They are not used in production/development context
Updated by Markus Kobligk almost 8 years ago
Switching the application context from "testing" to either development or production solved this problem for us.
Updated by Helmut Hummel almost 8 years ago
- Status changed from Needs Feedback to Rejected
Markus Kobligk wrote:
Switching the application context from "testing" to either development or production solved this problem for us.
Application context "Testing" is only meant for testing TYPO3. It is *NOT* meant for running your project.
Please use Development/Testing or Production/Testing instead
Updated by Peter Benke over 7 years ago
Maybe, it helps anybody:
I had the same issue inside a vagrant box (cent os) running on windows 10.
I tried everything described here: https://forge.typo3.org/issues/75728, but nothing helped.
Restarting the vagrantbox did not help.
I had to reboot windows to solve this,... no further comment.