Currently, the vocabulary form requires all vocabularies to be associated with nodes. This is unnecessary and curbs the usage of the taxonomy module in implementations that do not involve the node system/form.

Thanks
-K

CommentFileSizeAuthor
taxonomy.patch.txt680 bytesZen

Comments

Zen’s picture

Zen commented

Example use case: Use the taxonomy system as an hierarchical menu system (in tandem with the description field), with multiple parents etc. etc.

My own use case stems from the use of the NAT module and indulging in some magickery with associating the taxonomy image module with a node.

I believe that this is an innocuous changes and increases the flexibility of the taxonomy system.

Thanks
-K

Jaza’s picture

Jaza commented

+1.

This will definitely make the taxonomy module more flexible. The category module already has this field as non-required, and when using the taxonomy wrapper (included with category), this field also 'becomes' non-required for taxonomy.

I would like to set this to RTBC, but I'm cautious that it could actually be considered a feature request, rather than a bug, and hence that it might be too late to get it in for 4.7. However, if other people feel that it really is a bug (and I won't disagree with that), by all means, set it to RTBC.

drumm’s picture

drumm
he/him
Location NY, US
commented

-1. I don't think we should encourage non-node uses of categories (taxonomy) since they are relatively closely linked.

I don't consider my word on this issue to be final, so I'm leaving this open for review. I suspect a mailing list discussion might be needed to move this forward.

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Needs review » Closed (won't fix)

people who want to do fancy stuff can hook_form_alter the form.

kkaefer’s picture

kkaefer commented
Version: x.y.z » 4.7.x-dev

Discussion continues here: http://drupal.org/node/100429