On my Drupal 7 site, I have two node types: product and store. Using node reference, the product node references a specific store node. The product node has multiple rating axes and ratings are submitted through node comments. Following http://drupal.org/node/1274426#comment-4975152 I was able to get the average of each axis to be displayed on the product node. Now I want to display the average combined rating of all of the products on the store node, and am at a loss on how to do so.
The axes fields used to display the average on the product page, do not have a target, so I am unable to set the referenced node as a target. I have also tried using views to aggregate and display the average of the axes from these nodes, but this ends up with some incorrect values (possible bug?) for the averages.
On a slightly related matter, is a mechanism in place to have one field which displays the average rating of all of the axes or would something custom need to be written to achieve this? For example if I wanted there to be a general rating for a product which was the average of all axes.
Any help and guidance in this matter would be greatly appreciated and hopefully be useful for someone else in the future as well. Thank you in advance for the input.
Comments
Comment #1
IWasBornToWin commented8 months ago this question was asked. Wonder if there will ever be , perhaps, a small membership fee for Drupal so the "free" site doesn't cost so much? It would be worth it to pay for support. The best module in the world lacks when you can't get help.
Can anyone answer this question? Do the maintainers of this module get these questions? Just curious, this isn't the first issue on this module which I've seen go unanswered. I have the identical question. Love the module....when I can get answers.
Comment #2
jawi commentedany progress on this one?
Comment #3
whiteph commentedRe #1 - you should bring up the question of paid support in the main section of Drupal.org, it's a fair point. I'm the only active maintainer at the moment, and I've only had commit permission since February 1st when I created the alpha3 release which contained patches committed by previous maintainers. I'm trying to get the module and its issues list into good shape, but this is going to take some time. Please be patient.
Comment #4
whiteph commentedMoved the priority down. Using the definitions in Priority levels of issues, where it says Tasks and Feature Requests are very rarely “critical”. They should usually be “normal” or “minor”. Support requests should never be marked "critical" or "major" - if you believe you have run into a bug and it is preventing your site from working at all, post it as a bug report.
Comment #5
jawi commentedStill would be a excellent feature that really suits a drupal install well!
Comment #6
whiteph commentedThere are two feature requests in one here. The second one, averaging all of the axes, is a very common request. I've closed all apart from one as being duplicates, but linked them to the open issue Vote-averaging for multi-axis. I agree that this would be a very useful feature, and now that the first official Drupal 7 version of Fivestar is about to be created (the rc1 version has been out there for a couple of days with no adverse feedback so far), I'm going to start work on it shortly.
The second one is more complex, and I'll leave this one for now. Let's get the easier one into the module first.
Comment #7
whiteph commentedThere are two feature requests in one here. The second one, averaging all of the axes, is a very common request. I've closed all apart from one as being duplicates, but linked them to the open issue Vote-averaging for multi-axis. I agree that this would be a very useful feature, and now that the first official Drupal 7 version of Fivestar is about to be created (the rc1 version has been out there for a couple of days with no adverse feedback so far), I'm going to start work on it shortly.
The second one is more complex, and I'll leave this one for now. Let's get the easier one into the module first.