TYPO3 Core

Patch set 2 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/+/61315

Frank Naegler wrote:

If you build your condition like this you don't have an issue:

[...]

The first part will create a notice, but an exception will not occur.

Thank you! This is working indeed – but to me it isn’t quite logical: why doesn’t the way I tried ([request.getQueryParams()['tx_news_pi1']['news']]) work as well, when with dropping the ['news'] a proper is_defined is being performed? Besides I wasn’t able to find documentation on that behaviour and the returned exception anywhere.

I still believe the is_defined validation should be done automatically, considering Typoscript should be simplified compared to a proper programming language.

Find my take on this in #89176

The current best practice (as documented) is to use traverse in conditions with array elements (which might be uninitialized):

(also in the future, as this may change, please look at the documentation page for your TYPO3 version, use version switcher: https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Conditions/Index.html)

# before:
[page["uid"] == 2]

# after
[traverse(page, "uid") == 2]

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

# before
-[request.getQueryParams()['tx_news_pi1'] && request.getQueryParams() ['tx_news_pi1']['news'] > 0]

# after
+[traverse(request.getQueryParams(), 'tx_news_pi1/news') > 0]

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