Actions
Bug #89234
closed
$GLOBALS['BE_USER] is null causes Errors in FE
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-09-23
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
I have the same error as described in issue #85310, but with an up-to-date 9.5.9 (and with 9.5.8 before).
Samples from the logs:
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:50:50 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/research/topics - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:50:59 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/staff/people/xxx-xxx - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:51:00 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/staff/people/zzz-xxx - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:51:02 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/staff/people/xxx-yyy - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:51:02 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/staff/people/aaa-bbb - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:51:10 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/staff/people/ccc-ddd - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:51:11 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/staff/people/eee-fff - {"TYPO3_MODE":"FE","exception":{}}
typo3_f2db1a8af4.log:Mon, 23 Sep 2019 20:51:19 +0200 [CRITICAL] request="" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getModuleData() on null | Error thrown in file /opt/typo3/typo3_src-9.5.9/typo3/sysext/backend/Classes/Utility/BackendUtility.php in line 3180. Requested URL: https://example.com/research/topics/storage - {"TYPO3_MODE":"FE","exception":{}}
How can I debug that?
Updated by bitfire it services over 4 years ago
The error (which renders the page as 500 internal server error) randomly happens from time to time when a frontend URL is requested, but most requests just work.
It seems that all problematic pages contain my own Extbase/Fluid extension. However, it does nothing special, just some models and controllers/views for them.
Updated by bitfire it services over 4 years ago
Found it. I was using Backend\ViewHelper in a public template. No idea why it only broke some requests....
Updated by Georg Ringer over 4 years ago
- Status changed from New to Rejected
closing it as it seems that you find the problem + solution.
Updated by bitfire it services over 4 years ago
Yes, sorry for the noise.
Maybe it can be helpful for somebody else with the same error message: Don't use backend ViewHelpers (be:module) in frontend templates!
Actions