Bug #58915
closed
Fatal Error after upadate to 6.2.2: Call to a member function isEnvironmentInFrontendMode() on a non-object
0%
Description
After updating from 6.1.7 to 6.2.2 most backend modules wont work with the exception:
Fatal error: Call to a member function isEnvironmentInFrontendMode() on a non-object in /var/www/typo3_src-6.2.2/typo3/sysext/extbase/Classes/Configuration/ConfigurationManager.php on line 68
Pretty basic installation that uses only TemplayVoila and two own plugins (both work on a different installation of 6.2.2).
Install wizard steps all completed successfully and caches are cleared (also the cache files in typo3conf).
Updated by Markus Klein over 10 years ago
- Status changed from New to Needs Feedback
I'm not sure if TemplaVoila is 6.2 compatible. I guess this extension causes your problems. Try to uninstall it and check if it works then.
Updated by Klaus Hinum over 10 years ago
looks like it was a problem of the url i logged in.
When logging in with
http://test.com/typo3
I got the error, when using http://www.test.com/typo3 it works
Updated by Markus Klein over 10 years ago
So this can be closed as this seems to be a server issue then, right?
Updated by Klaus Hinum over 10 years ago
well i still see it as a bug, as the backend is not working when logging in with another url (without the www.). guess that could be a problem if your backend e.g. runs on backend.test.com and the frontend on www.test.com
Updated by Markus Klein over 10 years ago
This is a configuration issue on your server, as I'm doing this all the time.
Some editors enter the BE via www. others without. No problems at all.
Updated by Klaus Hinum over 10 years ago
was no issue before with 6.1, so what can that be?
Updated by Markus Klein over 10 years ago
No idea, sorry. Maybe update to 6.2.3 first and see if it got fixed there.
Updated by Klaus Hinum over 10 years ago
hah, you are right 6.2.3 seems to have fixed it (or the Clear PHP opcode cache, updated refindex, redone upgrade wizard).
Updated by Markus Klein over 10 years ago
- Status changed from Needs Feedback to Closed
Btw. 6.2.3 was a sec release, you should have updated much earlier. ;-)
Updated by Vlatko Šurlan over 10 years ago
Found one way to cause this error. User that has no permissions to access any module. It happened to me when changing user from admin to nonadmin be user. After that the new user had no modules enabled in Backend users -> Edit -> Access Rights.
Updated by Christoph Lehmann almost 10 years ago
I had the same error after Update from 6.1.12 to 6.2.9. Clearing all caches in the Install-Tool helped me