When using admin language it is only possible to select taxonomy terms, which are language neutral or if the term language is the same as the admin language. In my case I have a site with four Nordic languages in Danish, Swedish, Norwegian and Finish. I want the backend in English, but then I can't use "Per language terms". If I don't use multilingual terms, then path aliases are created language neutral and there can only be one across all languages.

Without admin language the 30% of my backend is translated, resulting in a very pour backend user experience.

Both i18n taxonomy and admin language uses the global $language object. Maybe this is an issue with i18n and the fact that it doesn't use the node language to set taxonomy language?

Comments

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

In our experience, per language terms are a bad idea anyway. All language terms translated via the translate interface UI seem to work better with Views, etc.

But still, good catch. Maybe this is actually a bug?

wulff’s picture

wulff commented
Version: 6.x-1.4 » 6.x-1.x-dev
Assigned: Unassigned » wulff

Good point on the per language terms, Greg.

I'll set up a test site and see if I can find a workaround (the solution could end up being similar to #621426: Module stopped URL Alias from working?.

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Issue summary: View changes
Status: Active » Closed (outdated)

Drupal 6 is no longer supported. If this issue is relevant for Drupal 7, please re-open and update the version.