Skip to content

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

Solved General
  • @dave1904 what was the output of the upgrade? Did it complain about any missing dependencies?

  • @phenomlab

    I couldn’t see that:

    Updating NodeBB...
    
    1. Updating package.json file with defaults...  OK
    
    2. Bringing base dependencies up to date...  started
    
    up to date, audited 1113 packages in 7s
    
    131 packages are looking for funding
      run `npm fund` for details
    
    13 vulnerabilities (7 moderate, 6 high)
    
    To address issues that do not require attention, run:
      npm audit fix
    
    To address all issues possible (including breaking changes), run:
      npm audit fix --force
    
    Some issues need review, and may require choosing
    a different dependency.
    
    Run `npm audit` for details.
    
    3. Checking installed plugins for updates...Checking installed plugins and themes for updates...   OK
    
    A total of 1 package(s) can be upgraded:
    
      * nodebb-plugin-question-and-answer (1.0.17 -> 1.0.18)
    
    Proceed with upgrade (y|n)? y
    
    Upgrading packages...
    
    4. Updating NodeBB data store schema...
    Parsing upgrade scripts... 
    OK | 0 script(s) found, 125 skipped
    Schema update complete!
    
    
    5. Rebuilding assets...  started
    2023-05-01T21:02:24.095Z [4567/261222] - info: [build] Building in series mode
    2023-05-01T21:02:24.096Z [4567/261222] - info: [build]         plugin static dirs  build started
    2023-05-01T21:02:24.105Z [4567/261222] - info: [build]         plugin static dirs  build completed in 0.009sec
    2023-05-01T21:02:24.106Z [4567/261222] - info: [build]          requirejs modules  build started
    2023-05-01T21:02:24.254Z [4567/261222] - info: [build]          requirejs modules  build completed in 0.148sec
    2023-05-01T21:02:24.254Z [4567/261222] - info: [build]           client js bundle  build started
    2023-05-01T21:02:24.259Z [4567/261222] - info: [build]           client js bundle  build completed in 0.005sec
    2023-05-01T21:02:24.260Z [4567/261222] - info: [build]            admin js bundle  build started
    2023-05-01T21:02:24.261Z [4567/261222] - info: [build]            admin js bundle  build completed in 0.001sec
    2023-05-01T21:02:24.261Z [4567/261222] - info: [build]         client side styles  build started
    Deprecation Warning on line 68, column 52 of node_modules/bootswatch/dist/flatly/_variables.scss: 
    !default should only be written once for each variable.
    This will be an error in Dart Sass 2.0.0.
       ╷
    68 │ $nav-link-padding-y:                .5rem !default !default;
       │                                                    ^^^^^^^^
       ╵
    
    Deprecation Warning on line 70, column 56 of node_modules/bootswatch/dist/flatly/_variables.scss: 
    !default should only be written once for each variable.
    This will be an error in Dart Sass 2.0.0.
       ╷
    70 │ $nav-link-disabled-color:           $gray-600 !default !default;
       │                                                        ^^^^^^^^
       ╵
    
    2023-05-01T21:02:30.523Z [4567/261222] - info: [build]         client side styles  build completed in 6.262sec
    2023-05-01T21:02:30.524Z [4567/261222] - info: [build] admin control panel styles  build started
    2023-05-01T21:02:35.223Z [4567/261222] - info: [build] admin control panel styles  build completed in 4.698sec
    2023-05-01T21:02:35.226Z [4567/261222] - info: [build]                  templates  build started
    2023-05-01T21:02:36.223Z [4567/261222] - info: [build]                  templates  build completed in 0.997sec
    2023-05-01T21:02:36.223Z [4567/261222] - info: [build]                  languages  build started
    2023-05-01T21:02:39.308Z [4567/261222] - info: [build]                  languages  build completed in 3.085sec
    2023-05-01T21:02:39.309Z [4567/261222] - info: [build] Bundling with Webpack.
    2023-05-01T21:03:07.379Z [4567/261222] - info: [build] Bundling took 23607 ms
    2023-05-01T21:03:07.394Z [4567/261222] - info: [build] Asset compilation successful. Completed in 43.284sec.
    
    
                                                NodeBB Upgrade Complete!
    
  • @dave1904 yes, that looks clean. On prod, could you provide the output of

    ./nodebb plugins

    I’m specifically interested in the version numbers of the emoji and reactions plugins. However, as dev is a replica of prod, I suspect the same “fix” (as heavy handed as it is) is needed for prod.

    However, I do agree that this approach isn’t desirable for obvious reasons.

  • Yes, I also have that bad feeling only reset would help. Anyway here is the output:

    Active plugins:
            * @nodebb/nodebb-plugin-reactions@1.0.2 (installed, enabled)
            * nodebb-plugin-2factor@7.0.5 (installed, disabled)
            * nodebb-plugin-beep@0.4.7 (installed, disabled)
            * nodebb-plugin-composer-default@10.0.48 (installed, enabled)
            * nodebb-plugin-contact-page@1.3.0 (installed, disabled)
            * nodebb-plugin-custom-pages@2.0.3 (installed, enabled)
            * nodebb-plugin-customize@3.0.0 (installed, disabled)
            * nodebb-plugin-dbsearch@6.0.0 (installed, enabled)
            * nodebb-plugin-email-blacklist@2.0.0 (installed, disabled)
            * nodebb-plugin-emoji@5.0.6 (installed, enabled)
            * nodebb-plugin-emoji-android@4.0.0 (installed, disabled)
            * nodebb-plugin-emoji-one@4.0.0 (installed, enabled)
            * nodebb-plugin-emoji-vital@4.0.0 (installed, disabled)
            * nodebb-plugin-markdown@12.0.2 (installed, enabled)
            * nodebb-plugin-mentions@4.1.0 (installed, enabled)
            * nodebb-plugin-newsletter@0.10.2 (installed, disabled)
            * nodebb-plugin-night-mode@1.0.7 (installed, disabled)
            * nodebb-plugin-ns-likes@3.0.0 (installed, disabled)
            * nodebb-plugin-ntfy@1.0.15 (installed, disabled)
            * nodebb-plugin-poll@3.0.4 (installed, enabled)
            * nodebb-plugin-question-and-answer@1.0.18 (installed, enabled)
            * nodebb-plugin-recent-cards@3.1.11 (installed, enabled)
            * nodebb-plugin-shoutbox@2.0.4 (installed, disabled)
            * nodebb-plugin-spam-be-gone@2.0.6 (installed, enabled)
            * nodebb-plugin-tenor-gif@3.0.0 (installed, enabled)
            * nodebb-plugin-youtube-embed@0.6.9 (installed, enabled)
            * nodebb-rewards-essentials@0.2.3 (installed, enabled)
            * nodebb-theme-harmony@1.0.1 (installed, enabled)
            * nodebb-theme-lavender@7.0.9 (installed, disabled)
            * nodebb-theme-peace@2.0.19 (installed, disabled)
            * nodebb-theme-persona@13.0.56 (installed, disabled)
            * nodebb-theme-slick@2.0.2 (installed, disabled)
            * nodebb-theme-vanilla@12.1.19 (installed, disabled)
            * nodebb-widget-essentials@7.0.9 (installed, enabled)
            * nodebb-widget-ns-stats@3.0.0 (installed, disabled)
    
  • Instead of a complete reset, would you be open to disabling all plugins apart from the stock ones, plus emoji, emoji android, and reactions?

    Obviously you’ll need to perform a rebuild and restart.

  • Do you know if I would have to reconfigure all the disabled plugins?

  • @dave1904 no, that won’t be necessary. Disabling them means that they won’t be loaded, but will keep their settings.

  • @phenomlab Yes I just thought I could have checked that myself on dev 😄 Yes I would try that but is there a list of the stock plugins?

  • @dave1904 umm. That’s a good question. I’m not sure there is. Let’s start with the below

    @nodebb/nodebb-plugin-reactions
    nodebb-plugin-composer-default
    nodebb-plugin-emoji
    nodebb-plugin-emoji-android
    nodebb-plugin-markdown
    nodebb-plugin-mentions
    nodebb-theme-harmony
    

    If reactions starts playing ball, then we enable the other extensions.

  • @phenomlab Thanks. I will try it tomorrow as it’s already late here

  • @dave1904 yep. You know where I am if you need me.

  • @dave1904 just checking in - any joy ?

  • Hi @phenomlab , I just disabled all the plugins except the mentioned ones, rebuilt and restarted the forum but still the plugin doesn’t fire. I guess I really have to reset the forum then.

  • @dave1904 sadly, yes, seems there’s no other viable route here.

  • @phenomlab Yes but for me that’s not worth it, I would rather try to develop a new plugin (featuring notifications) hehe.

  • @dave1904 just coming back to this thread as @DownPW and I both experienced issues with other plugins today, and the fix was to use the plugin ordering in the ACP and move the Harmony theme to the very top so it comes before everything else in terms of other plugins.

    It might be worth at least trying this to see if it gives you a result rather than the previous bulldozer approach. Thinking about it, the previous fix I proposed is along the same lines and disabling plugins does in fact change the order when they are enabled again, so this is definitely worth a try.

    Let me know how you get on.


Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • Nodebb design

    Solved General
    2
    1 Votes
    2 Posts
    282 Views

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

  • 1 Votes
    4 Posts
    312 Views

    @Vijay-Kumavat-0 I think you’d be better off customising the plugin above to be honest. It seems like you’d be reinventing the wheel otherwise.

    I’d modify

    /nodebb/node_modules/nodebb-rewards-essentials/lib/conditions.js
    /nodebb/node_modules/nodebb-rewards-essentials/lib/rewards.js

    These seem to be the two files that control what is in the dropdown lists.

  • Plugin to show images in teasers

    General
    6
    2 Votes
    6 Posts
    368 Views

    @dave1904 I’d start by adding a console.log function to hookData so you can see what is being returned

    return hookData; console.log(hookData):
  • Welcome to NodeBB V3!

    Pinned Moved General
    1
    0 Votes
    1 Posts
    240 Views
    No one has replied
  • Issues with 2nd NodeBB installation

    Solved General
    22
    3 Votes
    22 Posts
    1k Views

    @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 v2.4.0

    Solved General
    3
    2 Votes
    3 Posts
    411 Views

    @phenomlab As always…Thank you.

    Worked for me.

  • NodeBB vs Flarum for a non developer

    Solved General
    17
    10 Votes
    17 Posts
    1k Views

    @marusaky That’s really easily done. I think the docs need updating for the latest release. Did you land up on the 18.x train ?

  • NodeBB - Created pages not found?

    General
    20
    3 Votes
    20 Posts
    1k Views

    @jac Exactly. Hard point to argue.