1. Enable i18n and i18n_taxonomy
  2. Create content type with a translated taxonomy term field
  3. Create a term translated into a language other than the main/interface language
  4. Add that term to a node
  5. Browse to the node edit form for the node

You will see that the interface is now translated into the language of the term. This is because i18n_taxonomy_allowed_values() incorrectly writes to the global $language variable when it just needs a local variable.

CommentFileSizeAuthor
#2 i18n_taxonomy_field_changes_language_3003386_2.patch913 bytesmichel.g

Comments

d.laadidi created an issue. See original summary.

michel.g’s picture

michel.g commented
StatusFileSize
new i18n_taxonomy_field_changes_language_3003386_2.patch913 bytes

Added a patch because I had the same issue.

joshf’s picture

joshf commented
Issue summary: View changes
Status: Needs work » Needs review

It took me a very, very long time to track this issue down. Thanks for the patch!

joshf’s picture

joshf commented
Issue summary: View changes

joseph.olstad’s picture

joseph.olstad
Primary language French
commented
Status: Needs review » Fixed

see forthcomming release 7.x-1.30

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.