Title says it all. Working on fixing this.

Comments

vacilando’s picture

Subscribing ( taking into account what you wrote at http://drupal.org/node/275876#comment-899861 ).

wim leers’s picture

Status: Active » Fixed
vacilando’s picture

OK, great!!

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

akin.demirci’s picture

Version: 5.x-3.x-dev » 6.x-3.x-dev
Status: Closed (fixed) » Active

I see that "root term" (now called "parent term") setting is not fully supported.
The selet list is displayed as expected, but when I try to add new term to that level (not level-0 because the "parent term" option is used in the cck field setting), it adds the term to the level-0 of the vocabulary, it does not recognize that it is actually level-1 of the vocabulary.
This bug can be seen in the "Per-level settings for creating new terms" too. When "parent term" option is used in the cck field setting, the root levels of the vocabulary itself and the select list displayed is mixed up.
Can you fix that too?

akin.demirci’s picture

I found a fix like this: changed line 1015 of hierarchical_select.module
$parent = ($depth > 0) ? end($selects) : 0;

I've changed this line to:
$parent = ($depth > 0) ? end($selects) : $config['params']['tid'];

could you please check it out?

YK85’s picture

Status: Active » Needs review
chuckbar77’s picture

subscribing

freestone’s picture

In Add Term I no longer have the option of picking the parent of the term being added with this modules active.

I tried the above code changed but it did not fix the issue for me.

wim leers’s picture

Status: Needs review » Closed (won't fix)

The change in #6 is severely flawed. Changes should be made to hs_content_taxonomy.module, not to hierarchical_select.module. And most definitely no changes to hierarchical_select.module that are not generic: the changes proposed by akin.demirci only work for the content_taxomy module, and even then probably only in certain cases.

See the updated project page:

Note: the Content Taxonomy module integration is no longer supported. Patches are accepted and committed, but the maintainer does no longer want to fix bugs with this integration. The reason is simple. It's a nightmare. It makes one suicidal. Content Taxonomy is rotten. It needs to die. Thank god it won't be necessary to port this functionality to Drupal 7