Closed (outdated)
Project:
Voting Rules
Version:
6.x-1.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
6 Aug 2010 at 21:54 UTC
Updated:
17 Nov 2018 at 23:35 UTC
Jump to comment: Most recent
Hi,
Currently it seems like you have to have another voting module running as well as votingAPI - eg plus1 or vote up/down. Would it be possible to allow any event to add a vote??
EG When a Flag is hit, add a vote to that node.
This would really open up the votingAPI to be used in lots of ways, including using with Flag, which would be very useful for all those looking for a way to use Flag as the front end of theirt voting system.
Many thanks for the module - it's good to see it taking shape,
Joe
Comments
Comment #1
heydemo commentedThis sounds like a useful feature - I will go ahead and code this when I get some free time.
Comment #2
joecanti commentedThanks heydemo - that would be great. I will keep an eye out for it.
Joe
Comment #3
liam mcdermott commentedI have another use-case that's so similar to this feature request that I thought I'd post it here. Do say if it should have its own issue though.
My use case is that nodes are put through 'peer review', where users rate content via fivestar, if their rating isn't high enough the user must create a new node revision, then go through the process again. The problem is that existing votes are retained even after a new revision has been made.
In a nutshell: using Voting Rules, reset the fivestar rating (or any Voting API vote count) when a new node revision is created.
Comment #4
jaydub commentedIt sounds to me that was is wanted here is to take what is currently the set of events - insert / update / recalc - and make those not only events which trigger actions via Rules but also to make those events into actions themselves so that some other event could trigger a vote action.
So for Liam's case the event would be create a node revision and the action would be to reset the node's vote which isn't currently an event but if you work off of recalc you could probably make a reset out of it. Looks like there's no direct API function for blowing out a single node/user/comment's votes but a combo of loading single node, etc vote data and using the vote delete function following by recalc should approximate a single entity vote reset.
I stumbled across this module during research phase for voting where using Rules could be beneficial so I'll try to contribute what I can to support these features.
Comment #5
heydemo commentedOne of the problems with this module is Rules requires us to specify what type of object we´re operating on ahead of time (user, node, comment). So I would have to create seperate actions for each content type Add vote on a user, Add vote on node, Recalc on a user, recalc on a node, each with their own configuration forms, etc.
@Liam - sounds like what you want is delete votes. I´ll look into that once I´ve committed adding votes.
Comment #6
ju.ri commentedThis sounds really useful!
In my case I would like to store the current sums of votes into a new vote (with a new tag), to use those for calculations later...
Thanks for looking into this!
Comment #7
jthomasbailey commentedSubscribing
Comment #8
BIGREDPAUL commentedI'm pretty sure because of the usefulness of flags this request would be very popular. Subscribing.
Comment #9
heydemo commented6.x-1.0-beta1 has the ability to vote on node, comments, and users.....I believe you need an event with one of these types....it's possible I could add a content ambiguous action - let me know if this is needed!
Comment #11
restyler commentedI couldn't find this functionality for 7.x branch.
do we have it?
Comment #12
heydemo commentedNot yet on the 7.x branch
Comment #13
bluegeek9 commented