Closed (fixed)
Project:
Hierarchical Select
Version:
5.x-2.1
Component:
Code - Taxonomy
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
14 Feb 2008 at 12:47 UTC
Updated:
17 Apr 2008 at 19:32 UTC
Hi, this module is so great !
I have a vocabulary with 2 level of hierarchy and each terme is translated in french and in english.
The first time I choose a terme in my vocabulary when editing a node, It is ok and I only see the terme in the language selected.
However If I decide to change my first level of hierarchy and to explore another branch, then the terms in both langages appears in the select list of the first level.
Is my description of the bug clear enough ?
Comments
Comment #1
wim leersI have no idea what would cause this bug. I *always* use Taxonomy's API in the HS implementation of Taxonomy. So where things could go wrong … no idea.
You'll have to start digging yourself, I have no translated site around for testing. If you can tell me where the cause lies, I'll fix it.
Comment #2
julma commentedThanks,
I will do my best.
I have tried also today the second methode to translate taxonomy terms, I mean with localization interface as noticed in the comment following this thread http://drupal.org/node/133999
But in this case, another strange behavior happen : when I go to admin/settings/i18n/translation and I set a vocabulary to be translated, then the hierarchical select widget disappear in the node edit form and instead I can see only the normal select field...
I may also notice the conceptors and maintainers of the I18 module by posting a link to this thread in their issue queue.
Maybe they have a idea to solve this problem of compatibility.
Comment #3
wim leersCould you provide me with FTP + Drupal admin access to your site? Then I could find out how to alter forms that use the translated vocabulary.
Comment #4
wim leersI was in contact with julma via e-mail and it seems he's using the i18n + i18ntaxonomy modules to translate the content of the Taxonomy module. The i18ntaxonomy achieves translated form items by overriding them, the same way Hierarchical Select does. But the weight of i18ntaxonomy is heavier (20 versus 0), so it runs after HS, thus it overrides changes made by HS.
What's necessary to fix this?
- Make sure that the weight of HS is heavier than i18ntaxonomy.
- Alter the taxonomy and content_taxonomy implementations of HS to support the i18ntaxonomy module.
This won't make it into the HS 2.0 release.
Comment #5
wim leersComment #6
wim leersComment #7
wim leersIn version 2.2, the first method of translation (i.e. without the localization module) is working out-of-the-box for me.
The second (through the localization module) is indeed generating a normal select. I'll work on fixing that.
Comment #8
wim leersFixed. See http://drupal.org/cvs?commit=107231.
Comment #9
wim leersSeems it's not working entirely yet: it's still using the original terms. I forgot to wrap the term names in t() calls. Fixed that now. See commit http://drupal.org/cvs?commit=108126.
Comment #10
wim leersIt's been confirmed by julma: it's working fine now. I'll tag a 2.2 release later tonight.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.