Since the node is not automatically tagged with the term it's related to, I do not see why the vocabulary would need to be applied to the content type associated via Taxonomy Node to that vocabulary.
In my case I have 4 vocabularies I am using Taxonomy Node on, (all the same content type)
but I do not want these nodes to be tagged with any terms from those 4 vocabularies.
I can simply not tag them, but for user ease of use it would be nice to not include them on the node edit page.
Comments
Comment #1
ccshannon commentedAgreed. This 'feature' makes no sense. Why would I want to tag nodes with terms that represent the same nodes' node type???
For example:
- I create a Vocabulary called 'Colors' - Free Tag type
- I create a Node Type called 'Color'
- I create a Node Type called 'Car'
- Using Taxonomy node settings, I set 'Colors' Vocabulary to associate with Node Type 'Color'
- I want to apply terms from 'Colors' Vocabulary to nodes of type 'Car'
- When I save Vocabulary settings, the list says that 'Colors' applies to both 'Car' and the Node Type 'Color'
- Indeed, when I go to create a new 'Color' node, there's a Free Tag form for 'Colors' ... BUT I DON'T WANT THAT --> the ONLY node form that the 'Colors' field should appear on is the 'Car' node form.
- I try unsetting the 'Color' node in 'Colors' settings ... But it keeps coming back.
Unless someone has good reason for this, I would consider this a bug. There is no need for the Vocabulary settings to do this, for the rest of the module to work. Why would I want to apply a 'Colors' term, to a 'Color' node??? That makes no sense. They are synced versions of each other, not meant to applied to one another.
I guess the proper thing would be to use form_alter to hide the 'Colors' form field from the 'Color' node form.
But I also intend to look at the code and perhaps patch it, unless of course this setting business is required for the module to work properly. form_alter will hide it from my users.
Comment #2
heathergaye commentedsubscribing