Closed (won't fix)
Project:
Hierarchical Select
Version:
6.x-3.x-dev
Component:
Code - Content Taxonomy
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
28 Jun 2008 at 11:57 UTC
Updated:
5 Feb 2011 at 15:18 UTC
Title says it all. Working on fixing this.
Comments
Comment #1
vacilando commentedSubscribing ( taking into account what you wrote at http://drupal.org/node/275876#comment-899861 ).
Comment #2
wim leersComment #3
vacilando commentedOK, great!!
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
akin.demirci commentedI 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?
Comment #6
akin.demirci commentedI 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?
Comment #7
YK85 commentedComment #8
chuckbar77 commentedsubscribing
Comment #9
freestone commentedIn 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.
Comment #10
wim leersThe 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: