Damn, I can’t believe I missed the plugin. I knew it, but I could not find it. Thanks for correcting me; I appreciate it! I have always had a hard time with the search ahah.
(EDIT: and I just noticed I completely missed the first message in the deprecated plugin
)
Thanks for the replies. That’s good to know about the data explorer and the marketplace. The official plugin won’t work for me, unfortunately. I’m curious which requirements this plugin cannot do - is it just the rating on posts (vs topics)?
It’s simply not designed to work this way. It’s always possible to modify it, and that’s what marketplace place is for. ![]()
Hello, May I ask if this problem has been solved? I had the same problem. It seems that this problem could be solved by manually adjusting the height of the reply menu, but it would affect every user’s first-time experience. It also reduces the area of the topic you see. I think the best way to solve this problem is to arrange the text horizontally instead of vertically
I just found a deprecation notice in the developer console of my browser:
deprecation-identify-source.js:15 DEPRECATION: [PLUGIN discourse-ratings] The
topicproperty path was used in thediscourse/plugins/discourse-ratings/discourse/templates/connectors/topic-category/topic-tip-container.hbstemplate without usingthis. This fallback behavior has been deprecated, all properties must be looked up onthiswhen used in the template: {{this.topic}} [deprecation id: ember-this-fallback.this-property-fallback] This will be removed in ember-this-fallback n/a. See Resolving the `this-property-fallback` deprecation for more details.
Just wanted to bring this to attention - although I cannot fix it myself. ![]()
Could you check this plugin?
It has error with the latest version of discourse.
Detected themes/plugins which are incompatible with the new 'glimmer' post stream. Falling back to the old implementation.
The following plugins and/or themes are using deprecated APIs
Plugin is broken with the post stream changes.
A kind request to @jumagura to please help update this super useful plugin.
[Admin Notice] Plugin ‘discourse-ratings’ contains code which needs updating. (id:discourse.post-stream-widget-overrides)
Seems like it’s not being maintained anymore… we are also encountering deprecation errors on 2025.12.0
Thanks to @RGJ. This plugin is now updated ![]()
The plugin’s functionality has completely vanished from my forum now. In the admin interface I see:
The forum posts in the category where users were previously able to rate topics show no ratings widgets anymore.
If I recall correctly, I had to choose a category to enable the ratings in the settings or use a special tag for the category. But I could find zero documentation for that in GitHub - paviliondev/discourse-ratings: A Discourse plugin that lets you use topics to rate things · GitHub and this thread is too huge to read through all posts for any hints.
Any idea what is wrong with my forum? It is up to date.
There are leftovers (widget) which should be removed, from Compatibility update for v2026.01 by communiteq · Pull Request #76 · paviliondev/discourse-ratings · GitHub
I made a PR to fix the issue:
I think those widgets are exactly what I am missing. Previously one could use stars to rate the topic. But maybe it works differently now?
Correct, it has been replaced in the previous PR I linked above with components.
But the PR did not remove the widget files and you get an error because it references paths that doesn’t exist anymore in core.
Thank you for pointing that out @Arkshine and my apologies for making a mess of this.
To make it even a bigger mess, I completely modernized the plugin last week (gjs + Glimmer + cleanup), but I did not make a pull request yet because I was still testing it.
It’s here GitHub - communiteq/discourse-ratings: A Discourse plugin that lets you use topics to rate things · GitHub
Oh sorry, then I am probably just too clueless about Discourse. I have no idea what widgets or components are since I am just a user, not a programmer. ![]()
Do the existing widget files lead to errors that stop the components from working? Then I am super happy and thankful about your PR!
No worry! You understand correctly. The PR removes any references of widget and making the plugin work again.
Note the PR has been merged, if not done already, you can update the plugin.
Works like a charm, thank you so much!
@jumagura @angus @merefield i have Glimmerized and overhauled the plugin and made a PR. Could one of you please have the second pair of eyes on it and merge it?
I’ve contributed to and merged the PR, thanks @RGJ ![]()
