This is a really useful module! I believe most people need something like this!
What I need, is to enable multiple selection. My vocab is like this:
World
-- Africa
---- South Africa
------ Botswana
-- Americas
---- North America
------ Bahamas
------ Barbados
------ Canada
------ Costa Rica
------ Mexico
------ USA
---- South America
------ Argentina
------ Brazil
-- Europe
---- South Europe
------- Greece
...........and so on
If I enable multiple selection I can choose what I want, everything is OK but when I save the node, ALWAYS the terms World, Africa, South Africa, Botswana are kept no matter what I choose. Probably because this is the first tree path available. If I disable
multiple selection, the correct term is saved but only the last child is kept (this is by design as I understood). Practically and because this module can solve many problems I can propose the following:
1) A "none" option is essential for EVERY child level. I have seen that many people ask for it. It is very meaningful to be able to choose simply World, Europe, South Europe without being forced to select a specific country (e.g. the first in the list which is wrong). In case the "required" option is disabled, the "none" option should be there at the root level too, but that happens anyway I believe.
2) Somehow a check-box "save all terms path" should allow the admin to choose if he wants all terms saved or just the last child. This is irrelevant with the multiple selection option and is useful anyway.
3) Multiple selection can be as designed, but without the problem described above.
4) Real multiple selection can be useful too. Some might want to tag an article with World, Europe, South Europe, Greece AND World, Asia, Middle east, Turkey if their article is relevant to both Greece and Turkey. Normally the "save all terms path" option would be disabled here.
General comments: I believe that 1, 2, 3 are more important. No 4 might be difficult to implement and therefore too much to ask! I am relatively new at Drupal... I can see it is very powerful, the functionality is there but the User Interface is NOT there. Feels like having a perfect shotgun but without bullets!!!!
Thanks for the module anyway.
Comments
Comment #1
derjochenmeyer commentedI discovered a similar problem:
Used Versions
- drupal 5.3
- as well as drupal 5.4-dev as of November 10th 2007
- Hierarchical Select 1.4
Scenario I:
- vocabulary "Required"
- "Single Select"
expected behaviour: only top-term gets stored and is remembered the next time i go to the edit page.
=> everything works fine
Scenario II:
- vocabulary "Required"
- (!) "Multiple Select"
expected behaviour: the top-term and the term-path get stored and are remembered the next time i go to the edit page.
=> Part one works, the term-path and the top-term are stored
=> Part two is broken: returnig to the edit page preselects the first branch of the taxonomy tree (as term-path), no matter was selected before
=> saving without correcting the wrong term-path saves the new "wrong" path plus the previously selected top-term
Comment #2
palazis commentedAny news on how to resolve this?
Comment #3
wim leersI can't reproduce the basic problem you describe (that the first available term path is selected).
1) See this issue: http://drupal.org/node/189975
2) Has just been implemented (get the dev tarball within 4 hours or get it from CVS)
3) I don't understand what you mean.
4) You can sponsor it. The issue for this feature is: http://drupal.org/node/191806
Comment #4
wim leersComment #5
palazis commentedWell, issue discussed on http://drupal.org/node/189975 might be similar.
Difference No 1: His vocab uses multiple hierarchy, mine uses single hierarchy.
Difference No 2: He ends up in an infinite loop, if I understood well. I end up with the first available tree path being saved, instead of the term I chose being saved. I think this is clear enough.
I believe that derjochenmeyer discusses about a problem which is similar than mine.
Anyway I would be glad to test the new dev version, when it comes. I had no answer here, so I had to disable the module because of this problem. In any case I can enable it again, or try to install the new dev in a test site.
Despite this problem, in my previous comment I was generally referring to multiple selection and some of my ideas... That's another issue. You see my idea of multiple selection is to be able to choose many terms from a vocabulary. Your idea of multiple selection is to be able to choose and save all terms from the same tree only. In other words, I want to be able to press Ctrl + Click and select 2 or 3 terms, the way core taxonomy module normally behaves. Or in another case I want to be able to choose just one top-level term, the way core taxonomy module can. My opinion is that a contrib taxonomy module should do what core taxonomy module does and extend it somehow. But of course other opinions are also appreciated.
Thank you.
Comment #6
palazis commentedTitle change.
Comment #7
wim leersUhm okay, I guess I should read that issue again in more detail.
But you should too ;) The issue I'm referring to for point 4, really is about "true multiple select". Please continue your multiple selection questions over there!
Comment #8
Eugene Fidelin commentedI have the problem #2. I download the dev tarbal, but it didn't work at all (i mean it doesn't repace default select with hierarchical one)
Comment #9
wim leersThen you didn't install the module properly, Eugef. Make sure it's enabled at admin/build/modules.
Comment #10
Eugene Fidelin commentedI install HS properly - version 1.4 works.
But when i install dev-version - it doesn't!!!
Comment #11
wim leersMaybe you installed the old dev version. Not sure though.
Comment #12
Eugene Fidelin commentedI install dev version, which is dated "2007-Nov-20"
Wim Leers, it would be greate if you do a new release of your greate module!
Comment #13
Encarte commentedSeems a great module, indeed. The demo is very convincing (ant it leads to other interesting works of this developer). Since it still has some bugs, I'll be waiting for the 1.5 before installing. Hope it comes soon!
Comment #14
wim leersThe wrong path being selected on loading has been fixed in HEAD. This was a bug by design of the previous version of HS.
What you can find in HEAD is still in flux, but works very well, and is what will become version 2 of HS (yes, new features too). Feel free to test it and report back here.
Comment #15
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.