fivestar and voting actions module

A "redirect to url ..." will definitely cause issues with Fivestar's AJAX voting mechanism. Here's what's happening:

What normally happens:
- User clicks on a Fivestar widget to rate.
- AJAX request is made by the current page.
- VotingAPI saves the vote.
- Fivestar generates XML and prints the page.
- The current page receives XML, then updates the voting widget with the new values.

What happens with VotingActions:
- User clicks on a Fivestar widget to rate
- AJAX request is made
- VotingAPI records the vote
- VotingActions hooks in and says "oh I'm redirecting this URL" <-- Where things go wrong
- Instead of returning XML to the calling page (which would update the votes), the original page gets back a full HTML page of wherever VotingActions redirected the page.
- Fivestar doesn't get to generate it's XML, because VotingActions has ended the execution by using a drupal_goto().

So I don't think it's a bug in either VotingActions or Fivestar, it's just a case of using two features in incompatible ways. To make this work, Fivestar would have to *not* be AJAX driven, instead reloading the page to save a vote.

Fivestar provides a nice JavaScript hook that you can use to go to the next page. If you add JavaScript to the page that contains something like this:

function fivestarResult(voteResult) {
  window.location.href = 'http://google.com';
}

awesome tip! Exactly what I was looking for :)