Skip to content
Sudonix

Error install plugin

Solved Customisation
8 3 5.6k 1
  • DownPW
    DownPW
    DownPW
    wrote on
    #1

    Hi

    I have this error on fresh install nodebb 2.2.4 whein i want to install plugin via ACP
    Example here with question and answer plugin:

    20c09392-844b-437b-ab0d-25a03f20ef48-image.png

    An idea?

    PW and WS Spirit alive

    0
  • DownPW
    DownPW
    DownPW
    wrote on
    #3

    In fact when I go to research plugin I have one result in the list, research doesn’t work

    9054b9d8-be86-4e5e-a424-45d6f4bc8dbe-image.png

    verry odd

    I have installed all plugins in command line

    PW and WS Spirit alive

    0
  • DownPW DownPW

    Hi

    I have this error on fresh install nodebb 2.2.4 whein i want to install plugin via ACP
    Example here with question and answer plugin:

    20c09392-844b-437b-ab0d-25a03f20ef48-image.png

    An idea?

    phenomlab
    phenomlab
    phenomlab
    wrote on
    #2

    @DownPW that error message means the plugin you are trying to install doesn’t meet the minimum requirements of the latest version of NodeBB. You’d need to contact the plugin author to resolve that

    Mark Cutting also advises organisations as a Fractional CIO, Fractional CISO and Executive Advisor, helping boards improve technology governance, cyber resilience and executive decision making. Learn more at Gratmore Ltd

    0
  • DownPW
    DownPW
    DownPW
    wrote on
    #3

    In fact when I go to research plugin I have one result in the list, research doesn’t work

    9054b9d8-be86-4e5e-a424-45d6f4bc8dbe-image.png

    verry odd

    I have installed all plugins in command line

    PW and WS Spirit alive

    0
  • DownPW DownPW

    In fact when I go to research plugin I have one result in the list, research doesn’t work

    9054b9d8-be86-4e5e-a424-45d6f4bc8dbe-image.png

    verry odd

    I have installed all plugins in command line

    phenomlab
    phenomlab
    phenomlab
    wrote on
    #4

    @DownPW yes, this was a known issue in the first 2.x release if I remember rightly.

    Mark Cutting also advises organisations as a Fractional CIO, Fractional CISO and Executive Advisor, helping boards improve technology governance, cyber resilience and executive decision making. Learn more at Gratmore Ltd

    0
  • phenomlab phenomlab has marked this topic as solved on
  • DownPW
    DownPW
    DownPW
    wrote on
    #5

    ok but it’s a 2.2.4 version with no upgrade

    PW and WS Spirit alive

    0
  • DownPW DownPW

    ok but it’s a 2.2.4 version with no upgrade

    phenomlab
    phenomlab
    phenomlab
    wrote on
    #6

    @DownPW yes, the same issue still applies though.

    Mark Cutting also advises organisations as a Fractional CIO, Fractional CISO and Executive Advisor, helping boards improve technology governance, cyber resilience and executive decision making. Learn more at Gratmore Ltd

    0
  • DownPW
    DownPW
    DownPW
    wrote on
    #7

    it’s not very serious 😞

    PW and WS Spirit alive

    0
  • DownPW
    DownPW
    DownPW
    wrote on
    #8

    @pobojmoks

    Not WP plugin but nodeBB but it a known bug

    PW and WS Spirit alive

    1
Log in to reply

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

    What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    5k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • crazycells

    Page control arrows for PWA

    Solved Customisation nodebb
    27
    25 Votes
    27 Posts
    15k Views
    phenomlab
    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems. /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android } Once you’re in that rabbit hole, it’s impossible to get out of it.
  • dave1904

    How to style tool tip of nodebb-plugin-user-level

    Solved Customisation user level css
    4
    1
    5 Votes
    4 Posts
    3k Views
    phenomlab
    @DownPW thanks. I forgot about that.
  • DownPW

    Plugin reaction Bug

    Solved Customisation plugin nodebb reaction
    15
    1
    0 Votes
    15 Posts
    6k Views
    phenomlab
    @DownPW That was going to be my next suggestion
  • Sampo2910

    Tenor GIF Plugin

    Solved Customisation plugin
    19
    1
    5 Votes
    19 Posts
    9k Views
    Sampo2910
    @phenomlab Also for me now Upgraded in ACP and all good . Thx.
  • Sampo2910

    Plugin Install Error

    Solved Customisation plugin error discord
    6
    1
    2 Votes
    6 Posts
    3k Views
    phenomlab
    @Sampo2910 no problems. Happy to help. Just remember that this particular method isn’t the best in the sense that it may not get update notifications. The general recommendation here would be to move back to the official npm repo as soon as the GitHub version has been merged. For the meantime, it’ll work fine though.
  • RiekMedia

    NodeBB Discord Plugins

    Unsolved Customisation nodebb discord plugin
    7
    0 Votes
    7 Posts
    4k Views
    phenomlab
    @RiekMedia hi. Just following up on this thread (I know it’s old) but was curious to understand if it’s still an issue or not ?
  • JAC

    [NodeBB] Creating new user to auto post content

    Solved Customisation
    3
    0 Votes
    3 Posts
    2k Views
    JAC
    @phenomlab many thanks Mark .