-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Admin interface language can not be changed anymore #16548
Comments
@MagPim The language of the admin interface can be set for every user. You need to edit the profile: |
Ok thanks, The behaviour is different than before. |
I haven't noticed any change in behavior. This was already the case in the older Pimcore versions. The default language should be used for new users. The language remains unchanged for those already created. |
The user always had language field but we could set the default admin interface here for the user admin... |
Maybe the admin user had in older version a empty language field in the db. It can be possible to create users via PHP with empty language field. Than this option is the default for this users. Should we extend the language select in the admin interface with a "default"/"empty" option? |
We will see if someone replies but I closed this ticket, not a big deal. Thanks |
I would need to investigate what the reason for that setting field is. Don't know of a specific change of behavior there. |
Pimcore version
11.1.5
Steps to reproduce
Tested on demo.pimcore.fun.
Admin default language can be changed in the system settings and set to a different language. Unfortunately, after updating the BO, we still get English like if nothing had changed. The language has been correctly saved in the configuration but admin remains in English.
I have the same behaviour with a different Pimcore 11 installation.
Actual Behavior
I can change the default lauguage and save but English remains as default admin language.
Expected Behavior
I should load Pimcore admin in the set language.
The text was updated successfully, but these errors were encountered: