Content Taxonomy seems like a great way to replace the standard way that a vocabulary terms are selected at node creation. I like that it doesn't group all the taxonomy selection fields into one section like Taxonomy does. Even if I don't really need a CCK field that stores my taxonomy information (for example, if I only need Content Taxonomy to store the selected items in the Taxonomy table), I'm thinking about using Content Taxonomy as a replacement for the standard vocabulary selection on my content types. It just looks like a nicer form when there are multiple taxonomies used on a single content type.

Is this a proper use of Content Taxonomy? Will I encounter any problems later?

(I'm running Drupal 6.)

Comments

nevets’s picture

nevets commented

I think so. I like that you get to chose the input widget, easier to theme and you can limit the depth of terms.

dmetzcher’s picture

dmetzcher commented

Yes, and with hierarchical select being one of the options (if that module is installed), it does anything that Taxonomy can do, and more.

dmetzcher’s picture

dmetzcher commented

Any other thoughts on this?
I'm about to implement it on my site and wanted to know what others thought about any possible issues, etc.