Thanks, Benjamin. The options page for discourse-reaction looked normal (and the
emoji-icon was properly displayed on the
add-emoji-button, if that’s what you were after). No 404 errors in my network console.
Here’s what I was able to do:
- Imported a backup from my production site (running v2.7.5) to a testing system, on an instance running v2.7.8 beta2 (commit
fc61a7c0) and following the
tests-passed Git revision. At that point, the discourse-reaction notification icon would still be displayed.
- Upgraded docker_manager (from
91bf85a) : icon is still displayed.
- Upgraded discourse-reactions (from
6b0ee89 : icon is no longer displayed.
- Upgraded Discourse (from 2.8.0.beta2
fc61a7c0de → 2.8.0.beta2
800c6e1a) : icon is displayed again.
So it seems that newer versions of discourse-reactions are dependent upon changes implemented in the 2.8.0 branch, yet these newer versions are still made available for upgrade on sites that follow the stable branch.
Having looked at commit logs, I’m thinking that discourse-reactions’s
fdb0cab is what’s causing my issue.
What would be the less complicated way to downgrade this plugin to a prior version?