Skip to content

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

Solved General
47 3 16.8k 1
  • Hi,

    for me the @nodebb-plugin-reactions @v1.0.2 is not working on Harmony theme (nodebb v3). The reaction button doesn’t show up.

    As I know for @phenomlab it is working without any problems. There are no errors in the nodebb log so I don’t know exactly where to look at. Harmony is importing the reactions.tpl in post.tpl and I didn’t do any changes. Everything should be alright. Maybe there is a plugin interferring with nodebb-plugins-reactions.

    Does anyone have an idea? It worked without problems on v2.

    Best regards
    David

    wrote on last edited by
    #2

    @dave1904 hi David can you PM me your server details plus an account that has admin rights there and I’ll take a look.

  • wrote on last edited by DownPW
    #3

    @dave1904

    strange, works great on my development environment :

    image.png

  • @dave1904

    strange, works great on my development environment :

    image.png

    wrote on last edited by
    #4

    @DownPW said in nodebb-plugin-reactions not working @v1.0.2 with Harmony theme:

    @dave1904

    strange, works great on my development environment :

    image.png

    There is something messed up with peer dependencies on my installation. @phenomlab is looking at it right now.

  • wrote on last edited by DownPW
    #5

    Great, you’re in good hands 🙂

  • wrote on last edited by
    #6

    If needed or if it can be used by someone using this plugin, here is my code for a dark theme :

    /*----------------------------------------------------------------------------*/
    /*----------------------     nodebb-plugin-reaction     ----------------------*/
    /*----------------------------------------------------------------------------*/
    
    /* Popup bg */
    .emoji-dialog {
        border: 1px solid var(--bs-border-color);
        background: var(--bs-card-cap-bg);
    }
    
    /* Tab bg */
    .nav-tabs .nav-item.show .nav-link, .nav-tabs .nav-link.active {
        --bs-nav-tabs-link-active-color: var(--bs-body-color-muted);
        --bs-nav-tabs-link-active-bg: var(--bs-body-navbar-active);
        --bs-nav-tabs-link-active-border-color: var(--bs-border-color);
    }
    
    /* Tab Hover */
    .nav-tabs .nav-link:hover {
      border: var(--bs-nav-tabs-border-width) solid var(--bs-border-color);
    }
    
    /* Add reaction button */
    span.reaction-add {
        color: var(--bs-link-color);
    }
    

    cya

    🙂

  • @DownPW said in nodebb-plugin-reactions not working @v1.0.2 with Harmony theme:

    @dave1904

    strange, works great on my development environment :

    image.png

    There is something messed up with peer dependencies on my installation. @phenomlab is looking at it right now.

    wrote on last edited by phenomlab
    #7

    @dave1904 I’ve managed to fix most of the peer dependencies but there are still some really strange issues with this instance. I need to look at this in a bit more detail unfortunately as it’s like trying to chase a ghost presently 😕

    What I am seeing is the below

    npm WARN @apidevtools/swagger-parser@10.1.0 requires a peer of openapi-types@>=7 but none is installed. You must install peer dependencies yourself.
    npm WARN @nodebb/nodebb-plugin-reactions@1.0.2 requires a peer of nodebb-plugin-emoji@^4.0.0 but none is installed. You must install peer dependencies yourself.
    npm WARN cosmiconfig-typescript-loader@4.3.0 requires a peer of cosmiconfig@>=7 but none is installed. You must install peer dependencies yourself.
    npm WARN textcomplete.contenteditable@0.1.1 requires a peer of textcomplete@^0.14.2 but none is installed. You must install peer dependencies yourself.
    

    The second line I would not expect because that dependency is satisfied by nodebb-plugin-emoji@5.0.7 which is now installed. Hard to know what the peer dependencies are currently.

    EDIT: You have a really old npm version at 6.14.17. This should be upgraded and may solve the problems. For example, mine is v9.

    Additionally, using the command
    npm config set legacy-peer-deps true should auto resolve issues, but likely npm needs upgrading.

  • wrote on last edited by
    #8

    @phenomlab I’m very thankful for taking your time and fixing most of the peer dependencies. That’s really strange

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

    @dave1904 No issues. See my comment above about npm

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


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
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    phenomlab
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Modify the tagging behavior in NodeBB

    Locked General tagging harmony
    11
    3 Votes
    11 Posts
    4k Views
    phenomlab
    For anyone else following this thread https://community.nodebb.org/topic/17402/change-in-reply-to-xxxx-text And https://github.com/NodeBB/NodeBB/commit/f2152953cddd3247746ef393516b0a53ba7750a4
  • Collapsing blockquotes on Harmony

    General nodebb harmony collapsible quotes
    2
    1
    2 Votes
    2 Posts
    987 Views
    phenomlab
    @dave1904 that’s a really good point actually. I know it was there previously on Persona, but you’re right - no such function exists on harmony. However, putting something in place to mimick the behaviour of Persona won’t be hard from the js standpoint, although I wonder if perhaps we should ask the NodeBB developers is this feature was overlooked?
  • Issues with 2nd NodeBB installation

    Solved General
    22
    3 Votes
    22 Posts
    10k Views
    phenomlab
    @cagatay yes, that will be fine. Just watch for potential caching conflicts as you will have two sites writing to the one instance of iframely.
  • Nodebb as blogging platform

    General blog
    10
    5 Votes
    10 Posts
    6k Views
    phenomlab
    @qwinter I’ve extensive experience with Ghost, so let me know if you need any help.
  • Discord Login - OAuth2 - NodeBB

    Solved General discord nodebb plugins
    32
    11 Votes
    32 Posts
    14k Views
    phenomlab
    @Galaxian hi, and welcome to Sudonix Can you check your config.json file and ensure that your forum URL doesn’t have a trailing backslash or forward slash in it ? This was the issue @Sampo2910 had.
  • NodeBB Blog Comments

    General nodebb blog
    3
    1 Votes
    3 Posts
    2k Views
    phenomlab
    @kurulumu-net Not specifically, but you should review this post from the very large thread as it will save you a lot of time. There’s significant customisation on the Ghost side of things, but not in NodeBB https://community.nodebb.org/post/86022
  • Nodebb best plugins

    General nodebb plugins
    18
    7 Votes
    18 Posts
    7k Views
    crazycells
    @phenomlab thanks