VUD 1.x labeled all node votes with a `content_type` of 'node' in the votingapi_votes table. VUD 2.x changes the `content_type` to whatever the node type is for each vote (ie: 'page' instead of 'node').

To my knowledge (and the best of my poking-around ability) this new method is not compatible with views, so showing voting results in views is broken.

Comments

lut4rp’s picture

lut4rp commented
Issue tags: +vud-2-blocker

Marked as a blocker.

FatPitchFinancials’s picture

FatPitchFinancials commented

I am able to show vote results for VUD 2.x. The key with Views 2.8 is to first create a relationship called, for example, "Vote points total" with a Value type of "Points", Vote tag: -Other- and then type in your vote tag setting for Vote Up/Down, and Aggregation Function: Total score. Then under fields you can add (Vote points total) Vote results: Value. I placed "0" in the Empty text field and the result shows a view of the point totals. You can then sort them using a Sort criteria.

I believe the votingapi table does not break views functionality currently. I think we should consider removing this as a bug.

vood002’s picture

vood002 commented
Status: Active » Closed (fixed)

I'm not sure where this stands... i believe I may have been using the module as the designers did not intend by passing $node->type to the VUD widgget as 'type' rather than just passing 'node'.

In the latest .dev it seems to work out of the box with 'node' type votes, so this bug report might have been filed in error. If not, then the fix from FatPinchFinancials should do the trick. Marking as closed.