#106640Site settings definition: Allow localization of enum labels
Description
It is possible to localize labels in site settings definitions, but not the labels of an enum. They are always treated as a string…
I would like to see that something like this is possible:
setting.option:
# localized setting label - works already
label: 'LLL:EXT:example/Resources/Private/Language/locallang.xlf:setting.option'
category: Category
type: string
enum:
option1: 'LLL:EXT:example/Resources/Private/Language/locallang.xlf:setting.option.1' # localized enum label - does not work!
option2: 'LLL:EXT:example/Resources/Private/Language/locallang.xlf:setting.option.2'
default: 'option2'Reviews 2
History 612
-
Eric Harrer commented and changed target version Tags settings, definition, enum, label, language, localization <span data-processor="relativetime" data-value="2025-09-25T08:32:31+00:00" > 09/25/25, 08:32 </span>
-
Oliver Hader changed target version <span data-processor="relativetime" data-value="2026-01-23T12:29:47+00:00" > 01/23/26, 12:29 </span>
-
Eric Harrer commented <span data-processor="relativetime" data-value="2026-02-19T15:09:22+00:00" > 02/19/26, 15:09 </span>
I revisited my earlier approach with a closer look at the current Core internals and would suggest the following combined strategy:
- Keep explicit enum labels in
settings.definitions.yamlas an override (including directLLL:usage). - Add a standardized auto-key pattern for enum labels in
labels.xlf:settings.enum.<settingKey>.<enumValue>
- Use a deterministic fallback chain:
- explicit enum label if it is an
LLL:reference - derived key
settings.enum.<settingKey>.<enumValue> - literal enum label from YAML
- enum value itself (last fallback)
This keeps the feature backward-compatible while aligning with existing site settings key logic (
From an integrator perspective this provides both worlds:settings.*andsettings.description.*).- convention-based localization via
labels.xlf - explicit
LLL:labels when fine-grained control is needed
- Keep explicit enum labels in
-
Eric Harrer changed assigned to Eric Harrer <span data-processor="relativetime" data-value="2026-02-19T16:50:25+00:00" > 02/19/26, 16:50 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 92902 status
NewUnder Review <span data-processor="relativetime" data-value="2026-02-19T17:12:36+00:00" > 02/19/26, 17:12 </span> -
Gerrit Code Review pushed patch set 2 for main to change 92902 <span data-processor="relativetime" data-value="2026-02-19T17:14:11+00:00" > 02/19/26, 17:14 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 92902 <span data-processor="relativetime" data-value="2026-02-19T19:15:20+00:00" > 02/19/26, 19:15 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 92902 <span data-processor="relativetime" data-value="2026-02-19T20:10:25+00:00" > 02/19/26, 20:10 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 92902 <span data-processor="relativetime" data-value="2026-02-20T10:23:19+00:00" > 02/20/26, 10:23 </span>
-
Eric Harrer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-03-02T19:25:10+00:00" > 03/02/26, 19:25 </span>Applied in changeset commit:22342ce547fdb5a44fdabd62e05e3c14db6e8f8b.
-
Gerrit Code Review pushed patch set 1 for main to change 93041 status
ResolvedUnder Review <span data-processor="relativetime" data-value="2026-03-03T14:15:31+00:00" > 03/03/26, 14:15 </span> -
Eric Harrer commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-03-07T23:03:07+00:00" > 03/07/26, 23:03 </span>I am closing this as it has been resolved by merged patch:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/92902
We currently have the following identifiers available in
Configuration/Sets/<SITE_SET_IDENTIFIER>/labels.xlf:settings.<SETTING_IDENTIFIER>settings.description.<SETTING_IDENTIFIER>It would be great if there were also a standardised label identifier for enums instead of the
LLLnotation.I would like the following spelling, for example:
settings.<SETTING_IDENTIFIER>.enum.<ITEM_VALUE>Example:
Configuration/Sets/<site_set_identifier>/settings.definitions.yaml:</site_set_identifier>
Configuration/Sets/<site_set_identifier>/labels.xlf:</site_set_identifier>