Closed (fixed)
Project:
Voting API
Version:
6.x-2.3
Component:
Views Integration
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2008 at 16:08 UTC
Updated:
20 Feb 2010 at 16:16 UTC
I am using all the latest versions of CCK, Views (Head) and Voting API and Fivestar modules.
I would like to be able to use views to list a CCK node type by Title and its popularity (fivestar direct enabled on the content type). When constructing the view, there is no field to select the nodes 5 star rating/vote.
Thanks in advance for your help!
Comments
Comment #1
sniurkst commentedHi,
I am having the same issue with newest versions of Views, VotingAPI and Fivestar (Drupal6). While I have red that VotingAPI is already "connected" with Views and people are succesfully using it - I can not see anything related to voting neither in fields nor in filter selects. Node types I am working with has Fivestar fields.
I would be thankful for any advice relating this problem too.
And sorry for bad English.
- Sniurkst
Comment #2
ToddThomson commentedRelease notes for Views-RC2 mention that the Views handler functions were re-org'd with a resulting API changed that effects all modules that have a dependency on Views.
I am sure the maintainers of the votingAPI module are working on resolving this issue!
Comment #3
eaton commentedYep. The updated code is written, and should be checked in shortly. Votingapi 2.0RC1 will be rolled before this weekend.
Comment #4
Flying Drupalist commentedThank you very much, subscribing.
Comment #5
mercmobily commentedSubscribed
Comment #6
misterlawrence commentedsubscribed.
Comment #7
gordonbooker commentedGreat, looking forward to using this in Drupal 6
Comment #8
Flying Drupalist commentedComment #9
Flying Drupalist commentedComment #10
kevindoole commentedIs this actually fixed now?
i've got the latest versions of everything, i've cleared caches, i've set up the relationships, i've created new views from scratch, i've tested various configurations...
it just won't display anything vote-related.
if i set up a view with a voteingAPI relationship, it invariably displays no results.
i had about 10 blocks displaying different content sorted by votes that worked totally fine until upgrading to the new views.
then they just displayed random content so i updated votingAPI.
now they just display nothing.
is it just me? (probably)
Comment #11
mercmobily commentedHi,
I am experiencing the same.
Reopening it... sorry guys.
Merc.
Comment #12
eaton commentedPlease post the details of what version of VotingAPI you WERE using, what version you ARE NOW using, and an export of the view. Without that information, there's no way to determine what if anything is wrong.
Please note: With VotingAPI 2.0, you must add a relationship for vote data before any votingapi fields, sorts, or arguments can be added. If you upgrade from Views 2.0rc1 to rc2 later, you must use VotingAPI rc1 or later. When upgrading to those modules, you must also clear the views cache or the new API changes will not be recognized.
Comment #13
Flying Drupalist commentedSorry for being presumptuous, I updated the status after testing it and finding that it worked for me. So here's a vote as one who got it working.
Comment #14
mercmobily commentedHi,
Actually, while gathering more information, I figured that I did something immensely stupid.
Please ignore #11.
Merc.
Comment #15
eaton commentedNo problem! I've broken things more times than I can count while testing some of this stuff. ;-) Just wanting to make sure that any unnoticed problems get ironed out before an official release. Thanks!
Comment #16
kevindoole commentedok, here's one of the views that was working before i ugraded and now doesn't work:
i was using the most recent version of votingAPI and Views until new versions came out of them. now i'm using the current recommended releases. i basically just try to always have the recommended releases of projects.
thanks!
Comment #17
justinchev commentedSimilar problem - using views to order a list of Five star items, just updated to the latest version of VotingAPI (6.x-2.0-rc1) and it's now not working.
In the View setup under Relationship and Sort Criteria nothing appears relating to VotingAPI . Under Relationship and Sort Criteria there is now an error reading - Broken/missing handler.
The previous working version was 6.x-2.0-beta6.
Comment #18
eaton commentedDo you have the latest version of Views?
Comment #19
justinchev commentedThe last version of views I tried broke my site completely. I see there is a newer version than the one that broke my site will try that...
OK, changing both the Views and VotingAPI modules for the latest release has fixed it.
Thanks for your help.
Comment #20
lefnire commentedI think this could be a usability feature-request.
in votingapi 5.x, I didn't have to read instructions. I just set up a view with an "average vote" field. no-brainer.
in votingapi 6x-2.0, I came across the issue, thought it was a bug. Read the README.TXT front to back a couple times, and finally chanced upon this thread. After reading every comment in this thread, I sat there tweaking the "Node: Voting results" Relationship and adding different Votingapi fields until it finally worked.
just a suggestion to make a bit simpler for the typical end-user
Comment #21
eaton commentedUnfortunately, I'm not sure how likely that is. I'd suggest taking a look at the issue queue for the Drupal 5 version of VotingAPI's Views integration -- there's a small set of cases where it DOES work properly, and a huge number of cases where it simply explodes and makes a mess due to the tricky workarounds it employs to make things "kind of automatic".
I understand that the additional step of adding a relationship is, well, another step, but for the time being it's necessary. It's an officially supported aspect of Views2, not an ugly hack, and in contrast with Drupal 5's integration, it actually works.
The latest release of VotingAPI includes three sample views to demonstrate how the fields work. I'll be updating the README.txt with more explicit instructions, and I'll also be adding support for the Advanced Help module to provide inline help inside the Views UI.
If there are some specific improvements that can be suggested that won't break things in multiple configurations, I'm definitely interested in hearing ideas. Please start new feature requests issues for them, though, as it helps keep them separate from explicit bug reports about the current Views integration code. Thanks!
Comment #22
kevindoole commentedIn reply to my last post where nothing was working:
it may have been something i had done, but you may be interested to know (maybe?) that the problem was caused because my votingAPI_cache table had crashed. i emptied that table and now everything seems to be working again.
thanks for your support!
and hopefully/probably this was just a result of moving my site around.
thanks
Comment #23
egarias commentedI have a site: http://solomoto.es where users can vote to articles using fivestar.
I have a block with highest rating articles (+Votado on left sidebar with tabs). but I am unable to show the total votes, the output is 100 in all the nodes.
I am using views 6.2.8 and votingapi 6.2.3.
Here the code of my view:
Thanks in advance for any help