By the way, I have a simple question about this module.
That is, when creating an node with this module, it seems to me that we have to apply "taxonomy" and "cck taxonomy field" to the node seperately.
If it's true, I personally think it is not a sophisticated manner, and just wonder what the point/benefit of this module.
Ability to group the fields of taxnomy terms?

Please help.

CommentFileSizeAuthor
#2 image1.gif90.29 KBryo

Comments

robertdouglass’s picture

robertdouglass commented

The goal of this module is to use the lists and hierarchies built by taxonomy module as CCK fields. Other than the list building (vocabularies and terms), there is no overlap in functionality between this and taxonomy. It does not replace taxonomy. It just uses the list building functionality.

ryo’s picture

ryo commented
StatusFileSize
new image1.gif90.29 KB

Forgive me if my wording bothered you.

The goal of this module is to use the lists and hierarchies built by taxonomy module as CCK fields.

Yes, I think I understand it.

My question is regarding the content creation process.
Please see attached file.
Above "module categories:" is of taxnomy modules.
Below "module categories by CCK Taxo:" is of CCK taxonomy fields.

Do I have to select taxonomy terms twice?
Or do I get a wrong idea?

robertdouglass’s picture

robertdouglass commented

Aaah, I understand the question now. The CCK Taxonomy module does a special trick to your vocabulary form and allows you to select zero content types to be associated with the vocabulary. It is normally required to select at least one content type. When I use this module, I don't associate the vocabulary with any content types. That way only the CCK Taxonomy form, and not the taxonomy.module provided form appears on the node creation page.

ryo’s picture

ryo commented

Ah! Now I understand the trick now!
I didn't even imagine it allows us to select zero content types to be associated with the vocabulary.
I tried it just now and confirmed the fact.

Anyhow, I think it would be better to add this trick mechanism onto the module description page :-)

regards,

robertdouglass’s picture

robertdouglass commented
Status: Active » Fixed

I'll update the docs. Thanks for your feedback.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
sgdev’s picture

sgdev commented

Ah fantastic ... glad I found this. Was spinning around in circles trying to figure out why I had two sets of select boxes. :)

Just to make sure, there are no other impacts to Views or Categories by not having a Content Type set on a vocabulary?

merilainen’s picture

merilainen commented

Of course there is. It seems that this module only enables to show a certain taxonomy term in the node where you want it. If you don't associate your node type with any taxonomy, then your node will not have any connection to the taxonomy -> you cannot list nodes by taxonomy. Am I right?