Review main Merged

92519[TASK] Use "en" instead of "default" as backend user language

Benni Mack CR +2 V +2 Hard +205 −84 updated 02/11/26, 19:57

Commit message

The backend user language field (be_users.lang) historically used
"default" as the value for English. This changes the default to
the standard ISO 639-1 language code "en" instead.

With TYPO3 v12 Site Language Locales configuration in frontend
has been adapted, and backend now has changed as well.

The language key "default" is still accepted for backwards
compatibility with existing overrides or custom code,
but is no longer selectable in the backend user interface.

An upgrade wizard migrates existing backend user records from
"default" to "en".

Review

  • Code review CR +2 Done
    • Benni Mack +2
    • Anja Leichsenring +1
    • Ayke Halder +1
  • Verified V +2 Done
    • Benni Mack +2
    • Oliver Klee +1
    • Anja Leichsenring +1
    • Ayke Halder +1
    • core-ci +1 CI

Issues 1

Files 46

Show 26 more files

Review log 2736

Show 711 earlier messages
  1. Benni Mack uploaded patch set 1 01/26/26, 21:01

  2. core-ci voted on patch set 1 V +1 01/26/26, 21:09 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94380

  3. Benni Mack marked it ready for review 01/27/26, 09:01

  4. Benni Mack rebased onto patch set 2 V +1 01/27/26, 09:01

  5. core-ci voted on patch set 2 V +1 01/27/26, 09:10 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94401

  6. Benni Mack commented on patch set 3 V +1 01/27/26, 11:15

    Published edit on patch set 2.
  7. Benni Mack uploaded patch set 4 01/27/26, 11:17

  8. Benni Mack commented on patch set 5 01/27/26, 11:18

    Published edit on patch set 4.
  9. Ayke Halder commented on patch set 2 CR +1 01/27/26, 11:27

    In general this looks good - but didn't run the actual code. I'll do that later.

    Important-108783-BackendUserLanguageDefaultChangedToEn.rst:33

    We might want to keep `default/base` as "internal core logic" and thereby also keep the actual `default` in "TypoScript overrides" in the future - depending on the decision whether or not the internal fallback is changed to e.g.: * de -> default instead of current * de -> en -> default So maybe keep the wording here more open by just dropping the reference to "TypoScript overrides": ```suggestion * In general: Code that uses `default` as a language key will continue to work as `default` is still mapped to `en` internally. ```
  10. core-ci voted on patch set 3 V +1 01/27/26, 11:28 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94422

  11. core-ci voted on patch set 4 V +1 01/27/26, 11:28 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94423

  1. core-ci voted on patch set 5 V +1 01/27/26, 11:30 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94424

  2. Garvin Hicking commented on patch set 5 V -1 01/27/26, 11:47

    User settings show: The selected language "English" is not available before the language files are installed. You can use "Manage Language Packs" in the Maintenance module to easily download new language files. when switching a user language to 'english'; and 'english' cannot be picked as a maintenance language.
  3. Garvin Hicking commented on patch set 5 01/27/26, 12:08

    More places to address: - "Hand in the locale to load, or english ("default")." in LocalizationFactory.php - SiteLanguage.php->getTypo3Language() probably needs to stay with 'default' for now - TranslateViewHelper also uses 'default' for languageKey description - Several instances where we may want to change languageServiceFactory->create('default') to 'en': - CreateBackendUserCommand->getBackendUserPasswordValidationErrors - DebugBackendModulesCommand -> languageServiceFactory->create('en') - AbstractformEngineAjaxController->getLabelsFromLocalizationFile() - Typo3Information constructor - PasswordSetCommand - SettingsController->extensionConfigurationGetContentAction - CleanupRedirectsCommand - SchedulerExecuteCommand, SchedulerListCommand - SetupModuleController->renderLanguageSelect() [this one might be worth verifying with a fresh install too) - Middleware/WorkspacePreview - AbstractXmlParser->_getParsedData - languageKey handle 'default|en'? - XliffParser->doParsingFromRoot() - also 'default/en'? - Form/Service/TranslationService.php->setLanguageKeys() - LinkAnalyzerResult->processBrokenLinks (languageCode) (yes, I went through every "default" and 'default' search result. yes, there are lots.)
  4. Garvin Hicking commented on patch set 5 02/04/26, 18:23

    Reply

    This now happened in main already. Switching my user language to gernan and back to english "fixed" it. This is beyond the scope of this patch now I guess.
  5. Ayke Halder commented on patch set 5 02/06/26, 14:36

    SetupModuleController.php:711

    This part of the condition is always `true`. ```suggestion if ($currentSelectedLanguage !== 'en' && !@is_dir(Environment::getLabelsPath() . '/' . $currentSelectedLanguage)) { ``` Either: Change this to `en` to allow for english langauge, even in case the english langauge package is still missing. --> English can always fall back to common/base without the need of the english language package. Or: Remove the check `… !== 'default'` and always give an error if the english language package is not installed.
  6. Ayke Halder commented on patch set 5 02/06/26, 14:41

    LanguagePackService.php:96

    Just completely drop this. Also there must not be an exemption for `en` here, as also the english language package needs updates.
  7. Ayke Halder commented on patch set 5 02/06/26, 15:04

    LanguagePackService.php:96 Reply

    Okay, this exemption must stay. English has no language packages right now, as the english language files are provided by the extensions and not by the translation team. Maybe this can become a future feature: * The extension author provides common/base english. * The translation team provides a proper translation for the english language.
  8. Ayke Halder commented on patch set 6 V +1 02/06/26, 15:13

    Published edit on patch set 5.
  9. Ayke Halder commented on patch set 6 02/06/26, 15:14

    SetupModuleController.php:711 Reply

    Fix applied.
  10. core-ci voted on patch set 6 V +1 02/06/26, 15:23 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/95303

  11. Benni Mack uploaded patch set 7 V +1 02/07/26, 08:04

  12. Benni Mack uploaded patch set 8 02/07/26, 08:07

  13. Benni Mack commented on patch set 8 02/07/26, 08:07

    This change is ready for review.

    Reply

    I adapted the places that made sense.

    Important-108783-BackendUserLanguageDefaultChangedToEn.rst:33 Reply

    Done
  14. core-ci voted on patch set 7 V -1 02/07/26, 08:39 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/95371

  15. core-ci voted on patch set 8 V -1 02/07/26, 08:43 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/95372

  16. Benni Mack uploaded patch set 9 V -1 02/08/26, 09:50

  17. core-ci voted on patch set 9 V +1 02/08/26, 09:58 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/95403

  18. Ayke Halder commented on patch set 9 02/09/26, 09:20

    AbstractXmlParser.php:84

    IMO this needs some further investigation.
  19. Benni Mack commented on patch set 9 02/09/26, 09:55

    AbstractXmlParser.php:84 Reply

    this isn't in active use anymore
  20. Ayke Halder commented on patch set 9 02/09/26, 09:57

    AbstractXmlParser.php:84 Reply

    Acknowledged
  21. Ayke Halder voted on patch set 9 CR +1 V +1 02/09/26, 21:11

  22. Oliver Klee voted on patch set 9 V +1 02/09/26, 23:53

  23. Anja Leichsenring voted on patch set 9 CR +1 V +1 02/11/26, 19:56

  24. Benni Mack voted on patch set 9 CR +2 V +2 02/11/26, 19:57

  25. Benni Mack merged patch set 10 02/11/26, 19:57