Bug #99465
closed
Accessing site configuration via TypoScript getData triggers a warning when configuration option does not exist
100%
Description
The following stdWrap code currently triggers a log warning:
if.isTrue.data = site:settings.optional.property
My expectation is, that this "incident" should rather be logged at least as notice instead,
since the value accessed could intentionally be an optional value.
Updated by Gerrit Code Review over 1 year ago
- Status changed from New 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/+/77262
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/+/77220
Updated by Helmut Hummel over 1 year ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset da32f45cf6fe2eab7a0b3d75ef370ec5735e811d.
Updated by Gerrit Code Review over 1 year ago
- Status changed from Resolved to Under Review
Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77289
Updated by Gerrit Code Review over 1 year ago
Patch set 2 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77289
Updated by Andreas Kiessling over 1 year ago
- Related to Bug #98053: TypoScript: getData spams logfile if value in site config is missing added
Updated by Helmut Hummel over 1 year ago
- Status changed from Under Review to Resolved
Applied in changeset b8826742391a2ba3abc7e96375708dfb0e6a8ed3.
Updated by