TYPO3 Core

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

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

This is a known issue. You should take the effort to harden your TypoScript using the traverse() workaround to mitigate these errors.

So you should replace

[(request.getQueryParams()['newsletter']) && (request.getQueryParams()['newsletter']) > 0]

with

[(traverse(request.getQueryParams(), 'newsletter')) && (traverse(request.getQueryParams(), 'newsletter')) > 0]

Kudos to the TYPO3 Documentation Team, which startet to use traverse on several TypoScript options to cover this when simply copy&paste options, also the travese option has been around and documented quite a while, see for example:

https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Conditions/Index.html#page
https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Conditions/Index.html#traverse
https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Conditions/Index.html#request

Stefan Bürk wrote in #note-6:

This is a known issue. You should take the effort to harden your TypoScript using the traverse() workaround to mitigate these errors.

This is an option, I agree. But it is also only a workaround. And blow up the conditions.
The example above is a simple example, but there are more complex conditions that blow up much more.
Userfriendly looks different to me ;)

Frank Nägler wrote in #note-7:

Stefan Bürk wrote in #note-6:

This is a known issue. You should take the effort to harden your TypoScript using the traverse() workaround to mitigate these errors.

This is an option, I agree. But it is also only a workaround. And blow up the conditions.
The example above is a simple example, but there are more complex conditions that blow up much more.
Userfriendly looks different to me ;)

I agree. We have many different conditions and it is a lot of work which are blowing up our log files.
Maybe we would rewrite them all, but it would be better - for newer user of TYPO3 - to get a them working without blowing up the logs.

Well, this is an issue of the underlying library and how it works in combination with PHP.
There were issues on symfony itself where they don't like to "fix" that as that's how it is supposed to work. That's why TYPO3 added the extra function.

I also thought it would be cool to "fix" that, but I changed my mind. It's the same as if you'd write the same in PHP. You also won't complain PHP to become more strict, but you'll fix the issue within your code and e.g. add `??` operator.

I understand that re writing a lot of conditions the same way is stupid. But rector can already do that. In fact it already migrates old condition syntax to new one. Should be possible to add the check and traverse re write to TYPO3 rector to do the job for everyone.

Same problem for me typo3 11.5.17 and php 8 and 8.1. strange thing is, if I put setup typoscript to database instead of file, there is no warning. activating same setup in file inklude I get php warning ...!?

Can we close this as duplicate of #95781.

(Most of the other related issues listed in #95781 are closed. I think it would be easier to handle in one issue)

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