Posted by robertdouglass on May 4, 2006 at 11:36am
Prior to the recent innovations with actions integration, the recipe for digg was to install vote_up_down and follow directions. Now, if you do that, you end up with function conflicts between voting api and voting_actions. I therefore removed voting_actions since it seems to be deprecated. Where do I go from there to get custom actions based on voting?
(note: I'm researching almost as I type and hope to be able to answer my own questions =)
Comments
Doh!
Actually, the only conflict should be between the voting_actions.inc file and the votingapi_actions.inc file. I'm checking in a new version of the former to avoid the conflict now. Thanks for pointing it out. (Whoops...)
As I finish the UI for Votingapi's NEW actionsintegration, we're slightly 'between technologies'. There's no DIRECT way for users to edit actions, but the infrastructure that's there is a lot more robust. The first change is that any module can expose a set of criteria, and actions to be performed if a vote result meets the criteria. SimpleVote.module now has an example of this function that auto-promotes nodes to the front page if at least 5 people vote it 75% or higher.
The votingapi_actions.module will be bundled directly with VotingAPI, and will be usable by those who want to enable or disable those 'default' actions, or create their own custom voting action sets. I'll post more later today...
--Jeff
Look forward to your post
I'm still fuzzy on when a *_vote_result_handler function will get called.