As I reported here http://drupal.org/node/225740

When enabling Taxonomy context I cannot ad terms to nodes using Hierarchical Select. I am told this is because TC is somehow hijacking the form.

I noticed this also affects term selection using exposed taxonomy filters on views.

Disabling TC and everything works again.

I'm using Drupal 5.7 and the latest release candidate for Hierarchical Select.

Comments

lee20’s picture

lee20 commented
Category: bug » support
Status: Active » Closed (fixed)

Taxonomy Context isn't doing anything non-standard or "hijacking" any forms. Taxonomy context does absolutely nothing to a node form or the submission of a node therefore the incompatibility lyes elsewhere. The fact that it works when you disable Taxonomy context I believe is coincidence and misleading you from the true problem.

I tried HS and couldn't get it to work with or without Taxonomy Context therefore it seems to be an issue within HS or one of their sub modules. Also, Taxonomy Context has absolutely no interaction with views filters therefore that is also not an issue caused by Taxonomy Context.

I installed HS on a fresh Drupal 5.7 install, added a vocabulary and some terms, and checked the "Required" setting. When trying to add a page I couldn't get past the validation telling me that it is required. Disabling the requirement obviously let me add the page, but the term lineage was not saved and not preselected when I tired editing the page. This was without Taxonomy Context even installed.

Wish I could help more, but this is a problem with HS and not Taxonomy Context.

Jeff Burnz’s picture

Jeff Burnz commented

The hijacking sounded weird to me to also, I cant see in Taxonomy context anything that goes near a form, that's just the feedback I got when I posted the same issue in the HS bug queue.

Thanks for taking the time to try and replicate the issue, much appreciated.