Closed (won't fix)
Project:
Hierarchical Select
Version:
5.x-2.0-rc4
Component:
Code - Taxonomy
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
23 Feb 2008 at 15:05 UTC
Updated:
23 Feb 2008 at 16:21 UTC
Enabled HS for a single hierarchy vocab. Vocab is required.
Created node, attempt to add a term using HS.
When previewing or attempt to submit I get the error "For-sale field is required." (for sale is my vocab).
Making the vocab not required makes no difference, the term is never attached to the node and all forms are reset when going back to edit the node.
I reproduced this on two seperate sites.
The actual AJAX drop lists work fine, and look good. However, this is the first time I have used this module so I am not entirely sure what the default screens should look like. It also seems to be very slow at returning each level of the hierarchy, considering it is not a large vocab, with only 50 or so terms in total.
Running on Drupal 5.7 (both sites)
Site one theme: Zen Classic
Site two: custom theme
Comments
Comment #1
Jeff Burnz commentedOk, the lightbulb went on, I have Taxonomy Context module enabled on both these sites, disabling Taxonomy Context solves the issue.
In addition HS is working 10x faster and an annoying display bug where the second level partially obscured the fist level has gone away (I thought this might be a theme issue so I did not mention it.
Be great to work this out as both modules are great.
Comment #2
wim leersWell, you should ask the developer of Taxonomy Context then: HS can't be held responsible for modules hijacking the form.
About the perceived slowness: that's a performance issue of your site and/or server. Both on http://wimleers.com/demo/hierarchical-select and locally it works really fast.
Comment #3
Jeff Burnz commentedYeah, I'll report it over there once I get a bit more debugging done. Thanks.