limit the number of tags users can add

Taxonomy limit is never going to work with community tags. That module just does form validation on the node edit form.

Is your request for a per node/per user limit or just per node (a la taxonomy limit module)?

@meatbag - I was thinking about how this would work. Firstly I don't see that limiting community tags is a good idea in terms of user experience. It would either have to disable tag addition if the limit had been reached, and/or return a message via ajax to the user that their tag(s) were not added because the limit had been reached. Yuck.

Perhaps what you're after - and what makes much more sense to me - is to limit the number of community tags that become node terms. In the latest 2.x-dev snapshot you can elect to make node terms from added community tags or not. If the option is switched off then you can maintain node terms independently of community tags. Anyone who can edit the node can add the official terms via the node edit form, for which taxonomy limit will work. You can opt to have these terms added as community tags and it would normally make sense to do so. All terms added as community tags do not automatically become node terms so there's no issue with having too many node terms.

Of course, there is an issue with the community tags display becoming too large because their are so many community tags. But there are ways to address this currently using theming or views. An option to limit the "all tags" display to the top-n tags could be very useful in this case.

One more thought is to add further synchronisation options between community tags and node terms. Candidate options might be:

* Only add terms to the node for the first-n community tags added.
* Maintain node terms for the N most popular community tags. I.e. terms are added to and removed from the node according to their changing popularity.
* Only add terms to the node for community tags added by certain users/roles/groups etc.

@meatbag - What do you think? If I haven't covered it here, what was your motivation for this feature request?

Andy

Something for 2.x-dev.

Drupal 6 is now not supported. This could be a feature for Drupal 7.