Thanks for setting up the VPS. I was able to change update the ratings on your VPS too. I suspect you’re trying to do the thing via an API? I can assist you with that on a PM.
Just be clear, can you confirm everything works fine with the discourse UI and only an issue while using the API?
Although, I see a small issue with the category settings but that’s not completely related I guess?
p.s.
I think I know what you are pointing at. Are you pointing at the fact that when you open the composer with Uncategorized selected, it doesn’t show any rating options in the UI. Yes, that’s a bug but I couldn’t gather that from your explaination
Not sure what issue you’re referring, but it should not be related to the event generated.
This is NOT my issue, this is NOT what I’ve reported. I’m really confused, don’t you see the event bug, despite the screenshot, videos & explanations?
Will try again: whatever you post with composer or with the API, the generated event, here post_created or post_edited should include the actual ratings values after saving. Currently it includes the previous value.
E.g.:
I post a message with rating of 5:
current behavior: post_created event includes ratings: []
expected behavior: post_created event should include the value of 5: ratings: [value: 5, ...]
I edit the same message with rating of 1:
current behavior: post_edited event includes ratings: [value: 5, ...]
expected behavior: post_edited event should include the new value of 1: ratings: [value: 1, ...]
You used the word event but it would have sufficed for you to have said webhook event. Our current code doesnt pass the rating details correctly to the webhook payload.
I do acknowledge the confusion on my part too.
I think its an intresting usecase though. Can you create a feature request on our Pavilion instance?
Come one, I know my english is not the best, but I showed you many times with screenshot and video, the webhook events panel, describing exactly the ratings field value issue, with the name of the events post_created/post_edited (with code formatting) which can be only webhook event names…
I said feature request coz we don’t gurantee(yet) that the webhook payload will reflect the custom fields we create for our plugins. But we’re flexible on what the reports should be called.
Hi @hosna
I do realize we’re a bit behind in terms of documention how the new ratings system works for the admin. Although, there’s this topic which can help you get through initially. Rating Types - Ratings - Pavilion
Secondly, if you can point out the pain points in setting up the plugin, I can help you out via a PM and can write more docs which would be helpful for others too.
Was playing around with the plugin to see how it works and as of now ( Discourse 5cff198aba with latest Ratings Plugin), there is a small bug that I thought I would let you guys know about:
If you try to filter the replies on a topic per user, the result is blank, does not show any results. It does “finish” loading/filtering, but it’s just blank, empty.
This happens with both the new reply filter option and the default one. However, the new message/reply filter option does work perfectly and it is my understanding that this new filter leverages on the user-reply-filter that doesn’t seem to work when the Topic Ratings Plugin is enabled.
Can have a small feature that restrict rating base on the account age / days visited / posts read / topics posted etc to prevent user creating new accounts and manipulate the ratings?
