Bug #59969
closed
Typo3 6.2.3
0%
Description
After Installation from Typo3 6.2.3 the followin Error is displayed in BE as well as in FE:
Warning: Uncaught exception 'TYPO3\CMS\Core\Error\Exception' with message 'PHP Warning: require_once(PATH_t3libinterfaces/interface.t3lib_singleton.php): failed to open stream: No such file or directory in typo3conf/ext/cdnfiles/class.tx_cdnfiles_specialconfiguration.php line 6' in typo3_src-6.2.3/typo3/sysext/core/Classes/Error/ErrorHandler.php:111 Stack trace: #0 typo3conf/ext/cdnfiles/class.tx_cdnfiles_specialconfiguration.php(6): TYPO3\CMS\Core\Error\ErrorHandler->handleError(2, 'require_once(PA...', '/home/www/web19...', 6, Array) #1 typo3conf/ext/cdnfiles/class.tx_cdnfiles_specialconfiguration.php(6): require_once() #2 typo3conf/ext/cdnfiles/class.tx_cdnfiles.php(6): require_once('/home/www/web19...') #3 typo3_src-6.2.3/typo3/sysext/core/Classes/Utility/GeneralUtility.php(4671): require_once('/home/www/web19...') #4 typo3_src- in typo3_src-6.2.3/typo3/sysext/core/Classes/Error/ErrorHandler.php on line 111
Fatal error: main(): Failed opening required 'PATH_t3libinterfaces/interface.t3lib_singleton.php' (include_path='typo3/contrib/pear/:/usr/local/php55/lib/php:.') in typo3conf/ext/cdnfiles/class.tx_cdnfiles_specialconfiguration.php on line 6
No chance to see the Website and also not possible to enter into the BE Module. Except installtool works fine.
How can i fix this problem?
Could it be from a broken Extension that I had do deinstall?
Updated by Markus Klein almost 10 years ago
- Category deleted (
Backend API) - Status changed from New to Needs Feedback
- Priority changed from Must have to Should have
Hi, you're already answering this yourself: Have a look at the paths you see in the message.
typo3conf/ext/cdnfiles/
Your faulty extension is "cdnfiles".
Please use the forum or the mailing lists for questions like these, as this is the bug tracker, which we do not use for support questions.
Thank you.
Updated by Martin Kutschker almost 10 years ago
The cause of the problem is the extension, right.
But why is the exception uncaught? IMHO 6.2.x is not very forgiving when it comes to errors caused by extensions.
Updated by Anja Leichsenring over 9 years ago
- Status changed from Needs Feedback to Closed