I had several issues with i18n taxonomy synchronization so i started to trace the issue and managed to fix one of them #365606: Taxonomy synchronisation not working, missing term language.
But i turned out that it has several more issues as well, probaly this feature is not very popular because it hasn't been tested properly. In this issue queue i'll try to fix all of this issues and upload it as a unified patch and also get feedback from i18n users.

Please subscribe to this issue if you're interested and report the problems you have with taxonomy synchronization.
Currently i'm aware of this issues :

Comments

sinasalek’s picture

i18ntaxonomy_taxonomy is available and has most of the require functionality for complete taxonomy synchronization. but it does not work the it's suppose to.

PS : To i18n maintainers : i need advice about this , please correct me if i'm heading to a wrong direction :) tx

sinasalek’s picture

Title: Taxonomy syncronization issue » Taxonomy syncronization issues
jose reyero’s picture

Fixed most of this synchronization issues, see #379306: Synchronize translations for taxonomy terms not working (content type setting)

Still not fixed: tags (patches welcomed)

@sinasalek,
Thanks for putting together these issues, and for the heads up.

sinasalek’s picture

Jose,
Glad that i didn't start :). I'll test the latest version again and report back. (would you please update the dev snapshot if it's possible?)
Guess i can prepare a patch for tags, since i'm using it on my own site.

Thanks.

sinasalek’s picture

I just tried the dev snapshot, it works perfect for regular taxonomies , good job Jose.
However it sets Tags taxonomies of translation node to 0! i think the proper way is to ignore this type of taxonomy when it's not supported.

sinasalek’s picture

Version: 6.x-1.1 » 6.x-1.x-dev
Status: Active » Needs review
StatusFileSize
new2.52 KB

I did it, it works on my own site, it needs a little bit cleanup but i need a maintainer to see it cause i'm not sure if i've implemented it in proper way.

Thanks

sinasalek’s picture

I had some time today to test the dev version again. i wanted to test mode "Localize terms." and it works just fine, but i expected to see category follows node's language , but it follows page language. so the node language might be English but when it appears in German page, categories are in German. However it's not important for me , just wanted to share the result of my test.

There is author problem which i has not cause any problem for me , but it looks like that somewhere there is a wrong query which i guess might cause some problems. when i save a node which is synchronizable i always see this message which is wrong because there is a translation node attach to this node :
All 0 node translations have been synchronized.

I might fix the second issue on my patch.

sinasalek’s picture

StatusFileSize
new38.41 KB

It seems that term names are not unique even per each vocabulary. so i modified the patch and now it returns the lightest term (sorted by weight) when it tries to find term by its name.

There was also another issue which is resolved in this patch. since users are allowed to enter non existence terms in tags vocabulary it could cause some other issues.

I also fixed some small issues and added more comments. i think it's now in a good shape. please try it and let me know you opinion.

sinasalek’s picture

StatusFileSize
new4.2 KB
sinasalek’s picture

I found another issue in i18ntaxonomysync module, Vocabulary name can be translated via interface translation but it does not show up anywhere.

jose reyero’s picture

Status: Needs review » Fixed

Fixed the tag support a bit easier. Now, instead of handling complex form submissions, we reload a clean taxonomy array for the node before synchronizing ($node->i18ntaxonomy).

This should work for all kind of vocabularies now. Please confirm.

sinasalek’s picture

Did you apply my patch?, or you fixed it yourself?

sinasalek’s picture

Oh, i see.i checked the source code, looks good. thanks. i'm testing it right now.

sinasalek’s picture

Tags works very well,
Localize terms works
Per language terms works.

There are still few issues like translating vocabulary names. i'll open a new issue for each one

Good job jose thanks.

Status: Fixed » Closed (fixed)

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