Drupal 7.15
Internationalization 7.x-1.7
Variable 7.x-2.1
(Pathauto 7.x-1.2)

There is problem with taxonomy vocabulary and terms translation. When adding taxonomy terms to the content, it seems that when you have 2 tags in different language but they have the same name [for example you translate computer (en) to computer (fr)] then link to this term is broken. When I translate content to other language then all tags are wrong linked to other language (I HAVE translated all tags). Drupal is creating new tag tagname-0 (i18n 1.7) or choose wrong tag, it's not looking at you actual language that you adding content and tags with (i18n 1.5).

It also seems that translated Vocabulary Name is not used in translated taxonomy links - the default vocabulary language name is used all the time.

In older version of i18n (1.4) everything is working fine, however re-saved nodes (1.7) are behave like I describe above.

Those issues MAY have been pathauto related but I doubt that, [term:i18n-vocabulary]/[term:i18n-name]. Anyway some drupal guru should check this out.

Comments

spamator12’s picture

spamator12 commented

I have check pathauto and redirect/global redirect modules. None seems to interrupt with taxonomy translation, however I have exactly same problem:

It also seems that translated Vocabulary Name is not used in translated taxonomy links - the default vocabulary language name is used all the time.

and it looks like a pathauto integration problem...

pwiniacki’s picture

pwiniacki commented

I have just test it on clean drupal install:

drupal, ctools, i18n, token, pathauto, variable, views - all latest stable versions.

I can confirm this "It also seems that translated Vocabulary Name is not used in translated taxonomy links - the default vocabulary language name is used all the time."

link is indeed wrong - [term:vocabulary]/[term:name] - give me correctly translated term name but not translated taxonomy vocabulary. Also in article when you change language there is still title tags, even when you translate it to something else.

Also when you translate taxonomy term and it has the same name as default language one, I can confirm that drupal is adding

-0

to link to that taxonomy term and it's not working, taxonomy relations are destroyed.

Nice catch I didn't even notice it on my site. I'm making this as a major cause it simply completely broke my taxonomy relations.

kelutrab11’s picture

kelutrab11 commented

If I remember correctly Jose said something that taxonomy name must be different in all languages - but I can't find the issue right now.

pwiniacki’s picture

pwiniacki commented
Priority: Normal » Major

I'm using "Translate. Different terms will be allowed for each language and they can be translated." as a translate option so I don't think he refer to this. I would be stupid to name some tags like special events - for example new year to new year eng, new year fr etc. don't you think ? And it always worked fine for me in previous i18n versions so I don't think that maintainer had this scenario in mind when he was speaking of different taxonomy names.

batigol’s picture

batigol commented

Definitely a major. I can't update my site cause of this, it's totally destroy my taxonomy relations. I hope it's not a maintainer way for i18n but simply a bug, if not I'm in black hole here :P

I'm gonna test 1.6 to see if it behave like 1.7 Now I'm using 1.4 but even in 1.5 you can't chose same taxonomy name in other language you want translate the term to.

henrix34’s picture

henrix34 commented

I have just download drupal 7.15 and Internationalization 7.x-1.7 and I can confirm this problem exist (and it's annoying).

batigol’s picture

batigol commented

As I have wrote in #1 about pathauto - taxonomy vocabulary name is properly translated when I use pathauto 7.x-1.0 - I dunno what module fu@# things up.

However there still issue with taxonomy translation when u use same name for both translations - links are broken no matter what version you are using (tested with pathauto 7.x-1.0, pathauto 7.x-1.1, pathauto 7.x-1.2, i18n 7.x-1.7, i18n 7.x-1.6, i18n 7.x-1.5, 7.x-1.x-dev).

dwhutton’s picture

dwhutton commented

This seems to be the same issue that I have. The following steps will consistently reproduce the problem on my site, with Drupal 7.16 and Internationalization 7.x-1.7:

1) use a dual language site, let's say English and French, with /fr being the domain suffix for French. The vocabulary is set to translate (as opposed to localize)
2) choose a term that is the same in both languages, such as a name -- say Elvis Presley
3) create both the English and the corresponding French term, with different URLs (say category/topics/elvis-presley and category/topics/elvis-presley-0) and make these two a translation set
4) create a new English page, select 'Elvis Presley' from the list of existing terms, and save the page.
5) instead of the English term, the French one has been selected. You can see this by hovering over the term link: it will end in elvis-presley-0 instead of elvis-presley

