Bug #98611
closed
Warning if bodyTagCObject is set with another referenced TS object in php8.1 instances
100%
Description
After changing php version to 8.1 in our TYPO3 11 instance we have an error in frontend.
Undefined array key "bodyTagCObject."
Error occurs if we are using an referenced TyppoScript object for "bodyTagCObject".
Example:
u10n.bodyTag = TEXT
u10n.bodyTag.value = <body class="test">
page.bodyTagCObject =< u10n.bodyTag
Normally the error (E_WARNING) is not visible in frontend, but it will be logged by TYPO3 if logLevel allow logging of warnings.
Some things must be configured in the environment to show this error message.
We are using following configurations for our website:
- PHP error_reporting is set to 30466
- we are using whoops exceptionhandler in our composer based environment
- whoops configuration disables
$GLOBALS['TYPO3_CONF_VARS']['SYS']['debugExceptionHandler']and$GLOBALS['TYPO3_CONF_VARS']['SYS']['errorHandler'] - and of course debug settings in TYPO3 are set to true
Problem is in TYPO3\CMS\Frontend\Http\RequestHandler line:805(branch 11.5) line:832(branch main). It is one of the problems currently occurring in several places because of using php8.1.
Updated by Karsten Nowak (undkonsorten) over 1 year ago
I have just seen, bug is already fixed 2 days ago ;-). CommitHash: f754f7c776d2812333a8b38cccd1888bceaf2f3c
Related issue: #98582
Issue can be closed.
Updated by Stefan Bürk over 1 year ago
Are you sure, that it is really related to the other issue ? For me it sounds like different things.
I do not know that whoops stuff .. never had a need to mess arround here. Should it not display/output a stacktrace too ? Or at least configurable ?
The core will display a stack trace if in debug mode (not live mode) .. that would be nice. Or at least the corresponding entry from the log file.
However, you provided a TypoScript snipped .. not tried yet, but maybe be enough to reproduce and get the stack trace ourself.
Updated by Stefan Bürk over 1 year ago
- Status changed from New to Needs Feedback
Updated by Gerrit Code Review over 1 year ago
- Status changed from Needs Feedback to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76112
Updated by Karsten Nowak (undkonsorten) over 1 year ago
Sorry for the mistake. Bug was not resolved and the issue 98582 is not related to this. I pushed the fix now. Can be reviewed.
Updated by Gerrit Code Review over 1 year ago
Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76112
Updated by Gerrit Code Review over 1 year ago
Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76065
Updated by Karsten Nowak (undkonsorten) over 1 year ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 4473868351ceb6fbdbf15fae33977310b38e7a61.
Updated by