Bug #37413
BE Module not accessible
| Status: | Closed | Start date: | 2012-05-23 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 100% |
|
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
After the latest minor update from 2.3.2 to 2.3.3 I lost my BE module access. The content frame stays grey.
in apache error.log I get these two errors:
PHP Notice: Undefined variable: LANG in /var/www/typo3conf/ext/t3jquery/mod1/index.php on line 32, referer: http://www..de/typo3/backend.php
PHP Fatal error: Call to a member function includeLLFile() on a non-object in /var/www/typo3conf/ext/t3jquery/mod1/index.php on line 32, referer: http://www..de/typo3/backend.php
Using Typo3 4.5.16LTS
Related issues
History
#1 Updated by Anonymous about 3 years ago
- Status changed from New to Needs Feedback
- Assigned To set to Kai Kretschmann
Have you cleared typo3-cache?
#2 Updated by Kai Kretschmann about 3 years ago
Yes I did, with no difference.
But I found the guilty part, for anyone with the same symptom:
I restarted the apache process to clean up the opcode cache xcache and now it works. I normaly restart the apache when upgrading typo3 versions, it was never needed when updating extensions. No idea what made it so special this time.
Sorry, ticket can be closed als category error-sitting-in-front-of-screen :-)
#3 Updated by Anonymous about 3 years ago
- Status changed from Needs Feedback to Closed
- Assigned To changed from Kai Kretschmann to Anonymous
- % Done changed from 0 to 100
#4 Updated by Henrik Ziegenhain about 3 years ago
For all "Googlers"
I had the same problem - clearing caches from the Backend did not solve the problem.
Deleting all temp_CACHED_* files in /typo3conf/ solved the issue.
#5 Updated by Felix Nagel about 3 years ago
Same problem here after updating to v2.3.4 and TYPO 4.7. Manual clean up as Henrik mentioned did not work for me. BE module is not usable atm.
This problem seems similar to this core bug #20351
#6 Updated by Anonymous about 3 years ago
Fixed it in 2.3.5
#7 Updated by Felix Nagel over 2 years ago
If the Problem persists: removing and reinstalling did the trick for me.