I have Views that are setup to pull the Average of all nodes. After updating to the latest Fivestar and VotingAPI modules, the Views themselves break because they are looking for a JOIN with the table "votingapi_cache_vote_percent_average"
I looked all over the forums and only found issues with 6.x, but this is for version 5. The Views were working before the update; now I need to go through and manually edit the views to eliminate that requirement.
Additionally, I can't add the VotingAPI percent average field to Views anymore - the Field does not show up in the Fields select list for inclusion in the View. I feel that this is related.
Thanks, and apologies if I already missed a similar issue (or patch).
Comments
Comment #1
torgospizzaHere are the relevant parts of the Watchdog error.
Unknown table 'votingapi_cache_vote_percent_average' in field list query: SELECT node.nid, node.title AS node_title, node.changed, votingapi_cache_vote_percent_average.value AS votingapi_cache_vote_percent_average_value, ... (snip)
Comment #2
torgospizzaOne more update while I try to narrow this issue down. After playing around I found that deleting the field from the View and then editing it again allows me to add the Field to the View. Adding it allows the View to come back and be viewable on the site; however the view cannot add the Average Percent as a Sort Filter, nor does the Average display in the View itself. Still working on this, if I can decide on what the issue exactly is (and discover the solution) I will post back - in case others have this same problem.
Comment #3
torgospizzaA follow up, I reverted back to 1.3 of the module, and VotingAPI fields appear in my Edit View screen once again. 1.3 was the only version I had readily available on my server, but I will try with subsequent versions to find the issue.
Comment #4
eaton commentedViews integration in VotingAPI 5.x is fundamentally broken -- it works for a small number of cases but more complex cases like this are not supported, and this isn't being developed further. Views support was rewriten in the 2.x branch to fix these issues. If anyone wants to take a stab at rewriting the Views integration for D5, they're welcome to, but it's not on my radar at present.