Posted by jensen0 on July 17, 2007 at 6:51am
Jump to:
| Project: | CCK Taxonomy Super Select Ultra |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | rconstantine |
| Status: | closed (fixed) |
Issue Summary
I went through CCK TSSU and found it is working very well as a CCK taxonomy field.
My problem is I need a multiple checkbox solution for my taxonomy associations. The situation is that I associcate the taxonomy with the node directly, not through CCK field reference.
So, I am wondering if CCK TSSU can be handle this kind of work, just like Form Tweaker or Taxonomy Super Select do.
BTW, Form Tweaker gives me a corrupt rendered checkbox form and Taxonomy super select just doesn't produce the form transforming thing at my site.
As a CCK field, CCK TSSU works very very. the form rendering is correct and output is neat.
I am holding a great hope to see the great Constantine makes the things happened.
Comments
#1
Thanks for compliment. At some point I may add this feature as an option, but won't make it the default behavior. The reason is that I personally need 'hidden' taxonomy terms. What I mean by this is that by not using the taxonomy_node table (is that the one? I think it is, but maybe it's term_node) I am able to prevent the browsing/listing of a content type that users shouldn't see. However, other modules are able to find and use the taxonomy data from the cck field to accomplish whatever they need.
So I think this is a good feature to add, but it may take me some time to do it. If you or anyone else come up with a patch, I will review it. The functionality I would want is this:
In the admin UI, have a checkbox that says something like "Enable traditional node tagging". This would then add terms to the taxonomy_node (term_node?) table in addition to the cck field table. It would also update and delete terms as required.
I'm marking this as postponed.
#2
Content Taxonomy has the exact feature as you descriped here.
You may want to have a look at it .
Thanks for the replying.
#3
This was a pain to figure out, but easy to implement. At least, it seems to work.
Anyway, I added a checkbox to the content type configuration, so you can enable the tagging per content type, not per vocabulary. Will upload a new release soon.
#4