Bug #99064
open
Languages in config.yaml should be order independent
0%
Description
We have recently migrated our site from TYPO3 v10.4.31 to v11.5.18. Somehow there seems to be changes with the language management.
The Problem:
Using an earlier configured config.yaml (with TYPO3 version 9.5), the languages in the file are in the following order:
- German (languageId: 1)
- Italian (languageId: 2)
- Ladin (languageId: 4)
- English (languageId: 0, typo3Language: default)
The problem is illustrated in the picture 'typo3v11-backend-wrong-language.png': The backend shows German as the default language and the English language is missing despite being configured. German appears twice.
When I move the English language section to the beginning of the languages block, the problem is solved (See 'correct-language-configuration.png').
The correct parsing of the default language should not depend on the position it appears in the config.yaml.
Files
Updated by 
Updated by Eric Harrer 9 months ago
- Related to Epic #101557: Translation Handling Findings added
Updated by Eric Harrer 9 months ago
I can confirm this behavior in TYPO3 11. Apparently the default language must always be in first place. This is probably due to the fact that the default language has a special status as a structure-giving language and is always located in the first column of the backend interface of the page module. When a site configuration is newly created via the backend interface, it is ensured that the default language is in the first position. This is not the case if the site configuration was created in another way. At least when saving via the backend interface, the default should be automatically pushed back to the first position. But in the end the languages need some order for the output in the backend.