Skip to content

Conversation

brotkrueml
Copy link
Contributor

Setting a TypoScript option to false does not really disable the option, as it is casted to bool later on. true casts to true, which is correct, but for consistency reasons, we should always use 0 and 1 in TypoScript for boolean values.

See also: https://docs.typo3.org/m/typo3/reference-typoscript/12.4/en-us/DataTypes/Index.html#boolean

Releases: main, 12.4

Setting a TypoScript option to `false` does not really disable the
option as it is casted to bool later on. `true` casts to true, which
is correct, but for consistency reasons, we should always use
`0` and `1` in TypoScript for boolean values.

See: https://docs.typo3.org/m/typo3/reference-typoscript/12.4/en-us/DataTypes/Index.html#boolean

Releases: main, 12.4
@brotkrueml brotkrueml self-assigned this Sep 5, 2024
Copy link
Contributor

@froemken froemken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. It's looking a little bit confusing because of boolean and 0 and 1, but hey...it's TypoScript ;-)

@garvinhicking garvinhicking merged commit 7626095 into TYPO3-Documentation:main Sep 5, 2024
5 checks passed
@brotkrueml brotkrueml deleted the config-bools branch September 6, 2024 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants