Hi guys,

Was just curious if there's any way to make the votingAPI aspect of activity slightly more robust to take into consideration the module being used by votingAPI.

For example, I'm using both the Fivestar and VoteUpDown modules on my site. VoteUpDown works fine, my output is in the following format [author] gave [content-type] "[content-link]..." [author-vote] point. which translates into something like TheBigGuy gave comment "Party On Wayne!" 1 point. . Perfect.

Where this kinda blows up is with Fivestar, since apparently the [author-vote] token isn't taking into consideration that scoring is different. So [author] gave [content-type] "[content-link]..." [author-vote] stars., with a node given 5 stars, becomes something like TheBigGuy gave the story "Rock on Garth" 100 stars. instead of 5 stars, which would be the proper translation.

With the current tokens given I don't see an alternative... would it be possible to include this in a future release? (1.x or 2.x)

Thanks!

Comments

jaydub’s picture

jaydub commented
Component: Code » Activity Contrib
Assigned: Unassigned » jaydub
jaydub’s picture

jaydub commented

This won't make it to the next release but I think there are a couple things we should do:

1) Actually use the votingapi API to get vote data rather than query the tables directly like we are now

2) Use a theme function to return the actual vote value that's passed to the vote value token. This way you can override and modify the vote value based on what voting module recorded the vote.

sirkitree’s picture

sirkitree commented
Status: Active » Closed (won't fix)

closing. 1.x no longer supported.