Closed (won't fix)
Project:
Hierarchical Select
Version:
6.x-3.7
Component:
Code - Taxonomy
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 May 2011 at 21:06 UTC
Updated:
19 Mar 2015 at 10:45 UTC
Jump to comment: Most recent
Comments
Comment #1
paulhudson commentedI've the exact same issue. I see you managed to resolve it... care to share? :-)
Paul
Comment #2
paulhudson commentedComment #3
paulhudson commentedApologies, it seems the issue is not resolved for you. I must be tied.
Comment #4
omnia.ibrahim commentedThe module didn't work with already added taxonomy terms, when you change the main category the sub remains the same as the saved value
Comment #5
faridjame commentedWhen I decreased the number of levels to 3, it started to work fine. Check the same link I posted above.
Comment #6
bramface commentedMine worked fine until last week....and I reverted both the database and the codebase (I thought!) to before then and it STILL did not "work"...but it's possible that it's a user error and I just don't see something....
Basically, it's a two-level hierarchy, and the second level list DOES load when the first is selected, BUT the element is given "display:none" so I can't see it.
I vaguely remember some setting somewhere where you could determine what level to display and force the hiding of the second...but I can't find that now, and as I said, I restored the DB from an earlier version and had the same issue.
Gosh, it's frustrating!
Comment #7
stefan.r commented6.x issue without activity for over 3 years, closing.
Please reopen if this is still an issue in 7.x.