Bug #62741
closed
Fatal Error: ClassLoader.php on line 182 when updating any extension in TYPO3 6.2.6
0%
Description
Every time I update an extension in TYPO3 6.2.6 this will result in the following fatal error:
Warning: require_once(/xx/xx/xx/public_html/typo3conf/ext/news/Classes/Utility/Compatibility.php): failed to open stream: No such file or directory in /xx/xx/xx/public_html/typo3_src-6.2.6/typo3/sysext/core/Classes/Core/ClassLoader.php on line 182 Fatal error: require_once(): Failed opening required '/xx/xx/xx/public_html/typo3conf/ext/news/Classes/Utility/Compatibility.php' (include_path='/xx/xx/xx/public_html/typo3/contrib/pear/:.:/usr/local/lib/php') in /xx/xx/xx/public_html/typo3_src-6.2.6/typo3/sysext/core/Classes/Core/ClassLoader.php on line 182
What did I do?
Delete all cache > go to Extension manager > click on update icon > blue popup screen reports the extension has been updated. After that both BE and FE will output the fatal error.
The only way to get rid of it is to manually delete all files in the directory cache_core.
If I then try to update another extension, TYPO3 will generate the same error.
Also tried to delete all files in the directory cache_core and then update the extension, but this will result in the same fatal error. So it seems that somehow TYPO3 generates wrong cache files, or that the are not updated after the update of the extension.
Enabling or disabling an extension will not trigger the error.
Updated by Nicole Cordes over 9 years ago
- Status changed from New to Needs Feedback
Can you tell me which version of news you tried to update?
Updated by Muriel le Pair over 9 years ago
I updated the news extension to version 3.0.1.
But the fatal error occurs every time I update an extension with the fatal error referring to the 6.2.6/typo3/sysext/core/Classes/Core/ClassLoader.php and some other file of the updated extension.
To make it even stranger:
I made an exact copy of the entire site (including all files, db, localconfig) on the same server, the odd thing is that the error does not occur in the mirror site.
What led me to believe that somehow the error is triggered by being the first 6.2 installation on the server..
Updated by Benni Mack over 9 years ago
Could you please try again with 6.2.14 or CMS7? We reworked most of the class loader loading complexity.
Updated by Riccardo De Contardi about 9 years ago
- Status changed from Needs Feedback to Closed
There has been no feedback within the last 90 days;
The issue is resolved on version 7, and should be also for 6.2.15, so I think it can be closed for now.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.