Posted by voidberg on March 31, 2010 at 3:07pm
7 followers
Jump to:
| Project: | Community Tags |
| Version: | 6.x-2.x-dev |
| Component: | Node term synchronisation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hi,
We ran into an issue with community tags on our site. We are running a wiki like site where users can edit all nodes and they can tag them using community tags. The problem is that the community tags vocabulary textfield appears on node edit and a user can delete all community tags, even the ones which were not created by him.
The attached patch:
- Adds a new permission, edit tags on node edit.
- Hides the community tags vocabulary textfield on the node add / edit page if the user does not have that permission.
| Attachment | Size |
|---|---|
| community_tags.module.patch | 1.15 KB |
Comments
#1
Subscribe
-Daniel
Urbo
#2
Is this a widely desired feature? My concern is that since the permission will default to off, people will be confused why they cannot edit their tags. This is really a small concern since as it is they have to mess with permissions to get ctags to work, but I wanted to see what people thought before we commit.
#3
The patch applies cleanly against community_tags 6.x-1.0-beta3 and works as advertised. So far I didn't encounter any negative side effects.
Checking the permissions is alway a good idea after installing a new module, especially if it allows anonymous users to edit content. I think a pointer in the README.TXT and/or on the project page would suffice.
-asb
#4
I second this request, as it provides the ability to add a level of safeguarding at a point where it's easy to (accidentally, even) delete a bunch of data.
I'd guess that people are used to checking the permissions if something should be appearing on an edit form and is not.
#5
The patch is exactly what I was looking for.
I needed a second option for moderators to tag content only for their analysis purpose.
#6
I'd rather add an option to hide the taxonomy edit field. This would be set per enabled vocabulary/content type. A new permission would override this to make it always available to selected roles.
I think this would work better because a) it's more configurable, and b) you'd have to explicitly enable this feature to hide the term field(s).
Of course with this approach you're just hiding the field so anyone could spoof the post and delete all the terms and community tags. This is where the enhanced node/term synchronisation features in 2.x-dev come in...
If you don't enable the sub-module Community Tags Node then node terms are completely independent of community tags. If you need to synchronise node terms and community tags for some vocabularies/content types but not others then enable Community Tags Node and select/de-select the various synchronisation options on the relevant Community Tags settings pages. To guard against all users' community tags being deleted either unset all synchronisation options or select just "Sync community tags with node terms" which for terms added or removed on the node edit page will add and remove community tags for the current user only. Which is probably exactly what you want. Perhaps?