Use Content Taxonomy field and the Taxonomy vocabulary that is exposed to it
| Project: | Content Taxonomy |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi,
This module has been great for me so far and has helped me implement one of the most important features of my site. I've listed this as a feature request since I'm not sure if I'm currently able to do it, feel free to correct my mistake if I'm wrong.
Is it possible to have both the Content Taxonomy field and the Taxonomy vocabulary that is exposed to it available on the same content type? It seems to me that its either one or the other, but not both. I'm using the Taxonomy Super Select module and if I have TSS on the Taxonomy vocabulary, then both the CT field and the vocabulary appear on the create content form. I would like, however, to allow both the CT field and the Taxonomy field to be able to add tags to the content (ie add to term_node table). Unfortunately however at the minute I don't believe I can do this.
Would it be possible for me to achieve this functionality?
Thanks
#1
I've done some studying and I've come up with a solution to my problem.
I've set the CT field to NOT add tags to the page. I've then written a simple module which uses hook_nodeapi() to, on submission of the node edit form, take the tid value from the CT field and insert it into the term_node table in the database with the nid for the particular node which is being created. This adds the tag associated with the tid in the CT field to the page, without that option being selected in the CT field settings. Since the option is not selected, the taxonomy that is exposed to the field can still add its own tags.
I've tested this out quite a bit on my site and it works fine. Though I think it will only work with Taxonomy Super Select enabled for the vocabulary in question, since I haven't figured out how to get both the CT field and its exposed taxonomy to show on the node edit form at the same time.
I'm not sure if this is the best solution but it achieves the functionality that my quite particular case called for. I'll set this to fixed, but if any one in my previous situation would want to talk about what I did then I'd be happy to.
#2
Automatically closed -- issue fixed for 2 weeks with no activity.