Hi,

I use this excellent module since 5.x and I already submitted an issue some times ago about hidding the taxonomy select list when content taxonomy is enabled for a content type : see the post. After the patch provided, it worked great.

I'm testing the 6.x branch of content taxonomy, and I have the same issue. I enabled content taxonomy field, configured it (I enabled save in node_term table), and when I go to create my content type, I see both core taxonomy form and the content taxonomy one.

It is a known and wanted behavior or is the 6.x update broke it ?

thanks

zmove

Comments

zmove’s picture

zmove commented

Any news about it ? Am I alone to have this problem ? Do I miss an option to hide taxonomy field ? Am I alone to use the 6.x version of that module ?

pingers’s picture

pingers commented

afaik you need to disable the standard taxonomy for that node type.

Hope this helps,
Michael

zmove’s picture

zmove commented

Hi,

I had the same answer in the first issue for D5 I created some times ago, but I don't like the idea to do that to make it work.

It will break the association between the taxonomy and this content type, and so, it can break all others modules related with taxonomy that would need this association.

That's why I find that is far better and logic to remove the taxonomy field if content taxonomy is enabled with that content type (with a hook_form_alter I imagine) that tweaking taxonomy options like that.

pingers’s picture

pingers commented

You forget that you can choose to save terms in the term_node table using content taxonomy module.

It's a life saver! :)

zmove’s picture

zmove commented

Yes, this is what I done, the content taxonomy successfully save the term in the term table.

But if I go under the vocabulary page to remove the node type for which I want to hide the core taxonomy select list when I edit a node, Imagine I need a module that list content type depending on a vocabulary... the fact to disable this option would break the module that will be unable to list these content type because they are not associated anymore with the taxonomy vocabulary.

That's why I think it's better to hide the taxonomy select form by implementing a hook_form_alter than remove the association between the vocabulary and the content type in taxonomy administration.

Maybe there are no influences at all, but I'm not expert enough in drupal to affirm that, that's why I need some guru opinions ^^

Hyper-1’s picture

Hyper-1 commented

I'd also like to know if not associating a vocabulary with a content type makes a difference further than what I initially thought was to create a association to merely restrict the adding of terms to inappropriate content types.

mh86’s picture

mh86 commented
Status: Active » Closed (duplicate)

this issue is duplicated to http://drupal.org/node/267622. I fixed the problems by adding an setting to hide the default taxonomy fields. Now, it's optional to hide or show the default taxonomy fields, independent from the vocabulary settings and the associated content types.