@dave1904 No issues. See my comment above about npm
@dave1904 I’ll look more into this tomorrow, but you could
npm@phenomlab said in nodebb-plugin-reactions not working @v1.0.2 with Harmony theme:
@dave1904 I’ll look more into this tomorrow, but you could
- Upgrade
npm- Stop NodeBB
- Run the NodeBB upgrade process again
- Start NodeBB
- Test
I tried your steps but still no success unfortunately
@dave1904 what’s the output of npm --version and node --version ?
@dave1904 hmm. Nothing wrong with those.
@phenomlab After upgrading npm and node I did upgrade nodebb again but that didn’t do any changes. Can you please tell me which commands I have to use to see those peer dependencies listed in the screenshot you sent me via pn?
@dave1904 if you stop NodeBB and use ./nodebb upgrade, they should appear in the console.
2. Bringing base dependencies up to date... started
up to date, audited 1180 packages in 8s
139 packages are looking for funding
run `npm fund` for details
Looks better doesn’t it?
@dave1904 yes, it does.
@dave1904 did you manage to get any further with this ?
@phenomlab I gave up on this yesterday
@dave1904 Ok. I’ll login again later and take a look at this. I still think it’s related to dependencies.
@dave1904 I’ve managed to resolve this issue - see below
It seems that there is a conflicting plugin somewhere that causes reactions to not fire. Not sure which one it is, but below are the steps I took to resolve
./nodebb reset -t - this essentially resets everything back to default - be warned, as it will strip literally all customisations alsonodebb-plugin-emoji, nodebb-plugin-emoji-android and @nodebb/nodebb-plugin-reactions@latestObviously, these steps are quite dramatic and would mean some downtime for your forum. You’d also need to put everything back the way it was in terms of CSS, Widgets, etc, so quite invasive. My suggestion would be to try a minimal approach on prod to see if we can get that to work without having to use the somewhat “sledgehammer” approach above.
undefined phenomlab has marked this topic as solved on
Again, thank you very much for taking your time. Very happy that you could fix it. 
I guess the minimal approach would be to deactivate plugins one after another, rebuild and restart and see if the reactions plugin works?
@dave1904 yes, that’s the route I would take.
I will try this later and keep you updated.
@dave1904 any update? More to the point, so you need any help?
At the moment I try it the other way around so avoid downtime on prod: Activating plugins on dev to see if reactions stops working. Will keep you updated!
@dave1904 ok but I think you might need the steps I provided in previous posts in this thread.
