You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Behavior
The flexform has for the option settings.recursive the values [empty], '0', '1', and so on. If this field is included in overrideFlexformSettingsIfEmpty the value '0' will be treated as empty and the TypoScript value will be used. With a TS default of for example "5" it's impossible to set it to '0' in the flexform
Expected behavior/output
For fields where [empty] and '0' have different meaning overrideFlexformSettingsIfEmpty should not treat '0' as empty.
Environment
TYPO3 version(s): [10.4.latest]
news version: [master]
Is your TYPO3 installation set up with Composer (Composer Mode): [yes]
OS: [Linux]
Possible Solution
Seems quite complex to have a generic solution. As a workaround we've patched EXT:news to actively check for the 'recursive' field.
Additional context
[none]
The text was updated successfully, but these errors were encountered:
Hi David, as I wrote under "Possible solution" we didn't find a generic solution. Because the issue was discovered close to going live and there was just a single field ('recursive') that was problematic a patch was made to treat "0" as not empty just for this field.
It's not a real solution. Perhaps it needs an extra setting to list the fields for which the "zero is interpreted as empty" check can be skipped?
Bug Report
Current Behavior
The flexform has for the option
settings.recursive
the values [empty], '0', '1', and so on. If this field is included inoverrideFlexformSettingsIfEmpty
the value '0' will be treated as empty and the TypoScript value will be used. With a TS default of for example "5" it's impossible to set it to '0' in the flexformExpected behavior/output
For fields where [empty] and '0' have different meaning
overrideFlexformSettingsIfEmpty
should not treat '0' as empty.Environment
Possible Solution
Seems quite complex to have a generic solution. As a workaround we've patched EXT:news to actively check for the 'recursive' field.
Additional context
[none]
The text was updated successfully, but these errors were encountered: