hello
im using i18n 6.x.1.x-dev with drupal 6.3

my language config :
"Path Prefix Only"
"Only current language and no language"

i create a taxonomy vocabulary without language and with this option :
"Per language terms"
i add terms for the first language and for the second one
im using "translation" button to make the terms match

i create a node in my native language
i can see the good list of taxonomy terms and choose one
im saving the node and the result is fine

i create a translation of this node using the drupal's translation button.
i can see the good list of taxonomy terms and choose one
im saving the node and the result is fine

then, when viewing the node, i change the language using the "language switcher" block, and i cannot see the first taxonomy term saved, only the last saved is kept.

Comments

jose reyero’s picture

jose reyero commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Do you have the synchronization module enabled?
That one may change translations of the current node.

(If not, please let me know which modules you have enabled)

greenskin’s picture

greenskin commented
Status: Postponed (maintainer needs more info) » Active

We are having a similar issue where we create a vocabulary with a per language terms. Then create a new node in the default language (en) then create a translated version of that node for another language (es) and select a 'es' specific term. Then when we go back to edit the 'en' node the term is not selected, and using Devel module look at the Dev load tab we find that the 'en' node is pulling the term for the 'es' node.

Upon further investigation I have found that in the table 'term_data', it is saving the 'en' node tid as the tid from 'es' when the 'es' node is saved and vice versa.

greenskin’s picture

greenskin commented
Category: support » bug

Changing the category back to 'bug report' as this happens with a fresh Drupal 6 and only i18n plus dependent modules enabled.

jose reyero’s picture

jose reyero commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Please someone answers my question in #1

Do you have the synchronization module enabled? which settings

That may be an (intended) effect of i18n synchronization module.

greenskin’s picture

greenskin commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Yes, I meant to add my findings the other day but didn't get 'round to it. It is synchronization that is doing it. I could just turn off the taxonomy syncing for that content type except that I had another vocabulary tied to it that needs to be synced. I'll submit a feature request for being able to sync individual vocabularies for a content type instead of all taxonomy or none.

sinasalek’s picture

sinasalek commented

Same problem here with Drupal 6.14 and 6.x-1.1

borjagut’s picture

borjagut commented
Version: 6.x-1.x-dev » 6.x-1.7
Component: Miscellaneous » Code
Status: Closed (fixed) » Active

Hi,

nobody could solve this problem? I've the same, but with core 6.19 and i18n 6.x-1.7.

thanx so much

jose reyero’s picture

jose reyero commented
Component: Code » Blocks
Status: Active » Closed (won't fix)

Cleaning up the issue tracker. Closing all issues that haven't got any follow up for the last year (and are not on RTBC state). Feel free to reopen if you're willing to (really) work on this.