Views Integration

After playing around a lot I found a workaround for making advpoll work with views. I added some code in voting api to achieve this, so hopefully this can be implemented with a hook. Here 's how I created a table with the time my users voted along with their ip address.

Add this code in sites\all\modules\votingapi\views\votingapi.views.inc

• Search for function votingapi_views_data_alter(&$views_data) and add this:
  

    $default_relationships[] = array(
      'description' => t('Advanced Poll'),
      'entity_type' => 'advpoll',
      'base_table' => 'node',
      'entity_id_column' => 'nid',
      'pseudo_vote' => 'votingapi_vote', // for legacy compatability w/RC1.
      'pseudo_cache' => 'votingapi_cache', // for legacy compatability w/RC1.
    );
  

• Clear your caches
• Go create a new view (Show: Content of type:Advanced Poll, Display format: Table)
• Add Relationship: Content: Votes (Votes cast by users on Advanced Poll.). For the data filters don't select anything as it messes up the query created.
• Add fields: Votes: User, Votes: IP Address. You should now have a table with the uid of the user and the time him voted.
• If you and add the Relationship: Votes: User(The user who cast the vote.) you will be able to retrieve more info about your user.

If you know a better workaround please share.

It may be pretty simple but not sure if it is correct. The problem for sure is that Voting API looks for votes with entity_type either saved as "node" or "comment". Advanced Poll saves the votes with entity_type "advpoll". In the previous issues the developer states two ways to resolve this. Tried to follow his way of thinking but not sure if my way has taken in mind all the possible scenarios (e.g in my way you cannot add data filters like points,percent,normal) Don't know if those were working in the 6.x version though.

Couldn't make it work.

I only have one advpoll node.
Created a view with relationship "Content: Votes (Votes cast by users on nodes.)".
Added fields

• (Votes) Votes: Timestamp (Timestamp)
• (Votes) Votes: IP Address (IP Address)
• (Votes) Votes: User (User)

I can see the query to the database is not correct.

SELECT votingapi_vote_node.timestamp AS votingapi_vote_node_timestamp, votingapi_vote_node.vote_source AS votingapi_vote_node_vote_source, votingapi_vote_node.uid AS votingapi_vote_node_uid, node.created AS node_created
FROM
{node} node
LEFT JOIN {votingapi_vote} votingapi_vote_node ON node.nid = votingapi_vote_node.entity_id AND votingapi_vote_node.entity_type = 'node'
WHERE (( (node.status = '1') AND (node.type IN ('advpoll')) ))
ORDER BY node_created DESC
LIMIT 10 OFFSET 0

So the hook to add another enity type 'advpoll' didn't work. Same problem for the "Content: Vote results (Aggregate results of votes cast on nodes.)" relationship. Only in this relationship the query is done to the votinapi_cache table and the entity type is still set to 'node' instead of 'advpoll'.
I am attaching the export of the view. Don't know if you can find something useful there to help you fix the problem.