#109305Support different values for different languages in the site settings
Description
The Site Settings lack any support for translation handling. Some features, where a setting needs to be different depending on the language (date format, editable labels, etc), can only be configured in the site config or with some relation to the page tree (database, typoscript).
Settings could be flagged as language-specific. When they are, you would be able to overrule the “master” value per language. This would also need UI Integration.
https://talk.typo3.org/t/it-has-gotten-out-of-control-configuration-languages
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[FEATURE] Support different values for different languages in the site settings Resolves: #109305 Releases: main
Related issues 1
History 3
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-03-20T16:26:49+00:00" > 03/20/26, 16:26 </span>
-
Philipp Wrann changed Related to #109484 <span data-processor="relativetime" data-value="2026-04-03T11:26:27+00:00" > 04/03/26, 11:26 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:03+00:00" > 04/21/26, 11:23 </span>
I agree this would be nice!
For now I am using things like “setting.DE.mysetting”, “setting.FR.mysetting” and have categories for each in site definitions. This carries heavy redundancy, needs special evaluation in consumers, and cannot be applied to third party settings.
I guess the whole site settings could make the UI get a language dropdown and context, and persist changes to a “en.settings.yaml” and so forth.
These could then be processed in the site config loader when the sites language is defermined.