I have managed to manually repair a few nodes and terms by editing the values in the taxonomy_index and field_data_taxonomy_vocabulary_x and field_revision_taxonomy_vocabulary_x tables, but the corruption of the database is now widespread. The wrong-language terms seem to be propagating through my system, not just affecting recently-created or recently-edited nodes, but dozens of old nodes.

I consider this major since it is corrupting an extensive dual-language vocabulary with thousands of tagged nodes. One other point -- this entire setup worked perfectly on Drupal 6.

batigol’s picture

batigol commented

I have managed to manually repair a few nodes and terms by editing the values in the taxonomy_index and field_data_taxonomy_vocabulary_x and field_revision_taxonomy_vocabulary_x tables, but the corruption of the database is now widespread. The wrong-language terms seem to be propagating through my system, not just affecting recently-created or recently-edited nodes, but dozens of old nodes.

Thanks for the tip with the database.

My steps to reproduce are almost identical. I just use the same name for my taxonomies - like Elvis Presley (eng) and Elvis Presley (fr) but I distinguish them by vocabulary name. So in English it would be mypage/tags/Elvis-Presley and in French mypage/connexion/Elvis-Presley

I18n often try to add -0 to a tag but it should not do that when you have translated vocabulary name.

I wonder why older version of pathauto display correctly translated vocabulary name and newest version is not - it must be some bug in integration between those modules.

henrix34’s picture

henrix34 commented

Is this bug going to be fixed or we still need to use 1.4 ?

I can't believe that after 2 weeks we don't get any answer or ETA...

finex’s picture

finex commented

@henrix34: probably because Drupal i18n development is focused on the upcoming entity translation which will ship with Drupal 8 next year :-(

batigol’s picture

batigol commented

Next year :P So all ppl who instaled i18n are in black hole now ?:P

finex’s picture

finex commented

@batigol: a sort of :-)
...jokes apart: I'm currently using i18n but I've completely substitued taxonomy module with entity_reference and some custom code and patches in order to get it properly work. But there are a lot of use cases, so my advise is to try different combinations of modules/settings/patches until a working solution is found.

Cyclodex’s picture

Cyclodex commented

@FiNeX
But you do not have tag creation on entity_reference, do you?

FYI:
I also had some issues with ER and languages, and therefor I started creating this i18n_contrib patch/submodule to improve it in some use-cases like sync or add translation parts.

finex’s picture

finex commented

@Cyclodex: indeed, a free-tagging like feature is not easily doable with ER, but you can use modules like http://drupal.org/project/entityconnect or http://drupal.org/project/references_dialog (which needs some patches in order to work with ER if I remember correctly...). Moreover time ago I've found this sandbox: http://drupal.org/sandbox/dman/1720762, but I never tried it.

About http://drupal.org/node/1688156 I'm already following that issue and I will try the patch soon :-)

Cyclodex’s picture

Cyclodex commented

Cool, thanks for your feedback, I will check out the links!

kelutrab11’s picture

kelutrab11 commented

So is there any fast fix or work around? It's so hard to make i18n to distinguish between two taxonomy terms (with same name)? THANKS.

mwadi’s picture

mwadi commented

I think it is related to the pathauto module, the alias's language of the terms are set as "all" instead of their actual languages, which make a duplication.

kelutrab11’s picture

kelutrab11 commented

I have created new issue in PA queue - http://drupal.org/node/1860686. Lets see what PA guru think about this issue. It could be integration problem between those modules...

batigol’s picture

batigol commented

I can't fix this. I moved my page to WP (I have check joomla also but it does not support DA) cms until it's fixed.

spamator12’s picture

spamator12 commented

@batigol can you tell me how did you manage it to work ? I'm suffering here cause I simply can't use same taxonomy name with all my languages (3) and my links are not working properly. thanks.

batigol’s picture

batigol commented

It was simple drupal multisite installation move to wordpress (it support multisite). You can choose whatever tag module you want - tags, simple tags, etc. I have also add some tag cloud without any problem. Everything is working perfect. However I have some bigger sites with more complex modules and move them to wp is not so easy task. I still hope this issue will be fixed in near future and I won't need to move those sites (especially since old tags behave OK).

spamator12’s picture

spamator12 commented

I have manage it to work thanks to yours PM. Thanks again.

jose reyero’s picture

jose reyero commented
Title: Taxonomy translation problems » Taxonomy translation problems / tags in different languages, same name.
Component: Taxonomy » Compatibility
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)
Issue tags: +pathauto

