Second Hierarchy is not working [#1167726]

I'm not sure if this is a bug, or if I'm doing something wrong, but I have enabled Hierarchical Select for my "Catalog" vacabulary, but I cannot select any item from the second tier.

To reproduce:

1) go here http://bazanoo.com/
2) on the left sidebar, under "Find your product:", from the first drop down, select "manufacturer"
3) from the second drop down, try to select anything but "Brother"

Expected result: your selection should appear

Actual result: does not let you select anything but "Brother"

Comments

Comment #1

paulhudson CreditAttribution: paulhudson commented 25 May 2011 at 20:42

I've the exact same issue. I see you managed to resolve it... care to share? :-)

Paul

Comment #2

paulhudson CreditAttribution: paulhudson commented 25 May 2011 at 20:51

Category:

bug

» support

Comment #3

paulhudson CreditAttribution: paulhudson commented 25 May 2011 at 20:58

Category:

support

» bug

Apologies, it seems the issue is not resolved for you. I must be tied.

Comment #4

omnia.ibrahim CreditAttribution: omnia.ibrahim commented 26 May 2011 at 09:46

The 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 CreditAttribution: faridjame commented 26 May 2011 at 22:32

When I decreased the number of levels to 3, it started to work fine. Check the same link I posted above.

Comment #6

bramface CreditAttribution: bramface commented 27 May 2011 at 12:22

Mine 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!