TYPO3 Core

Is this triggered by extbase BackendConfigurationManager? Could you provide the full backtrace? We may need to adapt extbase in this case a bit.

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/+/78622

Hi Alex,

this is most probably due to the changes in #100237. Those changes were necessary after cleaning up the whole expression language implementation in #100047. You have to adjust your TypoScript to check for TSFE being available. Previously, the whole condition evaluated to FALSE if TSFE was not available, e.g. in backend context. Since #100237 however, the function (getTSFE()) itself returns FALSE in case TSFE is not available. To prevent the corresponding exception, the following check has to be used: [getTSFE() && getTSFE().type 1562349004].

I now created a patch which aligns the behaviour of getTSFE() to return NULL instead of FALSE. This allows to also use the null-safe operator ?. You will then be able to use [getTSFE()?.type 1562349004]. This is in line with the other expresion functions, like site or siteLanguage.

I hope this helps and I'm sorry for the inconveniences.

Best, Oli

Patch set 3 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/+/78622

Patch set 4 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/+/78622

Patch set 5 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/+/78622

Thx for digging into it.

I think a change to:

[getTSFE() && getTSFE().type == 1562349004]
...

Should do it for now