I have translated my taxonomy vocabularies using the Entity Translation module (tested with alpha 1 and the Apr-08 dev) and the Title module (used to translate the term names- 1.0 alpha 2).
I have a term reference field on the user profile that uses hierarchical select and the dropbox widget to allow multiple selections.
For two+ level deep hierarchies:
When I select a term, the first drop-down menu always shows the terms in English, which is the site's default language. However, if I select one of those terms, the next drop-down menu (second tier) will appear translated properly. The third tier drop-down menu also appears translated properly. The menu for the first tier is incorrectly displayed as the default language rather than the user's language.
Also, once a term is added in the Dropbox, the hierarchy is correct but the first tier term still appears in the default language. Upon saving the profile, the first tier remains in the default language and the rest of the tiers are saved properly in the user's language.
For single level hierarchies using the Dropbox:
The select widget appears in the default language rather than the user's language. However, when a term is added, it is shown correctly in the translated language in the Dropbox view area (unlike the case for two+ level deep hierarchies). Also, it then appears properly after the node is saved.
Comment | File | Size | Author |
---|---|---|---|
#14 | 1563890-entity_translation-14.patch | 5.78 KB | ajFernandez |
#6 | 1563890-entity_translation-6.patch | 5.96 KB | guillaumev |
#5 | 1563890-entity_translation-5.patch | 5.77 KB | guillaumev |
#1 | hobbies_hierarchical_select.jpg | 2.89 KB | ptmkenny |
Comments
Comment #1
ptmkenny CreditAttribution: ptmkenny commentedExample of the problem:
The site should all appear in Japanese, but the first drop-down menu shows up in English. The second shows up properly in Japanese. All of the terms have been translated.
Comment #2
Wim LeersMoving to the Entity Translation issue queue to gather feedback from their maintainers; please move it back once you've answered it.
Q: How does the Entity Translation deal with Taxonomy term translations compared to the i18n modules?
Comment #3
plachWell, ET basically use core field langauge support to provide a different value per language for each field attached to a term (see http://drupal.org/node/1500308 for some more general info). The Title module offers the ability to replace a plain property with a field, thus making it translatable. In the case described in the OP there is a name_field replacing the taxonomy name. i18n_taxonomy instead exploits i18n_string to translate the name and description properties.
Comment #4
plachMoving back as requested.
Comment #5
guillaumev CreditAttribution: guillaumev commentedHere is a patch that should fix this
Comment #6
guillaumev CreditAttribution: guillaumev commentedNew patch, because the last one caused a bug on the taxonomy edit form.
Comment #6.0
guillaumev CreditAttribution: guillaumev commentedadd info about title module
Comment #7
flyingkiki CreditAttribution: flyingkiki commentedHas anyone ever encountered issues as following?
In French content creation page, the hierarchy term reference field shows the French version term label correctly, but after choose on term and click "Add", original version term label (e.g. English term label) displayed under "All selections" area.
Comment #8
claudiu.cristeaThis seems to be the same as in #2252949: Untranslated root level terms. But that fix is straight.
Using single entity load (
taxonomy_term_load()
) for each term is too expensive. What I did in #2252949: Untranslated root level terms is that I loaded all terms once.Can you try that fix and see if fit?
Comment #9
stijndmd CreditAttribution: stijndmd commentedguillaumev's patch 6 causes the same error on term edit form as the number 5 one.
It also doens't fix the issue.
claudiu.cristea's patch that can be found at https://www.drupal.org/node/2252949 works.
Comment #10
claudiu.cristea@stijndmd, if you tested #2252949: Untranslated root level terms and that works for you, why not set that to RTBC? :)
Comment #11
GoldGiven the time that has passed and the claim that it has been fixed by the patch on issue #2252949 I'm closing this as outdated. If this is still an issue please reopen and update the description with detailed steps to reproduce.
Comment #12
proweb.ua CreditAttribution: proweb.ua commentedDrupal 7.65
hierarchical_select 7.x-3.0-beta9
title 7.x-1.0-alpha9+25-dev
entity_translation 7.x-1.0
child term is still not translated
patch #5 after manual patching, it works
Comment #13
ajFernandez CreditAttribution: ajFernandez commentedHi everyone,
I had the same issue as @proweb.ua in #12. After applying the patch #6 manually, it works for me but I still have the issue in the term reference fields in node edit forms. Does this happen to anyone else?
Anyway, I have updated the patch to adapt it to the latest dev release of the module. It is also compatible with the latest stable version of the module (7.x-3.0-beta9).
Comment #14
ajFernandez CreditAttribution: ajFernandez commentedI just updated the patch file to solve some issues with code indents.