Closed (fixed)
Project:
Fivestar
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 May 2011 at 09:18 UTC
Updated:
29 May 2011 at 23:11 UTC
Jump to comment: Most recent
I enabled Fivestar for a content type on my test site, and started to play with the voting widget. Every time I click on the widget selecting a different star, the click is the recorded, and the number of votes is increased.


As I am the only user voting, the average vote should then be the vote I last casted.
| Comment | File | Size | Author |
|---|---|---|---|
| Screen Shot 2011-05-12 at 11.16.28 AM.png | 7.3 KB | avpaderno | |
| Screen Shot 2011-05-12 at 11.12.28 AM.png | 7.49 KB | avpaderno |
Comments
Comment #1
avpadernoComment #2
Anonymous (not verified) commentedSame issue, the votingapi_vote table contains all my consecutive votes (same user, same node).
Comment #3
Anonymous (not verified) commentedIt's probably even worse, I think there is a related issue:
Just did a clean install of latest dev votingapi (april 1) and fivestar dev (may 9th). Enabled all default settings. When I cast a vote, it says:
"Saving your vote"...
"You vote has been saved"...
then jumps back to:
"No votes yet"...
Refreshing the pages: 0 votes, but the database table votingapi_vote has all my votes. And these votes are duplicates.
Comment #4
ericduran commentedThis is not a fivestar issue. Technically this is a duplicate of another issue but I'm going to leave this open so other people can see it.
The underline problem is #997092: Anonymous vote rollover not working over at the votingapi. There's already a couple of patches there please try them and review them.
Thanks.
Comment #5
avpaderno#997092: Anonymous vote rollover not working is about anonymous users, while when I have experienced what I reported I was logged in.
Comment #6
ericduran commented@kiamlaluno I get that the issue is with anonymous vote rollover but the underline problem is the same. There's something wrong with the votingapi select query which causes it not to select the queries that we want to delete when a specific use is voting.
At least thats what I've found when investigating this problem. I would recommend trying some of the patches on that issue queue and seeing if that helps. Unless you know where in fivestar the bug is.
I might be wrong, but for now I'm going to postponed this issue until the votingapi issue is resolve and we're sure is a fivestar problem.
Thanks.
Comment #7
ericduran commented@kiamlaluno, I changed the way this module was implementing is vote casting. This should now fix the problem you where having.
There votingapi issue is still a problem, I just circumvented it for this specific use case.
Thanks.
commit -- http://drupal.org/commitlog/commit/2490/1bff258b24316f240669051e610eba92...