Topic Ratings Plugin

Hey! Just to clarify, you’re having issues with this plugin on IE 11? Could you describe the issue in some detail? Thanks.

In Chrome, normal
IE 11 ver : New topic -> Enter rating -> No rating value

IE 11 : There is no value attribute.

New Topic rating view(IE 11) : <input class="ember-view" id="ember1362" type="radio">
New Topic rating view(Chrome) :<input id="ember1996" type="radio" value="3" class="ember-view">

directory : discourse-ratings\assets\javascripts\discourse\templates\components
source : {{rating-star value=star rating=rating enabled=enabled}}<i></i>

value=star is Not applicable

Ah interesting. Thanks for this. Would you mind making a bug report for this here:

Thanks :+1:

1 Like

I tried to write.

See the url below

1 Like

Hi Angus, I love your plugin.

For my forum, I recently changed the setting to require a moderator to approve topics for new users. But during the approval process, the rating the user gave their topic disappears. Is there a way to prevent this memory loss?

This is the flow of my problem:

  1. A new user creates a new topic with a rating. They must wait for a moderator to approve their topic.
  2. The moderator sees the post that needs approval (in the /review window, no rating is present).
  3. The moderator approves the topic.
  4. On the site, both inside the topic and on the Latest page, no rating is associated to the topic.

Am I missing a setting somewhere or was the plugin not built to work with post approval?

Thank you!

1 Like

@Owen_Neuber Thanks for this feedback. This sounds like bug. I’m going to work on that @영광_임 posted later today, so I’ll take a look at this as well. Please post a full report here:

Hi Angus, I love your plugin.
Is there a way to statistics the star score received for each user?
Which table should I look at?

I want to give a prize to a user who scores a lot of stars.

Yes, ratings are stored in post_custom_fields as ‘rating’, so you just need to join post to post_custom_fields and select the user_id of post and value of post_custom_field’s with the name ‘rating’.

Thank you
I like rating-plugin

hey Angus. Just tried this by adding to app.yml and breaks the rebuild when I use the launcher. Is this added thru the admin settings or some other issue?

Anyone know how to get this done right? I’ve tried adding the whole section.

hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone

I tried adding just this

- mkdir -p plugins - git clone

I’ve tried just the normal way of -git clone

No matter what I do it doesn’t allow the launcher to rebuild the app.

This is yaml syntax and it doesn’t allow tabs to begin with. There may be other issues but make sure you’re using spaces and not tabs for indents.

Thanks. I copied and pasted it from the github so maybe that’s the reason. Should it be the full section added or just the git clone part?

Check this out.

1 Like

Yeah that’s just the standard. I tried that. Where I’m guessing my issue is with the -mkdir -p plugins line.

Yes. you don’t need to do that.

Ok so heres the error i get

I, [2019-08-27T09:33:32.898647 #20]  INFO -- : 
I, [2019-08-27T09:33:32.898807 #20]  INFO -- : > cd /var/www/discourse/plugins && git clone
Cloning into 'discourse-ratings'...
I, [2019-08-27T09:33:35.337452 #20]  INFO -- : 
I, [2019-08-27T09:33:35.337768 #20]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2019-08-27T09:33:35.341827 #20]  INFO -- : 
I, [2019-08-27T09:33:35.342189 #20]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2019-08-27T09:33:35.344659 #20]  INFO -- : 
I, [2019-08-27T09:33:35.344783 #20]  INFO -- : > mkdir -p /var/nginx/cache
I, [2019-08-27T09:33:35.347471 #20]  INFO -- : 
I, [2019-08-27T09:33:35.348471 #20]  INFO -- : Replacing pid /run/; with daemon off; in /etc/nginx/nginx.conf
I, [2019-08-27T09:33:35.348857 #20]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server; } in /etc/nginx/conf.d/discourse.conf
I, [2019-08-27T09:33:35.349118 #20]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2019-08-27T09:33:35.349463 #20]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2019-08-27T09:33:35.349744 #20]  INFO -- : > echo "done configuring web"
I, [2019-08-27T09:33:35.352366 #20]  INFO -- : done configuring web

I, [2019-08-27T09:33:35.352807 #20]  INFO -- : > cd /var/www/discourse && gem update bundler
I, [2019-08-27T09:33:40.884054 #20]  INFO -- : Updating installed gems
Nothing to update

I, [2019-08-27T09:33:40.884237 #20]  INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
chown: cannot dereference '/var/www/discourse/plugins/discourse-ratings/discourse-ratings': No such file or directory
I, [2019-08-27T09:33:42.396049 #20]  INFO -- : 
I, [2019-08-27T09:33:42.396498 #20]  INFO -- : Terminating async processes
I, [2019-08-27T09:33:42.396661 #20]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 74
I, [2019-08-27T09:33:42.396733 #20]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 191
191:signal-handler (1566898422) Received SIGTERM scheduling shutdown...
2019-08-27 09:33:42.397 UTC [74] LOG:  received fast shutdown request
2019-08-27 09:33:42.418 UTC [74] LOG:  aborting any active transactions
2019-08-27 09:33:42.424 UTC [74] LOG:  worker process: logical replication launcher (PID 83) exited with exit code 1
2019-08-27 09:33:42.424 UTC [78] LOG:  shutting down
2019-08-27 09:33:42.440 UTC [74] LOG:  database system is shut down
191:M 27 Aug 2019 09:33:42.447 # User requested shutdown...
191:M 27 Aug 2019 09:33:42.447 * Saving the final RDB snapshot before exiting.
191:M 27 Aug 2019 09:33:42.880 * DB saved on disk
191:M 27 Aug 2019 09:33:42.880 # Redis is now ready to exit, bye bye...

Pups::ExecError: cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+ failed with return #<Process::Status: pid 360 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "find $home ! -user discourse -exec chown discourse {} \\+"]}
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
1 Like

@angus I think its related to the plugin. I can repro that.


@Garrick Sorry for the slow response here. I just pushed a fix. I also moved the repository, so before rebuilding again, please update the link to

The old link will still work, but better to have the actual one. Let me know how that goes.