Assumed there's a multilingual vocabulary (Deutsch, Français, English) with the terms (aktiv, actif, -) and (passiv, passif, passive). Term translation is done with i18ntaxonomy and translations are set up as shown. And the i18n content selection mode says that content of several languages may be displayed to the user. Default language is German.
Now, the vocabulary is displayed, with Content Taxonomy for example, but the content selection mode is not properly applied to the vocabulary. Content Taxonomy uses taxonomy_get_tree(...) to retieve the terms. The result is not what you would expect:
Content selection mode: Mixed current language (if available) or default language (if not) and language neutral.
Current language: German.
Expected result of taxonomy_get_tree(...): aktiv, passiv
Actual result of taxonomy_get_tree(...): aktiv, passiv
--> "As expected." (just because current language = default language)
Content selection mode: Mixed current language (if available) or default language (if not) and language neutral.
Current language: French.
Expected result of taxonomy_get_tree(...): actif, passif
Actual result of taxonomy_get_tree(...): aktiv, actif, passiv, passif
--> Not as expected, because for both terms is a translation availabe, and therefore the German terms shouldn't be in the result set.
Content selection mode: Mixed current language (if available) or default language (if not) and language neutral.
Current language: English.
Expected result of taxonomy_get_tree(...): aktiv, passive
Actual result of taxonomy_get_tree(...): aktiv, passiv, passive
--> Not as expected, because for "passiv" is a translation availabe, and therefore the German term "passiv" shouldn't be in the result set.
Details:
content/taxonomy/edit/vocabulary/1
Multilingual Options are set to:
(O) Per language terms. Different terms will be allowed for each language and they can be translated.
admin/content/taxonomy/1/translation
(Term translation ist set up here.)
admin/settings/language
Default language is German.
admin/settings/language/i18n
Content selection mode is one of these:
(?) Current language and language neutral. [1]
(?) Mixed current language (if available) or default language (if not) and language neutral. [1, 2]
(?) Only default language and language neutral. [1]
(?) All content. No language conditions apply.
[1] There's no language neural term in the example vocabulary. (Language neutral terms should always be part of the result set.)
[2] This issue is for sites using this content selection mode, as this is the only mode where term translations of the default language should disapear when there's a term translation for the current language.
Comments
Comment #1
Aress commentedI've got a similar error. If I use the option " Mixed current language (if available) or default language (if not) and language neutral. ", both default and translated terms are shown when I create a new node in a language different from default.
For example default language italian, current language english. If I switch the interface to English and then I create a node, I can choose both italian and english taxonomy terms. If the interface is in italian all works fine.
Any suggestions?
Comment #2
wanjee commentedHello,
Same issue here.
Content selection mode is : "Mixed current language (if available) or default language (if not) and language neutral."
Vocabulary translation mode is : "Per language terms. Different terms will be allowed for each language and they can be translated."
Terms exists in our 3 languages and translations are provided using admin/content/taxonomy/_vid_/translation
There is no neutral language terms but we really need the fallback to language neutral for other purposes.
Whenever we edit a node we get terms for current language (fr/nl) AND the English ones (English is default language). If we edit a node in English we only get English terms.
It's blocking for us as some terms are very similar in both displayed languages leading to incorrect term choice by the user. English terms should never be selected on a Dutch node...
Any help would be greatly appreciated !
Thanks,
Wanjee
Comment #3
wanjee commentedComment #4
jose reyero commentedCleaning up the issue tracker. Closing all issues that haven't got any follow up for the last year.