Bug #15129
closedNot possible to change BE user language
0%
Description
If you change the language settings of a backend user e.g. from english to german all items are still shown in the original language. If you logoff and relogin to the backend the option says that the language is now german but all texts are still shown in english. So the language always stays on the selected one when the account was created.
(issue imported from #M1693)
Files
Updated by Peter Niederlag about 19 years ago
most likely not a bug but missing the language-packs.
reloading of BE is usually sufficient after changing the language
Updated by Peter Niederlag about 19 years ago
no bug imho. will keep it open for a while and close if no further comments or information will be provided
Updated by old_sirdud about 19 years ago
German language pack is installed. When the user is created with the default language english it is not possible to change the language later. You can close the browser and start again. When the new created user logs in the language is still english. Only when a user is created with default language german then the backend is also in german. It can be easily reproduced on all of my installations.
Updated by old_sirdud about 19 years ago
I've added two screenshots. Language setting is German. Backend appears in English.
Updated by Peter Niederlag about 19 years ago
Might be that you can't change the "default-language" afterwards. Then you need to change the language from the user's setup module.
I'll try to have a look and see if this can be improved.
Updated by Sebastian Kurfuerst about 19 years ago
I think it is like peter described, but I don't think this is a bug. It is anyways possible to set the language with setup.override in user/group TSconfig, if this helps.
Greets, Sebastian
Updated by Peter Niederlag over 18 years ago
Again:
in BE-record you can just apply a default-language. After first login/manual change of the BE-user you need to change the language form users/settings module.
I'll set this to "wont fix" now since I don't consider it a bug.