Plugins cannot be loaded.

Technical Support

Suggested Topics


  • 0 Votes
    3 Posts
    701 Views

    I have found a work around. There are a few more concerns I have as of now, but they are not major at all. Everything that needs to be working is working 🙂 Thank you for the reply though @PitaJ.

  • 0 Votes
    7 Posts
    2k Views

    @julian I found this after re-reading the NodeBB NGINX configuration docs

    nginx must be on version 1.4.x to properly support websockets. Debian/Ubuntu uses 1.2, although it will work there will be a reduction in functionality.

    Previously, in the same doc:

    NGINX version v1.3.13 or greater

    I'm not sure if that is just a sign of an outdated doc, or if there is actually some type of incompatibility (which apparently doesn't surface everywhere). All I know is that by reverting to 1.4.x, all functionality was restored.

  • 0 Votes
    2 Posts
    1k Views

    Looks like your minfile might not be compiled properly. Ensure you have no errors on startup (check ./nodebb log or look at logs/output.log)

  • 0 Votes
    2 Posts
    2k Views

    Post your plugin.json maybe it has a syntax error. Also did you put your theme in node_modules and activate it from the ACP?

  • Can't upgrade plugins

    Technical Support
    0 Votes
    12 Posts
    3k Views

    Ensuring compatibility is quite a daunting task, especially since core itself does change often (less so than before, but occasionally still does).

    In the case of bundled modules, that is, those defined in package.json, if they are out-of-date or too far ahead, they will cause NodeBB to not function. Its behaviour is quite restrictive, although it is intentional!

    We're considerably less restrictive when it comes to third-party plugins, and all we read is the nbbpm.compatibility portion of package.json. Even then, we can't ensure that a dev will keep this section up to date, or even that there will be a section at all! So it is merely a suggestion, though I am open to changes.

    I am considering changing nbbpm itself so that if a nbbpm.compatibility section is not found, it will not be added to the plugin listing. Right now a great majority of plugins don't specify compatibility information at all...