Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
So... how exactly do i use this plugin?
i have set my default language to Danish, yet the module says that my default language is English?
If im in danish, and switch language to English while logged in, the whole Drupal system gets translated to english - and that is absolutely not what i want.. I want to use Drupal in Danish only, but let the content be translateable .. i really dont know what im doing wrong, i have checked all settings and they seem to be set the correct way.
Please provide some information or tutorials for this great module.
Thanks.
Comments
Comment #1
GiorgosKplease provide a screenshot of what your settings look like
also remember to set correct permissions for the role that needs to use admin language
and I think each user has to set the language they prefer on their user form
user/xxx/edit
Anyway here is very simple tutorial
and select appropriate settings
my settings are
- Use administration language on every page except the listed pages.
- Use admin paths provided by core (checked)
- Hide administration language on user form (enabled but does not work due to #2046395: Hide widget "Administration language select" from the user form)
-Hide administration language on node form (disabled)
- Force use of default language (disabled)
- Force language neutral aliases (disabled)
- Use administration language in the administration menu (enabled)
Comment #2
AnybodyI think these both describe the same problem in different ways...
Comment #3
AnybodyI think I've found the reason, at least it fixes these problems for me:
In
(Line 653 of admin_language.module)
a wrong variable was used: "admin_language" which is always empty and so always returns "en" fallback!
This has to be corrected to: "admin_language_default".
Important: This has NO implications on the used admin language, but is just a problem on the Display-Layer.
Please fix in the next release :)
Comment #4
Liam MorlandIs this still relevant?
Comment #5
Anybody@Liam Morland: Yes I think so. The code is still the same, but now in Line 816 in the latest dev. Of course my assumptions should be checked, but for me this was the reason for the problems.
Comment #6
Liam MorlandCan you provide your fix as a patch?
Comment #7
AnybodyNope, as written in an other issue I'm now using a different module. Sorry.