Just renaming, recategorizing (that kind of titles don't help too much). After reading the whole thread, really, there are too many posts and very little information...
1. I still don't understand whether the problem is the node not getting the right term or the path not being the right one for the term.
1. Which kind of field we are talking about (field settings, widget, etc..)?
2. Which language (interface) are you using to edit the node?
3. Pathauto? How is it related to this? Is it the node not getting the right term? Only pathauto? Both? Or is it just not using the right (translated) name for the term.

Btw, about tagging it is just not working #1085190: Make taxonomy autocompletion work / tagging / block tagging ?
And about pathauto, maybe the issue is here, https://drupal.org/project/issues/i18n?text=pathauto&version=7.x

batigol’s picture

batigol commented

Hi Jose. Thanks for your interest. This issue is old so I have test it on clean drupal install (standard) one more time.

Drupal 7.18
Internationalization 7.x-1.7
Variable 7.x-2.1
(Token 7.x-1.4)
(Pathauto 7.x-1.2)

1 - we are speaking of Term reference Field with Autocomplete term widget (tagging) widget - its a standard field in Article content type.

2 - Regional and language » Languages » Detection and Selection:
URL - Determine the language from the URL (Path prefix or domain).

(Configuration » Regional and language » Multilingual settings » Selection:

Content to filter by language
Select nodes by language - checked
Select taxonomy terms by language - checked)

It doesn't matter which language I use to create/edit/translate the node/taxonomy - the results are the same, believe me I have tried many different things - it's not working.

3 - I don't know its a pathauto bug - even when you translate Vocabulary Name (for example TYPER in FR) when you hover on some tag you see link - mypage/TAGS/tagname and when you choose other language (fr) you still can see mypage/fr/TAGS/tagnamefr. Problem with tagname-0 (same taxonomy name in both languages - translated) link and broken links (non exist one) persist.

EDIT:
This issue is so old that I don't remember correctly all the symptoms but in #9 I have wrote

I wonder why older version of pathauto display correctly translated vocabulary name and newest version is not - it must be some bug in integration between those modules.

and I was right.

With pathauto 7.x-1.0 and 7.x-1.1 Taxonomy term paths Default path pattern (applies to all vocabularies with blank patterns below) change to [term:vocabulary:i18n-name]/[term:i18n-name] path are displayed correctly (TYPER). However in 1.2 there is a problem - you see TAGS all the time. I'm sure it's pathauto fault cause I have test 1.0 and 1.1 version with i18n 1.7 and they are working fine however 1.2 is NOT (http://drupal.org/node/1155132).

I'm sorry I can't be more helpful. And the most important thing - translated tags were working fine on drupal 1.4 and previous versions of i18n. I did discover this issue when I have updated my site to 7.15 (and i18n up from 7.14). My old tags are working, those newly created ones are broken.

jose reyero’s picture

jose reyero commented

@batigol,
Thanks for the update.

Still we need to clean up the scope of this issue:
- Multilingual tagging is just not working, see/move to related issue #24
(If that is the issue we mark this as duplicated).
- If it is a pathauto issue, please try to reproduce it without 'Tagging', using a drop down and please explain it to me clearly. Also see this one because it may be a duplicate too #358722: Node aliases lost/changed when using i18n synchronize translations

batigol’s picture

batigol commented

OK, so for clarifying this out - tagging is not working as it should. If you use tagging pathauto 1.0 and 1.1 are for you (1.2 is not working), but you cannot use same taxonomy name in both languages (mytag in eng and same mytag in fr won't work, it will get mytag-0 url... like I describe above).

Using Check boxes/radio buttons as a widget is working fine. It's a little bit frustrating to create taxonomy, translate it and then add it to the node but it is working. Taxonomy linking with this widget is not a issue anymore. I'm gonna do some live test on this with node save and hope to update my site soon.

Jose feel free to make it as a duplicate, and thanks for you and rest of the members for help.

So fast fix for you page to behave normal is to change a widget ---> structure > content types > yourcontenttype > manage fields > and change a widget that is used with field type term reference to Check boxes/radio buttons.

P.S. One sentence like this on i18n main page would be very helpful for some users that don't know WTF is going one with their taxonomy after the update.

jose reyero’s picture

jose reyero commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

So this is a duplicate, see #1085190: Make taxonomy autocompletion work / tagging / block tagging ?
Added a note here http://drupal.org/node/1114016