Skip to content

nodebb-plugin-reactions not working @v1.0.2 with Harmony theme

Solved General
47 3 16.5k 1
  • @phenomlab I’m very thankful for taking your time and fixing most of the peer dependencies. That’s really strange

    wrote on last edited by phenomlab
    #10

    @dave1904 I’ll look more into this tomorrow, but you could

    1. Upgrade npm
    2. Stop NodeBB
    3. Run the NodeBB upgrade process again
    4. Start NodeBB
    5. Test
  • @dave1904 I’ll look more into this tomorrow, but you could

    1. Upgrade npm
    2. Stop NodeBB
    3. Run the NodeBB upgrade process again
    4. Start NodeBB
    5. Test
    wrote on last edited by
    #11

    @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

    1. Upgrade npm
    2. Stop NodeBB
    3. Run the NodeBB upgrade process again
    4. Start NodeBB
    5. Test

    I tried your steps but still no success unfortunately

  • @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

    1. Upgrade npm
    2. Stop NodeBB
    3. Run the NodeBB upgrade process again
    4. Start NodeBB
    5. Test

    I tried your steps but still no success unfortunately

    wrote on last edited by
    #12

    @dave1904 what’s the output of npm --version and node --version ?

  • @dave1904 what’s the output of npm --version and node --version ?

    wrote on last edited by
    #13

    @phenomlab

    npm --version
    9.6.5

    node --version
    v18.16.0

  • @phenomlab

    npm --version
    9.6.5

    node --version
    v18.16.0

    wrote on last edited by
    #14

    @dave1904 hmm. Nothing wrong with those.

  • wrote on last edited by dave1904
    #15

    @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?

  • @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?

    wrote on last edited by
    #16

    @dave1904 if you stop NodeBB and use ./nodebb upgrade, they should appear in the console.

  • wrote on last edited by
    #17
    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?

  • 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?

    wrote on last edited by
    #18

    @dave1904 yes, it does.

  • wrote on last edited by
    #19

    @dave1904 did you manage to get any further with this ?

  • wrote on last edited by
    #20

    @phenomlab I gave up on this yesterday

  • @phenomlab I gave up on this yesterday

    wrote on last edited by
    #21

    @dave1904 Ok. I’ll login again later and take a look at this. I still think it’s related to dependencies.

  • wrote on last edited by phenomlab
    #22

    @dave1904 I’ve managed to resolve this issue - see below

    204f1bd9-ede2-4c07-a357-a09ccddb379b-image.png

    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

    1. Issue ./nodebb reset -t - this essentially resets everything back to default - be warned, as it will strip literally all customisations also
    2. Reactivate only the essential plugins (typically those that come with the stock installation)
    3. Install and activate nodebb-plugin-emoji, nodebb-plugin-emoji-android and @nodebb/nodebb-plugin-reactions@latest
    4. Rebuild and restart

    Obviously, 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.

  • phenomlab phenomlab has marked this topic as solved on
  • wrote on last edited by
    #23

    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?

  • 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?

    wrote on last edited by
    #24

    @dave1904 yes, that’s the route I would take.

  • @dave1904 yes, that’s the route I would take.

    wrote on last edited by
    #25

    @phenomlab

    I will try this later and keep you updated.

  • @phenomlab

    I will try this later and keep you updated.

    wrote on last edited by
    #26

    @dave1904 any update? More to the point, so you need any help?

  • @dave1904 any update? More to the point, so you need any help?

    wrote on last edited by
    #27

    @phenomlab

    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!

  • @phenomlab

    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!

    wrote on last edited by
    #28

    @dave1904 ok but I think you might need the steps I provided in previous posts in this thread.

  • wrote on last edited by dave1904
    #29

    @phenomlab A complete reset feels a bit like an overkill for one plugin not working which, as julian I think mentioned, could be re-developed soon. But the plugin keeps active on dev, even after activating many plugins again.


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics