- Issue created by @msypes
I have an entity with multiple voting widgets on it, using the Rate module β as a front end. Some are "fivestar" widgets, and one is a "thumbs up" widget. I would like to have a relationship that allows me to see the sum of all widgets regardless of type.
Using the Vote result "Sum" for entity type, gives me one row for each widget type, each with the sum for all widgets of that type. Similar results are achieved with Vote result "Count" for entity type, and I suspect, the other "plain" Vote Result options.
There are relationship options for each widget type, and combinations of these will output the same data, keeping a single entity on a single Views result row, which sounds more desirable than getting multiple rows anyway.
Add multiple Rate widgets of several types to an entity type and cast votes. Create a View to display the entity and add the Vote result "Sum" for entity type relationship. Then add fields, e.g., vote type and vote value to the display. You'll get multiple result rows for each voted-upon entity, one for each widget type, rather than a single row with a summation of all widgets.
I suggest either adding new relationships that don't segregate based on widget type and make it clear in the UI how they're different from the existing "plain" ones, or refactor the existing "plain" ones to exhibit the behavior I expected in the first place.
On further reflection, while it makes sense to have relationships that segregate based on widget type, which I noted seem to already be in place, what's missing is a relationship based on value type (points | percentage | options).
Active
4.0
Code