Using HEAD. Right now if i have a Vocabulary with 3 levels
Level A
-Level B
--Level C
- I create a new node and tag with the deepest Level C term (saving all the path)
- I get Level A > Level B > level C
- I change this node and tag with Level B term leaving the Level C empty
- I get Level A > Level B
- I change this node and tag it with
<none>in the first Level A - I get Level A > Level B
- I change this node and tag it with
Labelnamein the first Level A - I get Level A > Level B
- I change this node and tag it with
Labelnamein the Level B - I get Level A
its seems its impossible to get rid of the Level A tag.
Comments
Comment #1
wim leersThanks for the bug report. I'm working on multiple select support first, then I will start the bugfixing.
Comment #2
wim leersI'm fairly sure this bug has been fixed by the last commit. Please verify.
Comment #3
derjochenmeyer commentedI took a fresh CVS Version of hierarchical_select.js and hierarchical_select.module
Still the same behaviour. I cant get rid of the first level tags. Chosing
<none>orlevel labeldoes nothing to existing tag.Expected behaviour would be to remove all tags from the node.
Comment #4
wim leersReproduced.
Comment #5
derjochenmeyer commentedi think it might be a bug in the js function
HierarchicalSelect.updateOriginalSelect = function(hsid) {when nothing is selected the option with value="" is not selected because the values dont match with "none" or "level_0". so nothing is changed and the tags are not removed.
Comment #6
derjochenmeyer commentedsorry i changed the Status without intention.
Comment #7
wim leersI just fixed in the case of "none", but forgot to fix it for the case when labels are selected.
Follow-up will come soon.
Note that this is actually not a real bug, but an anomaly of Drupal core's Taxonomy module, and how that works. If nothing is selected, it *should* select nothing, but instead, it keeps the previous selection.
Comment #8
wim leersVoila, also fixed.
Comment #9
derjochenmeyer commentedWorks :)
Comment #10
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.