Support for anonymous tagging

Urgh. Yeah, this could be difficult, and complicates the architecture. Lots of extra code to get total tag counts and such.

Let's leave it as minor priority for now. While there may be some valid usage scenarios for this, I also don't think requiring somewhere to register is a big barrier (e.g. logintobbogan instant register, then you can tag even with an "unverified" role).

Subscribing. It would be lovely if people could actually /use/ the awesome community tagging module.

Hi,

this was a feature request in 2006, then it was postponed; now we have 2010, so I'd kindly like to ask about the status of this issue.

In community_tags 6.x-1.0-beta3, anonymous users see a "My tags" form; that form is evaluated (meaning: strings can be inserted and are looked up in taxonomy), but they seem not to appear in "All tags" (meaning: are not added to the node's tags and/or are not added to the vocabulary).

I think this behaviour - if it even is intended - isn't optimal; users shouldn't see a feature (the "My tags" form) that they can't use in a reasonable manner; I would consider this a user interface issue. If the tags inserted by anonymous users should be handled in 6.x-1.0-beta3 as are tags inserted by registered users, I would consider the described bahaviour as a bug.

So anyway it's time to re-open this issue (setting to "active"); if there is no progress after three years, we should consider to set this to "won't fix" or "by design".

Greetings, -asb

Ugh. "Won't fix", my arch enemy. I've never seen that tag used in an acceptable manner. Otherwise, I agree- Three years is a bit much for a core feature like this.

So there is an important decision to make. Right now Community Tags is basically a way module that records who tagged what when. There is a tagging interface, but it is not very customizable and is quickly becoming dated. One option is to integrate with the tagging module (this does not yet support anonymous tagging though...) #684618.

Another possibility is to completely remove the UI from community tags and let it exist solely through its API and Views.

Until I have more time to dedicate to the module these major changes are on hold. But, if you have a anonymous tagging patch I would definitely be interested in committing it after review. Perhaps one way to handle this is add a new DB table to "counts" the number of times a tag is applied.

Sorry I can't contribute an anonymous tagging patch, but I'd like to point you to the 'Fivestar' module (based on 'Voting API') which has solved similar issues a while ago; it has a widget that can be used by anonymous users, and it has some (quite complex) views integration to harvest the stored voting data. If I remember correctly, the implementation was nontrivial and required some adjustments in the storage/processing backend (see issue queue).

I'm no coder, but it might be worth to have a look at the code how they have done it: Fivestar, Voting API, documentation. However, the approach to separate the UI from the API sounds interesting. Maybe an integration of 'Tagging' could enhance the user experience, and ' Community Tagging' could be made an API to be used by the 'Tagging' module. Anyway, it's the coder's call ;)

Greetings, -asb

My error logs are still cluttered with error messages like:

Type	access denied
Date	Tuesday, June 29, 2010 - 15:42
User	Anonymous
Message	node/980/tag

This applies to anonymous usery.

But:

./node/980/tag

Resolves to this error message for user #1 (!!!):

Access denied
You are not authorized to access this page.

./node/980 exists and is visible to anyone, including anonymous users.

Changing category to "bug report" since this issue seems not only to apply to anonymous tagging.

As far as I can tell this isn't a bug in the latest 1.x dev (soon to be beta4) release. If tagging permission hasn't been granted to anonymous users (and it shouldn't) then they shouldn't see a community tags tab or block. They do see all tags if the CT display is inline but with a message to login or register.

Setting back to feature request and looking to implement this soon on 2.x.

Is this available in the D7 version?