Bug #39917
closed
Connection Problem Sorry, but an error occurred while connecting to the server. Please check your network connection.
0%
Description
After updating to 4.7.4 we are receiving this error message.
calling the domain with a simple .html file works fine
The error log says:
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: PHP Fatal error: Uncaught exception 'BadFunctionCallException' with message '*TYPO3 Fatal Error: Extension "aloha" was NOT found!*' in /var/t3/typo3_src-4.7.4/t3lib/class.t3lib_extmgm.php:104, referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: Stack trace:, referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #0 /var/t3/typo3_src-4.7.4/t3lib/class.t3lib_autoloader.php(171): t3lib_extMgm::extPath('aloha', 'ext_autoload.ph...'), referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #1 /var/t3/typo3_src-4.7.4/t3lib/class.t3lib_autoloader.php(121): t3lib_autoloader::createCoreAndExtensionRegistry(), referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #2 /var/t3/typo3_src-4.7.4/t3lib/class.t3lib_autoloader.php(69): t3lib_autoloader::loadCoreAndExtensionRegistry(), referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #3 /var/t3/typo3_src-4.7.4/t3lib/config_default.php(799): t3lib_autoloader::registerAutoloader(), referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #4 /var/t3/typo3_src-4.7.4/typo3/init.php(201): require('/var/t3/typo3...'), referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #5 /var/t3/typo3_src-4.7.4/typo3/ajax.php(55): require('/var/t3/typo3...'), referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: #6 {main}, referer: http://domain/typo3/backend.php
[Sat Aug 18 10:25:10 2012] [warn] [client 1.0.236.245] mod_fcgid: stderr: thrown in /var/t3/typo3_src-4.7.4/t3lib/class.t3lib_extmgm.php on line 104, referer: http://domain/typo3/backend.php
-----
Why aloha now required in 4.7.4 as we never used it before nor had it installed?
It seems to be missing in core either!
This error message is very very strange and actually does not seem to point out the real problem or a solution for the connectivity problem!
Andi
Updated by Michael Stucki over 12 years ago
- Status changed from New to Needs Feedback
Just to make sure that this is not caused by other changes: Can you please downgrade to 4.3.7, clear caches, and try to reproduce the behaviour?
If you are familiar with Git, it might also be interesting to find out using git-bisect which change is causing this problem. You can check out TYPO3_4-7-4 and then make a comparison with all changes up to TYPO3_4-7-3 (or just the last version that was working for you).
Git-Bisect is nicely explained at the following page: http://alblue.bandlem.com/2011/07/git-tip-of-week-git-bisect.html
Updated by Andreas Becker (Andi) over 12 years ago
Hi Michael
is this a joke or an april fools - we got august ;-) - or a TYPO... "Can you please downgrade to 4.3.7, clear caches, and try to reproduce the behaviour?"
I am not sure since when we had last time used 4.3.7 but this is a couple of years ago as all our customer sites get regularly updated and maintained.
Everything worked until 4.7.3 beside the fact that the core team had thrown out parts which are needed by templavoila. But meanwhile those parts are there and we upgraded to 4.7.4 and get again those error messages. The most interesting part is actually that we don't have aloha installed nor we know where it would be available. So why is an error message poping up about aloha when it is even available or integrated in core - or is it a hidden feature?
Updated by Michael Stucki over 12 years ago
Of course it was a typo! I swapped 4-7-3 with 4-3-7.
Also let me point out that I'm not recommending to downgrade to an old version. I'm only trying to give you assistance on how to find the change that introduced the problem.
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.