Reported here: http://drupal.org/node/276142. New issue for clarity.

Comments

vacilando’s picture

Subscribing.

wim leers’s picture

Observation: 2 content_taxonomy fields, both using the same vocabulary, both configured to use "save as tag", both using a "Select list" as widget (as opposed to Hierarchical Select). If you select term A for the first field, term B for the second field, then:
- on display, for each field, both term A and B are selected, so it seems as if FOUR terms are selected simultaneously
- on edit, the same term is selected for each field (in my case term B was selected twice, the one with the lowest weight)

So this really is a "bug" in content_taxonomy, but I doubt this can be done any better; this is what you need "save as both" for.

wim leers’s picture

I messed with this for more than 2 hours and couldn't get it to work.

I had a content type with a field in no field group, and one field in a field group. As soon as I moved both of them both out of any field group, it stopped working: only one of the fields would show. So it seems content_taxonomy itself doesn't support this! It didn't even work when I changed the widget to "Select list". When I move them both into the same fieldgroup, it seems to work when using "Select list".

I can't even begin to express how much I hate this module…

wim leers’s picture

I.
Got.
It.
Working.

Woot. One less thing users will keep nagging about. Now you can choose the "save option" yourself again!

wim leers’s picture

Title: Problems when a node type has multiple content_taxonomy fields that use the same vocabulary » Support for the 'both' and 'cck' "Save options" of Content Taxonomy fields
Status: Active » Fixed
vacilando’s picture

Proficiat, Wim. Amazing effort, and result!

So could you share what exactly have you done to fix this? Did you go around content_taxonomy's imperfections (filing a bug with that module?) or did you eventually realize there was something to fix in HS? Do you now recommend setting 'both' in CCK for this to work, or only 'as tag', or only in 'CCK table'?

Which module did you hate in #3? :-)

wim leers’s picture

Find the CVS commit that matches this node (#277780) for details. You'll see that the added code doesn't make much sense.

I recommend 'both' for maximum compatibility with other modules that integrate with it (e.g. Token).

I hated content_taxonomy in #3.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.