#105694Extension settings: customcategory label not used
Description
In ext_conf_template.txt the same syntax should be applicable as in the constants editor (according to the core documentation). But labeling a customcategory as described for the constant editor doesn’t seem to work anymore in the extension settings since v12.
The “tricks” described in #100936 don’t work for me (e.g. adding an empty line afterwards) in the extension settings editor. The labels used for displaying the tabs (i.e. the customcategories) are simply the customcategory name (with ucfirst() applied in v12). This also happens in v13 LTS. In v11 LTS it worked fine.
The labels of customsubcategories are ok.
Example:
# customcategory=api=LLL:EXT:myext/Resources/Private/Language/locallang.xlf:extconf.api
# customsubcategory=baseurl=LLL:EXT:myext/Resources/Private/Language/locallang.xlf:extconf.baseurl
# cat=api/baseurl/a; type=string; label=Files API
filesApi = /api/v1/files/
# cat=api/baseurl/b; type=string; label=Mails API
mailsApi = /api/v1/mails/
The label for customcategory is not shown, but simply “Api” (or “api” in v13LTS), while the label for customsubcategory is shown correctly.
Reviews 2
Related issues 2
Files 1
History 1323
-
Georg Ringer changed Related to #100936 <span data-processor="relativetime" data-value="2024-11-26T06:45:45+00:00" > 11/26/24, 06:45 </span>
-
Garvin Hicking commented and changed status
NewClosed <span data-processor="relativetime" data-value="2024-11-26T09:35:11+00:00" > 11/26/24, 09:35 </span> -
Michael Stopp commented <span data-processor="relativetime" data-value="2024-11-26T11:10:24+00:00" > 11/26/24, 11:10 </span>
I don’t think that the problem I describe in my issue is the same as in #100936. I first considered just adding a comment to #100936, but then decided to create a new issue, because the two situations (TS constant editor vs. extension settings) behave differently, despite using the same syntax.
In the same TYPO3 installation, where I encountered this problem with the extension settings, we also have a site package that uses lots of customcategories + customsubcategories for defining all sorts of TS constants. This all works fine and all the labels are displayed correctly. (Which means that I can’t really reproduce the problems described in #100936 for the latest v12 versions).
But the identical use of customcategory + customsubcategory (in terms of syntax) in
ext_conf_template.txtdoes not work for me in the same v12 TYPO3 installation (while it did in v11 LTS). It’s also a different situation, because customcategories in the extension settings are translated into tabs, which is not the case for the constant editor. I therefore think this is a related but different issue. -
Garvin Hicking commented and changed status
ClosedNew <span data-processor="relativetime" data-value="2024-11-26T11:57:08+00:00" > 11/26/24, 11:57 </span>Understood. Reopening, haven’t verified this yet.
-
Marco Kuprat commented <span data-processor="relativetime" data-value="2025-03-12T07:36:23+00:00" > 03/12/25, 07:36 </span>
I can confirm that also for TYPO3 13.4.
Also category labels of system extensions like “backend” or “extensionmanager” are not displayed properly. -
Rémi Payette commented and changed attached 105694.patch <span data-processor="relativetime" data-value="2025-09-30T19:45:51+00:00" > 09/30/25, 19:45 </span>
I tried to push this to the review server but I think outbound port 29418 is blocked here :(
I attached a patch file, my commit message would have been :
>[BUGFIX] Bring back the use of labels to display customcategory in extension configuration
>
>Resolves: #105694
>Releases: main -
Gerrit Code Review pushed patch set 1 for main to change 90850 status
NewUnder Review <span data-processor="relativetime" data-value="2025-09-30T20:37:19+00:00" > 09/30/25, 20:37 </span> -
Garvin Hicking changed Related to #98357 <span data-processor="relativetime" data-value="2025-09-30T20:47:42+00:00" > 09/30/25, 20:47 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 90850 <span data-processor="relativetime" data-value="2025-09-30T20:49:26+00:00" > 09/30/25, 20:49 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-09-30T20:53:42+00:00" > 09/30/25, 20:53 </span>
@nalmar Thanks for the commit! I tried to brush up on it. There are CI failures. I’m afraid with the GitHub workflow you will not be able to follow-up on the patch to fix the failures there.
Also I’m not too sure about the side-effects of the patch, but I could now relate this to issue #98357 which reworked this interface.
For TYPO3 v14 we are planning to completely scrap the custom extension configuration interface. A fix like this will no longer be backportable to TYPO3 v12, so… I just want to raise awareness that maybe our review powers will be more focussed on getting the new configuration interface in, rather than fixing the “mess” that is ext_conf_template.txt parsing, which has no future.
-
Gerrit Code Review pushed patch set 3 for main to change 90850 <span data-processor="relativetime" data-value="2025-09-30T20:54:49+00:00" > 09/30/25, 20:54 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 90850 <span data-processor="relativetime" data-value="2025-09-30T21:23:26+00:00" > 09/30/25, 21:23 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 90850 <span data-processor="relativetime" data-value="2025-09-30T21:25:15+00:00" > 09/30/25, 21:25 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 90850 <span data-processor="relativetime" data-value="2025-09-30T21:37:34+00:00" > 09/30/25, 21:37 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 90850 <span data-processor="relativetime" data-value="2025-10-01T14:10:39+00:00" > 10/01/25, 14:10 </span>
-
Rémi Payette commented <span data-processor="relativetime" data-value="2025-10-01T14:27:55+00:00" > 10/01/25, 14:27 </span>
> For TYPO3 v14 we are planning to completely scrap the custom extension configuration interface. A fix like this will no longer be backportable to TYPO3 v12, so… I just want to raise awareness that maybe our review powers will be more focussed on getting the new configuration interface in, rather than fixing the “mess” that is ext_conf_template.txt parsing, which has no future.
What is it going to be replaced with and is the replacement already available in v13 ? I could already get my extension ready if it’s the case.
-
Rémi Payette commented <span data-processor="relativetime" data-value="2025-10-01T15:16:52+00:00" > 10/01/25, 15:16 </span>
I think I answered my own question : https://docs.typo3.org/m/typo3/reference-coreapi/13.4/en-us/ApiOverview/SiteHandling/SiteSettingsEditor.html
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-10-01T15:27:10+00:00" > 10/01/25, 15:27 </span>
Yes, the Settings API is the ideal candidate for this, and the foundation is ready to apply what’s also been done for the Site Set Settings Editor here. It’s not adoptable yet, and still in planning/development phase.
-
Gerrit Code Review pushed patch set 8 for main to change 90850 <span data-processor="relativetime" data-value="2026-04-22T06:31:46+00:00" > 04/22/26, 06:31 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 90850 <span data-processor="relativetime" data-value="2026-06-11T22:21:34+00:00" > 06/11/26, 22:21 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 94502 <span data-processor="relativetime" data-value="2026-06-12T07:52:33+00:00" > 06/12/26, 07:52 </span>
-
Rémi Payette commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-06-12T08:05:09+00:00" > 06/12/26, 08:05 </span>Applied in changeset commit:b8064d049efa59c2abbd63c62f8fc65bb22163df.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-08-11T08:46:39+00:00" > 08/11/26, 08:46 </span>
Hi Michael,
thanks for your Feedback. I believe this is the same information that is tracked in https://forge.typo3.org/issues/100936 so I’d like to close this issue as a duplicate. Please feel free to add your comments in the existing issue.
Thanks!