I've enabled the module and configured it on the corresponding vocabulary, but when I go to the edit node form or create node form, the original taxonomy selection box is not being replaced with the hierarchical select box. I´m using Drupal 6.14 and the dev version from 2009-Oct-19

Is there anything I'm doing wrong? any tip? how can I make it work?
Do you know when will the 6 version go on a stable version?

Sinceresly thanks

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

There must be another module overriding it.

Can you reproduce this on a vanilla Drupal site? If you cannot, keep on adding modules that you're using on your actual site until the problem is reproduced.

When you're able to reproduce this (on a vanilla Drupal site with the minimum number of modules to reproduce it), then please make a screencast of:

  1. your site configuration
  2. the problem being reproduced

That makes it easier for me to reproduce the problem. Thanks!

P.S.: don't have any screencast software yet? On Windows and Mac OS X, you can use the free Jing.

mairav’s picture

mairav commented

I installed it on a fresh site and it worked. I'll check disabling module by module, to see which one is making this to fail.

Is there any way the module can remember the which hierarchy was selected if a term has multiple parents?
Will you launch the stable release any time soon?
It's safe to install the dev version on a production site?

I'll anwser here when I discover the module making troubles.
Thanks!

mairav’s picture

mairav commented

mmmm, I found it. It's not a problem with some module.
I have two vocabularies, one needs no translation, as they're company names, and the module works there.
The other has the option "Localize terms. Terms are common for all languages, but their name and description may be localized." and with that option checked, the module is not working. If I check the vocabulary as "None. No multilingual options for this vocabulary." the selecion works.

As I read, this was solved in #341993: Hierarchical Select: use the special translation function provided by the i18n module but I have the dev release of 2009-OCt-19 and doesn't work for me. Do I have to something else?

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Title: Hierarchical select not showing on edit/create node » HS not showing on form for vocabulary that uses localization
Component: Code » Code - Taxonomy

Is there any way the module can remember the which hierarchy was selected if a term has multiple parents?

Yes, enable the "save lineage" setting.

It's possible that the i18n support of HS is not flawless. Drupal + i18n/l10n is a hornet's nest, to be honest … I'm afraid can't help you with that until you provide very detailed information. I don't have the time to build a test site with translations.

mairav’s picture

mairav commented

If I check the save lineage it saves the parents, but if a term has multiple parents and I select to lineages, with end terms that shares parents, It makes mistakes. For example. Term "a" is parent of term "c" and "d". On the other hand Term "b" is also parent of term "c" and "d". If I select:
a > c
b > d

The final result is:

a > c
a > d
b > c
b > d

Four lineages instead of the two I selected.

Maybe I'll finally won't need the module cause my customer request a change of plans in the way the content is organized. If I finally use it, I'll give you all the information you need to fix it. It's a great module and would be great if it works with translations.

Thanks very much.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

From the README:

Limitations
-----------
<snip>
- In hierarchies where items can have multiple parent items and where you have
  enabled Hierarchical Select's "save lineage" setting, it is impossible to
  remember individual hierarchies, unless the underlying module supports it.
  So far, no module supports this. Hierarchical Select is just a form element,
  not a system for storing hierarchies.
  For example, if you have created a multiple parent vocabulary through the
  Taxonomy module, and you have terms like this:
   A -> C
   A -> D
   B -> C
   B -> D
   If you then save any two lineages in which all four terms exist, all four
   lineages will be rendered by Hierarchical Select, because only the four
   terms are stored and thus there is no way to recover the originally
   selected two lineages.
mairav’s picture

mairav commented

Yes, I read that, but I was asking if there is any way that the module can be modified to remember the two selected lineages.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

No, there isn't:

it is impossible to
  remember individual hierarchies, unless the underlying module supports it.
  So far, no module supports this. Hierarchical Select is just a form element,
  not a system for storing hierarchies.

It's technically impossible. And not HS' task. Sorry.

mairav’s picture

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

Ok, thanks.
You can close this issue if you want. It would be great that it works with sites selecting the "localize terms" option for translations, but as there are other posts with this problem, I'll talk in them later if I finally use for this multilanguage site the module.

Thanks again for all your answers!