# Topic Ratings Plugin
**URL:** https://meta.discourse.org/t/topic-ratings-plugin/39578
**Category:** Plugin
**Tags:** pavilion
**Created:** [February 14, 2016, 9:06pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578 "2016-02-14T21:06:53Z")
**Posts on this page:** 20
**Page:** 7
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [December 6, 2017, 8:52am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/124 "2017-12-06T08:52:48Z")
Hey, Santa Angus! Got some room in your busy schedule? š
[[feature request] Show the count of reviews along with the avg score Ā· Issue #11 Ā· paviliondev/discourse-ratings Ā· GitHub](https://github.com/angusmcleod/discourse-ratings/issues/11)
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [December 7, 2017, 9:23am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/125 "2017-12-07T09:23:47Z")
Added š
Setting is `rating_show_count`; default is false.
[https://github.com/angusmcleod/discourse-ratings/commit/0822e094a5fa25d875c615fcc07a1bbd02676d06](https://github.com/angusmcleod/discourse-ratings/commit/0822e094a5fa25d875c615fcc07a1bbd02676d06)
See further: [https://discourse.angusmcleod.com.au/t/the-400-blows-truffaut/151](https://discourse.angusmcleod.com.au/t/the-400-blows-truffaut/151)
---
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [December 7, 2017, 12:12pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/126 "2017-12-07T12:12:57Z")
Dear Santa, thank you very much! I always believed you were real š
---
### Author:  [@Tumi](https://meta.discourse.org/u/Tumi)
#### Post date: [December 16, 2017, 10:05pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/127 "2017-12-16T22:05:36Z")
Thanks for Your time. Ok i will learn how to do it all becouse im not a programmer.. Need some time. Pls tell me - should i learn a ruby laungage or not really ? Should i know somethink more ? How to learn it as fast as it possible (not for be a pro - just for myself needs)
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [January 2, 2018, 11:20am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/128 "2018-01-02T11:20:25Z")
@dalerka @hnaseri As discussed, Iāve updated the average / count style. It now looks like this:
Both the Amazon style and the use of an emoji has issues. I think itās best we keep it simple.
[https://github.com/angusmcleod/discourse-ratings/commit/0b7b8fb908cb2073d3a95b3f3f17b9028092bfd2](https://github.com/angusmcleod/discourse-ratings/commit/0b7b8fb908cb2073d3a95b3f3f17b9028092bfd2)
Thanks for your suggestions š
---
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [January 2, 2018, 12:18pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/129 "2018-01-02T12:18:21Z")
Thanks, Angus! I totally agree with you on KISS, but genuinely curious if you could expand on issues with Amazonās approach. Is it about UX or Discourse-related?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [January 2, 2018, 1:52pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/130 "2018-01-02T13:52:05Z")
There arenāt any inherent flaws with Amazonās rating UI/UX or any inherent limitations in Discourse, it would just take considerably more work to achieve the same result in this plugin and there would be various UX tweaks to their approach and decisions that youād need to make.
Effectively it would be a new feature-set rather than a UI tweak, which is all that is required for now.
Off the top of my head, some things youād need to do would be:
1. Fractional stars, which would entail a refactor of the CSS. Albeit, this has the minor caveat that the fractional star in Amazon typically does not represent the actual average. See the screenshot below for an example (4.5 according to the stars, 4.7 according to the text)
2. Provide the rating breakdown from the server and set up the UI so that itās consistent with the Discourse UI, e.g. the bar chart would be a new UI element youād need to build specifically for this.
3. Interactivity of the rating breakdown, i.e. in Amazon if you click on one of the ratings you see just those ratings. Once a rating breakdown is provided, the ability to filter the rating posts by rating is the natural next step.
Not to say that I wouldnāt want to do each of all of these things at some point, just not right now, particularly as these kind of features get more relevant when youāre dealing with consistently large volume of ratings, which (as far as Iām aware) weāre yet to see with this plugin.
---
### Author:  [@Boogs](https://meta.discourse.org/u/Boogs)
#### Post date: [January 9, 2018, 1:32am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/131 "2018-01-09T01:32:15Z")
This is awesome!
Iāve been thinking how awesome a Discourse / ecommerce integration would be. There are heaps of third-party reviews systems, but they all to some extent take the SEO and community engagement away from your site.
IMO, this plugin + your Q&A plugin would work very nicely! Basically you could relate the post to a particular product (from say a CSV or XML product feed or ecommerce CMSās API). I guess the ratings threads would need a way to restrict topic creation so that there is only one thread per product.
On the ecommerce CMS side youād have some kind of widget that shows a snippet of the ratings and Q&Aās for that product, similar to the WP / Discourse integration.
Thoughts?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [January 9, 2018, 3:29am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/132 "2018-01-09T03:29:30Z")
Yes thatās all doable. I havenāt been doing a lot of work on the QnA plugin, so if you want to use that in a serious way youāll need to take a close look at it and test its functionality thoroughly.
> [@Boogs](#):
>
> I guess the ratings threads would need a way to restrict topic creation so that there is only one thread per product.
Not entirely sure what you mean here, but this would seem to be something your moderators would handle, at least initially.
> [@Boogs](#):
>
> On the ecommerce CMS side youād have some kind of widget that shows a snippet of the ratings and Q&Aās for that product, similar to the WP / Discourse integration.
Sounds a bit like you may want to also use [Topic List Previews](https://meta.discourse.org/t/topic-list-previews/41630).
---
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [January 18, 2018, 12:29pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/133 "2018-01-18T12:29:36Z")
š¤Ŗ Today I updated the plugin to `(fd25572)` and the _Rating-stars_ disappeared from items of _topics list_ view and on _suggested topics_ list (i.e. I can still see the stars on a topic page).
I cannot find any elements with `.topic-rating` class in the source code of the _topic list_ view. Is it a bug or is there a new setting I should enable?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [January 19, 2018, 12:42am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/134 "2018-01-19T00:42:42Z")
Yup, minor bug. It will work as normal now. Thanks for reporting.
[https://github.com/angusmcleod/discourse-ratings/commit/2607f452519a7ddf357c033bf6403fdd4e75a83b](https://github.com/angusmcleod/discourse-ratings/commit/2607f452519a7ddf357c033bf6403fdd4e75a83b)
---
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [January 19, 2018, 6:26am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/135 "2018-01-19T06:26:33Z")
Thanks! So, (just for the record) previously the plugin rendered the `.topic-rating` nested under `.social-footer` and now it renders nested under `.topic-title` (in a _topic-list_ view).
Now, I also see that in the _suggested topics_ list sometimes (randomly) the `.topic-rating` and `.topic-excerpt` elements donāt get rendered at all. Any ideas why?
UPDATE: Donāt know why, but the later issue with excerpt and rating not rendering randomly has suddenly disappeared. Magic š
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [January 19, 2018, 7:48am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/136 "2018-01-19T07:48:04Z")
Hm yeah. This is all about plugin outlet placement in the topic list item template(s). The Ratings plugin is now using the `topic-list-after-title` outlet.
Iāve handled the case youāre referring to. For social style, the plugin outlet will render content in the gutter now.
[https://github.com/angusmcleod/discourse-topic-previews/commit/2f3d069d93e988f784bcacd64aac8c77a4fc23ad](https://github.com/angusmcleod/discourse-topic-previews/commit/2f3d069d93e988f784bcacd64aac8c77a4fc23ad)
---
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [January 19, 2018, 10:29am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/137 "2018-01-19T10:29:18Z")
Haha, Iām sorry, didnāt mean to distract you.
The `after-title` position was actually preferable for me (even with Social style). My point was to help other people fix styling (target the right element). I made few CSS changes and removed hiding an extra `middot`.
So, if possible can you keep it _the new way_ (i.e. rendering at _after-title_)?
UPDATE: Also with the recent update the `.topic-ratings` element doesnāt render on mobile (with _social style_ topic list enabled). So, to keep it simple, maybe just render after title?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [January 20, 2018, 4:04am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/138 "2018-01-20T04:04:05Z")
Iāve [fixed the mobile outlet](https://github.com/angusmcleod/discourse-topic-previews/commit/6ff037ae8a4ab537238570942e8eb02577964525), but Iām sorry, I think it makes more sense for the social style to have the outlet in the footer by default - itās where all the other topic info is in that style.
If you want to move the element on your instance (i.e. more than just using CSS), you can use jQuery:
```plaintext
Ember.run.scheduleOnce('afterRender', () => {
const $topicRating = $('.topic-rating');
const $target = $(target);
$topicRating.appendTo($target);
});
```
This will make the topic-rating element the first child of whatever container you want to put it in.
---
### Author:  [@dalerka](https://meta.discourse.org/u/dalerka)
#### Post date: [January 20, 2018, 5:11am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/139 "2018-01-20T05:11:22Z")
No, problem at all! As long as things are kept consistent across updates š
Thank you for all your hard work!
---
### Author:  [@Anshul\_TM](https://meta.discourse.org/u/Anshul_TM)
#### Post date: [February 1, 2018, 8:13am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/140 "2018-02-01T08:13:35Z")
Hey @angus,
I want to extend this to allow for multiple ratings instead of just one.
e.g. in my case Train reviews can include punctuality, cleanliness, food.
Iāve cloned the repo and exploring the code, a few pointers will be very helpful.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [February 2, 2018, 2:21am UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/141 "2018-02-02T02:21:22Z")
Do you mean multiple ratings on one topic? Yes that could be done I suppose. Basically, youāll need to add in additional custom fields, wherever the current rating custom fields are. And some conditional logic to handle the calculation of the average separately for each type.
For example, you may end up with something like this for saving the rating when a post is created:
```plaintext
DiscourseEvent.on(:post_created) do |post, opts, user|
if opts[:rating] || opts[:rating_type2]
post.custom_fields['rating'] = opts[:rating] if opts[:rating]
post.custom_fields['rating_type2'] = opts[:rating_type2] if opts[:rating_type2]
post.custom_fields["rating_weight"] = 1
post.save_custom_fields(true)
RatingsHelper.handle_rating_update(post, opts)
end
///
```
Then add some conditional logic in `handle_rating_update` to calculate averages and push those averages to the topic, for each type of rating.
---
### Author:  [@parisa](https://meta.discourse.org/u/parisa)
#### Post date: [February 7, 2018, 5:41pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/142 "2018-02-07T17:41:53Z")
The newest version makes opening the rating topic too slow. for example if other topics would open in two seconds, rating topic opens in 5 seconds.
on the other hand is there an option to remove stars from below topic title and just let them be inside the topic?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [February 10, 2018, 1:14pm UTC](https://meta.discourse.org/t/topic-ratings-plugin/39578/143 "2018-02-10T13:14:13Z")
> [@parisa](#):
>
> The newest version makes opening the rating topic too slow. for example if other topics would open in two seconds, rating topic opens in 5 seconds.
Can you give me an example of this? In my own testing on localhost, and on [https://discourse.angusmcleod.com.au](https://discourse.angusmcleod.com.au), rating topics load at the same speed as any other topic.
> [@parisa](#):
>
> on the other hand is there an option to remove stars from below topic title and just let them be inside the topic?
Iāve added settings for the average ratings in the topic and in the topic list:
[https://github.com/angusmcleod/discourse-ratings/commit/c1ada78cbd12d6422b3fefa1faae2022c4447f04](https://github.com/angusmcleod/discourse-ratings/commit/c1ada78cbd12d6422b3fefa1faae2022c4447f04)
[Previous page](https://meta.discourse.org/t/topic-ratings-plugin/39578.md?page=6)
[Next page](https://meta.discourse.org/t/topic-ratings-plugin/39578.md?page=8)