I've checked "view" and "use" for anonymous user in access_control.
I turned off caching and dropped my cache in case that was the issue.
The anon user cannot vote.

Is this a feature? Looking at the SQL, if anon could vote you'll get an error if more than one anon votes on a node, since the table has primary on uid/nid.

You should present an option to allow anonymous voting! A lot of people don't care if voting is abused - they just want a spiffy toy.
You'd have to add a vote_id field as a primary key.
Then, if anon voting was turned on, use auto_increment on the vote_id (so there's never a conflict, and multiple voting is allowed)
If anon voting was turned off, use a composition of the uid/nid for vote_id.

Would you accept a patch for this modification?

Comments

kbahey’s picture

kbahey commented

If it is optional, I may accept it.

It also should identify the anon user somehow, e.g. session id as an identifier.

firebus’s picture

firebus commented

i'm definitely thinking of it as an optional (settings option) feature and certainly not the default.

is session id the right thing to log? would it be more useful to log ip address? or to provide a field for the anon user to enter their name (like anonymous comments?)

in any case, let me see if i can find the time to make a first pass at it...

firebus’s picture

firebus commented
Assigned: Unassigned » firebus
Status: Active » Closed (works as designed)

i never did this, i no longer have the need to do this, and no one else is interested (at least on this issue) in doing this. closing.