Selecting the hierarchical select widget input option with 'Save term lineage' selected results in content taxonomy field input not being saved. I don't know for sure if this is a bug with HS or with Content taxonomy, a mis-configuration on my part or maybe an incompatibility issue between the two modules.

If anyone is interested in providing some paid support I've posted a request here: http://drupal.org/node/363560

Comments

plan9’s picture

plan9 commented

If somebody takes up this offer of paid support I will release any patch necessary to make these modules work together back to the community.

kobnim’s picture

kobnim commented

Wondering ... have you figured out how to save the lineage? I am having the same problem (with version 6.x).

plan9’s picture

plan9 commented

No, it's still broken I'm afraid.

mullman’s picture

mullman commented

I just upgraded to 6.x-1.0-rc1 and I'm having this problem too. Any ideas on a fix?

It appears to be saving only the very first term from the list. For example, my form uses hierarchy to first choose the state and then the city within that state. The selection process works fine. I was able to choose Wisconsin and then La Crosse but when it saves the node Alabama is the value stored (the first option in the taxonomy list). I need to be able to store the lineage because some states have duplicate city names, for example, Onalaska, Wisconsin and Onalaska, Texas.

mullman’s picture

mullman commented

Has there been any movement on this?

marcoka’s picture

marcoka commented

subscribe :)

jibort’s picture

jibort commented

I still have a problem related to this.

I have a CCK field "zone" of type Content Taxonomy. The field is displayed with Hierarchical Select.

When I edit the node form all works well, but when I use that field in the Registration Form (with Content Profile), the field apears well but when I submit the data is not saved.

Any solution,

thanks !!

magnus’s picture

magnus commented
Status: Active » Closed (won't fix)

Cleanup of old issues. According to maintainer: "active development is only done for the 6.x branch! 5.x is not supported any more".
Reopen issue if problem still exist in 6.x branch.

baff’s picture

baff commented

subscribe

Vishakha’s picture

Vishakha commented

I have the same problem. I have enabled the option 'Save term lineage' in my vocabulary, my content_taxonomy field related to this vocabulary term does not save the lineage. I tried disabling 'Multiple select' but it did not work. I have multiple parent terms in my vocabulary. Does it save lineage when there are terms with multiple parents?

fp’s picture

fp commented

Here's something that might be useful: https://drupal.org/node/976394#comment-5516004