The community tagging form appears on nodes whose type is NOT set for the community tagging vocabulary.

The form appears to allow users to tag these nodes.
This is incorrect -- if the vocabulary is not set on this content type, it shouldn't be possible to tag nodes of this type from this vocabulary.

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: doesn't respect vocabulary settings for content types: able to tag node types not in vocab » It doesn't respect the content types vocabulary settings
joachim’s picture

joachim commented

Basically, hook_nodeapi needs to check the vocab applies to the current node, the same way hook_menu does.
I would suggest moving this out to a helper function to check that community tagging is required for the given node.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I agree; it is the only way for the module to operate correctly.

If the module must show its form fields only on nodes which are associated with a specific vocabulary, then it must check if the node hook_nodeapi() received like argument has any taxonomy term of that vocabulary.

chaps2’s picture

chaps2 commented
Status: Active » Closed (won't fix)

Not an issue in 6.x and #1068648: Community Tags 5.x no longer supported so closing.