Feature #96648
openLet users choose the BE language on login
0%
Description
Feature request/suggestion for v12.
Summary¶
Show a dropdown box with all available BE languages at the login form and let users choose the language for the session. On change, the labels and texts of the login form also change (e.g. from "Username" to "Benutzername" if a users switches from English to German).
Current Situation¶
TYPO3's default backend language is English. Site administrators can download/install translations to let backend users select their language in the user settings. When users log-in to the backend later on, the web interface comes up in the language they configured.
Problem¶
Although simple labels such as "Username" or "Password" are clear to most users, error and info messages are not easy to understand for non-English speaking users. As far as I know (maybe I am wrong), the backend login form and its labels, messages, etc. can not be localized. We can possibly overwrite the labels stored in the XLF file but this is a global configuration. The preferred language of a user is based on the user settings which becomes available after the login
Suggested Solution¶
TYPO3 should let users choose the language before they log-in to the backend. The language selection should take place before or at the login form to enable users to select the language of the labels and other texts shown in the form such as user name, password, "forgot password?" link, MFA token, etc. A dropdown box with country flags and language names could be one option. The default value (pre-selected dropdown item) could be automatically determined based on, for example, a HTTP header in the request (e.g. the " Accept-Language
" header or a custom header with the country code sent by a proxy or CDN node).
Files
Updated by Georg Ringer about 2 years ago
- Status changed from New to Needs Feedback
the backend login is localizeable and this works fine since kind of all versions. checkout LoginController
which checks HTTP_ACCEPT_LANGUAGE
for possible languages. of course those language packs need to be downloaded from the integrator.
IMO no change is required - what do you think?
Updated by Michael Schams about 2 years ago
- File feature-96648-1.png feature-96648-1.png added
I didn't know that. Thanks for clarifying, Georg.
In this case, my problem description is of course incorrect. However, what I have in mind is something like the following:
The list would show all available (installed) languages. The default language could be the language that the user usually uses.
Although, I just realized that this would possibly clash with the fact that you can limit backend languages to specific users (not sure if anyone does that though).
Updated by Georg Ringer about 2 years ago
- Status changed from Needs Feedback to Accepted
- Priority changed from Should have to Could have
I like the idea, however it is not that easy to implement because the selected language should then also be valid for e.g. password forgotten and all other login actions like 2fa. this means that the prefered language must be persisted in a cookie.
i leave the issue open