Fivestar stores only the latest vote

Have you upgraded the fivestar or votingapi dependency modules recently? If so what was the last versions it worked. Also which version of Drupal core did you upgrade from (presume your on the latest now of 7.22).

Same problem here...really annoying:

Drupal 7.23
Fivestar 7.x-2.0-alpha2
Voting API 7.x-2.11

Same here aswell

Drupal 7.23
Fivestar 7.x-2.0-alpha2
Voting API 7.x-2.11

It became a major problem, because nobody wants to see the latest vote, average or his/her own instead.

After a little code digging, I realized, that no matter what values are stored in the table of the fivestar field, becase it recieves the vaues from the votingapi_cache table. So I don't think it is the source of the problem.

Another thing that this problem is only happened in Firefox. When I was cheking it in Chrome, it had displayed my vote first, but the average after I re-loaded the page.

I hope I can help you a little to be closer to the solution.

I have precisely the same problem! My settings are exactly the same as the ones mentioned in the first comment here. I just don't see the 'Exposed' option in the Node > Manage display, so that's not ticked. Also, as a reply on @k.dani, it doesn't work in any browser.

Please help, because I really need this!

I solved the problem by deleting the Fivestar rating fields and creating them again. The 'Exposed' check box appeared this time.

I'm also having this problem.

Drupal - 7.23
Fivestar - 7.x-2.0-alpha2
Voting API - 7.x-2.11

I've got a content type. It has a Fivestar field with rating on view. In display I've turned off the exposed value.

I placed the same field on the comment and set it's votes to the parent node. It's rate on editing.

When I create a comment the first vote is stored however future votes replace the previous comment. The average isn't summed and the number of votes cast never increases past 1.

I'm using different users (because I have votes per registered users set to 1) and I have anonymous votes set to unlimited.

I am suggesting the working solution.
Use the latest development module for both fivestar & voting api.
In Voting API settings on configuration page- select Anonymous vote rollover & Registered user vote rollover for 5 min
In Vote tallying setting select 'Tally results whenever a vote is cast ' option & save configuration.
Then write comment from same user on single node but there should be more than 5 minute interval between these two comments.
(means write second comment on same node after 5 minute.)

U will get required result.
Then u can minimize the time limit as per your requirement.
Hope, this solution will give you Idea that how to deal with this problem situation, you are facing.

Can you please test with the 7.x-2.0-beta1 version? It has about twenty fixes applied since the latest comment here.

Lack of response by the community, so downgrading the priority.

Lack of response from the community, so closing.

Well, four years later: here is some community feedback:

The problem still exits, even when following the instructions as seen above in #10

Using Fivestar 7.x-2.2 and Voting API 7.x-2.12

Hi. It's happening again.

Fivestar 7.x-2.2
Voting API 7.x-2.13

This problem seems to be happening again.
Voting API 7.x-2.13
Fivestar 7.x-2.2

How can I make the module recalculate all the old ratings? I'm trying to implement an average rating for a node based on user ratings in comments. The Fivestar field in comments has existed for a long time and has accumulated ratings. Now, I’ve added this existing field to the node entity and configured everything according to the instructions. It works fine for new ratings in comments, but not for the old ones.

To make the module account for all the old ratings, I tried re-saving the comments. However, this results in the module counting only one rating from the most recently re-saved comment. That is, the average rating displays the value of the last comment's rating, and the counter always equals 1.

When I switch to new ratings, everything works almost correctly. The counter counts new ratings accurately and calculates the average rating properly. But when I re-save a new comment, its rating and counter are counted twice. Deleting a new comment with a rating doesn’t change anything.

Does anyone know how to make the counter and average rating recalculate all the comments with ratings, both old and new?

I have anonymous and not votes set to unlimited and try different versions of fivestar and votingapi.