Closed (won't fix)
Project:
Fivestar
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Oct 2008 at 05:55 UTC
Updated:
4 Mar 2014 at 08:10 UTC
Jump to comment: Most recent
Comments
Comment #1
sin commentedI just realizd that my patch will not work because when the anonymous node will be published by admin the vote will be cast using admin's IP-address :( We can't just publish/unpublish anonymous votes until we got some vote moderation support in VotingAPI. Any ideas?
Comment #2
sin commentedA solution without touching VotingAPI... what if I store vote IP and timestamp in addition to rating and target columns in CCK content-type table? When I can safely delete the vote on review node unpublishing and cast it again on node publishing. This would also improve IP-based anonymous vote deletion.
This would require 2 new optional arguments in _fivestar_cast_vote() function: ip and timestamp. Is it a good solution?
Comment #3
quicksketchA more reliable method would be storing the vote_id in the CCK content-type table, then there would be no doubt at all about which vote was associated with the CCK field. This is the approach used by fivestar_comment module to keep track of votes when comments are deleted.
Comment #4
sin commentedThanks, quicksketch, I thought about it but do not found where VotingAPI returns vote_id, I'l check fivestar_comment module.
Comment #5
Timur5 commentedHey sin and quicksketch,
The patch indeed doesn't work for anonymous users who leave votes which require admin approval: the vote for unpublished comments is still displayed.
However, that looks like a bright idea!
The reason why users use admin approval measure is mainly to prevent spammers from casting meaningless votes.
So, if we could somehow at least eliminate the showing of unapproved votes, the problem will be solved - an admin will come and delete the spam vote while the page remains intact shiny and spam free :)
Comment #6
daneyuleb commentedAny updates on this? (Showing unpublished comment votes is pretty much a show stopper for the fivestar comment module on my site).
Comment #7
sin commentedNo. I didn't worked on this issue anymore.
Comment #8
jsims281 commentedI had a similar issue but using the fivestar comment module.
My workaround can be found here:
http://drupal.org/node/358614#comment-4421454
You would have to change some of the database queries to work with your site, but the basic idea might get you started?
Comment #9
ericduran commentedMoving to the 2.x branch. Sorry is not feasible to maintain 3 different branches. I'l work on 2.x then anything that's been fixed there we can proposed to be back-ported to the 1.x branch.
Thanks.
Comment #10
whiteph commentedWe can no longer support the Drupal 6 version of Fivestar. It is in security maintenance mode only. When the Drupal 8 version of Fivestar is released, the Drupal 6 version will be officially deprecated.
Comment #11
whiteph commentedSee Help testing Drupal 6 patches.