Bug #86257
closedInvalid TypoScript condition expressions breaks TYPO3
100%
Description
The symfony expression language has no type check, which results in PHP Warnings in case the in
expression is used without an array.
example:
[1 in "foo"]
will throw a PHP Warning: in_array() expects parameter 2 to be array
This case should be handled by the core in two different ways:
1) In Frontend a InvalidTypoScriptConditionException should be thrown (if strictSyntax feature toggle is enabled)
2) In Frontend silent catch this error and log it (if strictSyntax feature toggle is disabled)
3) In Backend silent catch this error and log it, but never break the backend.
Updated by Gerrit Code Review over 6 years ago
- Status changed from In Progress 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/58280
Updated by Gerrit Code Review over 6 years ago
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/58280
Updated by Gerrit Code Review over 6 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58280
Updated by Gerrit Code Review over 6 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58280
Updated by Frank Nägler over 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset b22bb42c7b5865b9dd5e8e6f61129107522038e3.