Actions
Bug #95211
closedDebugUtility results in Oops, an error occurred!
Status:
Closed
Priority:
Should have
Assignee:
Category:
Content Rendering
Target version:
Start date:
2021-09-13
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
11
PHP Version:
8.0
Tags:
Complexity:
no-brainer
Is Regression:
Sprint Focus:
Description
Hello Core Team,
I have installed TYPO3 10.5.0-dev at Commit e0aa9faa4add5414951c20a733f5a32d4f43fc36. Sometimes I get an "Oops, an error occurred!" when showing cached content in frontend. The error in log is:
Oops, an error occurred! Code: 20210913191958a399196e- Exception: PHP Warning: Undefined array key "line" in /var/www/html/TYPO3.CMS/typo3/sysext/core/Classes/Utility/DebugUtility.php line 160
I have created a backtrace for you in frontend. Last part is:
array(4) { ["function"]=> string(6) "render" ["class"]=> string(60) "TYPO3Fluid\Fluid\Core\ViewHelper\AbstractConditionViewHelper" ["type"]=> string(2) "->" ["args"]=> array(0) { } }
As you see, there is no array key "line". IMO access to this key should be checked first.
You don't get the error in production mode.
You don't get the error if you set config.contentObjectExceptionHandler = 0
Stefan
Updated by Gerrit Code Review about 3 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/71079
Updated by Stefan Froemken about 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 22da2a2277bf55f324b0e3ccd72fcca8ed3eaa00.
Actions