Issue Bug Closed

#102760ext_conf_template.txt is parsed inconsistently, leading to missing configuration fields

Christian Spoo 01/05/24, 14:22 updated 07/09/24, 15:12

Description

If I have an extension with the following ext_conf_template.txt:

# cat=foo//0; type=boolean; label=some config
bar = 0

# cat=foo//1; type=boolean; label=other config
baz = 0

only the second configuration option is shown in the Backend. However, if I replace the double slashes with single ones, like so:

# cat=foo/0; type=boolean; label=some config
bar = 0

# cat=foo/1; type=boolean; label=other config
baz = 0

both options are shown. As the documentation defines ext_conf_template.txt’s syntax to be similar to the one used for the TS constants editor, I think this is a bug. The examples above are comparable to those in the documentation (https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/UsingSetting/TheConstantEditor.html#id3).

Reviews 2