Posted by drupaloSa on September 11, 2008 at 11:17am
| Project: | Community Tags |
| Version: | 6.x-2.x-dev |
| Component: | Unitag integration |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
As asked here #300512: Tag approval queue? for 5.x, i believe there should be a way to approve/disapprove user tags to prevent spam and unappropriate tagging. Currently Unitag module provides this feature on node submissions for 5.x branch. It does this by making free-tagging vocabularies read-only and sending non-existent terms to a management interface where they can be dealt with either by
- saving as new terms,
- saving as synonyms of provided root terms,
- saving as child terms of provided parent terms,
- or deleting.
Unfortunately Unitag module doesn't work with the current implementation of CT and also there isn't a 6.x version. So even CT could be made work with Unitag, this won't help 6.x users. Perhaps it may be possible to implement this feature directly in CT instead of making it dependent on Unitag.
Btw, here is the Unitag maintainer's comment on the issue.
Comments
#1
This is a decent idea that may help open up anonymous tagging in the future. A filter system might help as well- i.e. not allow anything formatted like a URL to be posted.
#2
I second this feature request. Even working with unitag to make it support this module would be awesome.
#3
Wonderfull feature, subscribing
#4
I'm also looking for this feature to moderate tags. It would definitely make tags a lot more organized.
#5
I am interested in this, but I think it would require a lot of code refactoring (patches?). Supporting Anonymous tagging by itself will not be hard, but this will necessitate the previously mentioned things like sanitation (also easy) and most importantly an approval queue.
Also I am concerned having anonymous tagging would conflict with the concept of knowing "who" tagged what when. If it is anonymous it will make this somewhat ambiguous. Basically this a related but still distinct functionality which will make it non-trivial to implement.
#6
Hmm, in my case I wasn't planning to allow anonymous users to use community tags anyways. I actually think this is a good idea with just registered users. With registered users there is still a lot of inappropriate and generally "sloppy" tagging.
#7
Here's a patch for unitag integration.
In order to avoid any dependencies on unitag this patch introduces two hook_alter callbacks with the actual integration implemented as a contrib module of community_tags. Install the patch and don't forget to enable the new community_tags_unitag module.
Feedback will be greatly appreciated.
#8
Patch looks great.
I could not get the synonym replacement to work, but it would not work regardless of whether I used the ctags form, so this is probably my user error or oversight. Has this been tested?
I get an error when trying to "approve as synonyms of the root term"
user warning: Duplicate entry '7-2' for key 'PRIMARY' query: INSERT INTO term_node (nid, vid, tid) VALUES (2, 2, 7) in /Applications/MAMP/htdocs/skfd/includes/common.inc on line 3528.user warning: Duplicate entry '7-1-2' for key 'PRIMARY' query: INSERT INTO community_tags (tid, nid, uid, date) VALUES (7, 2, 1, 1289187125) in /Applications/MAMP/htdocs/skfd/sites/all/modules/community_tags-DRUPAL-6--1/contrib/community_tags_unitag/community_tags_unitag.module on line 160.
The error goes away with community_tags_unitag module disabled.
Lastly I am a little concerned that there is no user feedback to explain how the ctags form works with unitag enabled. What happens is the user adds tags, they get added to "my tags" but not to the actual node tags. Perhaps a simple message that says something like "Your suggestion has been sent to the approval queue", but then my concern becomes making the message customizable/configurable (which is a huge weakness throughout all of ctags).
Anyway great work Chaps2! I am also 1000 times pleased this was implemented as a separate module, and wholly impressed by the quality of the code and comments. Lets get this in as soon as reasonable (ideally a few more people would try it out and give feedback first).
#9
This is now included in 2.x-dev as a sub-module. In addition to setting per-vocabulary unitag settings, unitag integration must be enabled on the community tags settings pages as required.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.