lcollong
FabriKant d'applications web
Hi there,
I've a very basic "suggestion list" on which there is a rating element. Every one can "vote" (see config snapshot).
It works well and I can see the #__fabrik_rating table growing with the right data.
It seems that the average value is computed "on the fly" when the list is displayed. The rating column in the main list is never updated and always contains zero. Thus, it's not possible to sort the table on the average rating level.
Wouldn't be better to update the main table element with the average value ? It would allow sort on the next refresh/display. It would also prevent the queries on the #__fabrik_rating each time the main list is displayed.
Another point. I've set the decimal number to 1. In the detail/form view it shows the right value (said 3.7) whereas in the list view, it's always round up to the next integer (4). Without decimals.
I've a very basic "suggestion list" on which there is a rating element. Every one can "vote" (see config snapshot).
It works well and I can see the #__fabrik_rating table growing with the right data.
It seems that the average value is computed "on the fly" when the list is displayed. The rating column in the main list is never updated and always contains zero. Thus, it's not possible to sort the table on the average rating level.
Wouldn't be better to update the main table element with the average value ? It would allow sort on the next refresh/display. It would also prevent the queries on the #__fabrik_rating each time the main list is displayed.
Another point. I've set the decimal number to 1. In the detail/form view it shows the right value (said 3.7) whereas in the list view, it's always round up to the next integer (4). Without decimals.