My installation of HS works great! However when I go to edit a node the second level of the hierarchy is never selected correctly. It always shows the first option.
This also happens when using HS with views. When you select a first and second option and submit the filter the second option never shows what was selected but it shows the first option always.
Drupal 5.3
HS 5.x-1.4
jquery_update-5.x-1.0
jquery_interface-5.x-1.0
I am using HS with the core taxonomy.
Let me know if you need any other information. TIA!
Shinan
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | category input.JPG | 53.12 KB | Daryljames |
| #13 | category output.JPG | 49 KB | Daryljames |
| #2 | 1196276001953.png | 50.35 KB | skassam |
Comments
Comment #1
wim leersIs multiple select enabled?
Comment #2
skassam commentedI did at one point but since have set to Single. I have attached a screen shot of the configuration for the vocabulary. Thinking it might be a stale cache issue, I cleared my browsers cache and restarted the web server but the same behavior persists.
If you want access just let me know and I will email you the url and login credentials. Thanks!
Comment #3
wim leersMultiple select != multiple hierarchy.
From the screenshot, I can see that you have multiple select enabled. Please send me your login credentials, but I can't test it right now -- I'm in my exam period.
Comment #4
wim leersThe login credentials you sent me are no longer working. Please resend them.
Comment #5
skassam commentedSent them over to you. I reset the credentials to what I told you they would be in the original email. Thanks for taking the time to look into this.
Comment #6
wim leersConfirmed.
I sent you the HEAD version of HS, to see if the bug still exists in that version. I'd swear I've tested this use case and verified it working. Very odd.
Comment #7
wim leersBug persists in HEAD. Will fix this ASAP.
Comment #8
wim leersWhen the "multiple select" (in version 1.4) or "Save term lineage" (newer versions) option is enabled, all terms are saved. However, when they are loaded again, they are not in the hierarchical order. They are ordered by weight and lexicography (alphabet). Hence we need to resort them again to retrieve the actual lineage.
This has been fixed in HEAD, using a simple BubbleSort algorithm.
Comment #9
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #10
Daryljames commentedI can confirm this is still happening in the latest release 5.x-3.0-rc6
Comment #11
Daryljames commentedJust thought I'd reopen this because I'm seeing the same behavior when save term lineage and multiple select is enabled... when viewing output via views...
Comment #12
wim leersThen please provide me with detailed information, i.e. screenshots of the input (through HS) and the output (through Views).
Comment #13
Daryljames commentedI've attached a screenshot of the category selection... and the table view output....
Thanks Wim for looking at this...
Daryl
Comment #14
wim leersThat's because Views doesn't display taxonomy in a hierarchical manner.
Second, I can't provide new formatters for Taxonomy without hacking the views_taxonomy module, which is part of Views. So that's a no-go.
Third, if you'd switch to using Content Taxonomy, you *can* format it an hierarchical manner, because such a formatter is written for it. That *is* possible because Content Taxonomy is a CCK field, for which any module can define new formatters.
Comment #15
Daryljames commentedright on... Thanks wim for the update....
I'll see If I can make content taxonomy work....
Comment #16
wim leersYou're welcome :)
Comment #17
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.