Plugins Upgraded Beyond Supported Version (Upgraded from 0.5.3 to 0.5.4)

General Discussion
  • Pictures pretty much say it all:

    Says this when I click upgrade on either one:

    Nothing seems to be broken, other than the little red flags here.

  • I go in and update plugins after doing an upgrade. I did so after upgrading to 0.5.3, and maybe 0.5.3 didn't have this protection so it permitted the ACP to install the updated version?

  • This has suddenly gotten much, much worse. It's now telling me there are new versions of most of my plugins. I updated one (nodebb-plugin-dbsearch), and it crashed NodeBB so that I had to do a plugin reset.

    I assume this is due to the 0.6.0 breaking changes, but neither of these behaviors seems appropriate to me. First it was telling me my installed version was too high, now it's telling me to install breaking versions.

  • You're still on v0.5.4, yes? NodeBB shouldn't allow you to upgrade the plugins if they're not supported (e.g. upgraded for 0.6.0 compatibility)

  • Shouldn't, but it did (and obviously broke NodeBB by doing it). And yes, still running 0.5.4 and no updates were done between when it was telling me these two very different things. I figured it couldn't be telling me about breaking updates since the code hadn't changed and it was warning me about plugins which were upgraded too high just a few days previously, so I tried one of the upgrades and had to manually reinstall the correct version with npm to get it back to a functional state.

  • @julian This what happened to me. It let me upgrade plugins to ones that did not work.

  • Upgraded to 0.5.5, seems to have the same problem. I haven't verified by actually trying to install the plugins, but unless the 0.6.0 versions work with 0.5.5, it's still broken.


  • @Shaun You're saying the "latest" version is beyond your current version? Yes, this is intended for the moment.

    The nbbpm serves the same plugins list to all NodeBBs, whatever the version, but v0.5.5 should not let you upgrade past 0.0.15 of dbsearch, for example.

    Looks like it should automatically upgrade you to v0.0.16.

  • It's possible that the upgrade it performed when I tried it on 0.5.4 was to 0.0.16. I had to revert to 0.0.15 to get it functioning again. I just assumed 0.0.16 and 0.1.0 both contained the 0.6.x breaking change.

    I will try the upgrade again when I have more time to deal with whatever ehe fallout may be and let you know what I find.

  • I haven't tested but I'm pretty sure, given the experiences of others here, that the actual cause of my NodeBB breakage was dbsearch 0.0.16, so while it's awkward to be told there are all of these upgrades available, I don't think the problem was nbbpm, just a bad plugin.

Suggested Topics

  • 0 Votes
    4 Posts

    @pitaj I can confirm that this fixed my issue! Thank you!

  • 0 Votes
    3 Posts

    @julian thanks for your reply.

    The reason why I inject Apollo as a middleware is because of the server integrate document on Apollo website shows that we can use the apollo-server-express package to integrate GraphQL with existing Express server by adding following code:

    server.applyMiddleware({ app }); // app is from an existing express app

    Does router will be the express app to be passed to plugins? Because I solved this problem by passing router into .applyMiddleware() method as following changes:

    const router = params.router; apolloServer.applyMiddleware({ app: router, path: '/api/mygraphql', });

    Now, the GraphQL works fine on my NodeBB server ! Hope this can help someone who run into the same problem like me. Although it looks like GraphQL is not popular in NodeBB community 🤔.

  • 0 Votes
    1 Posts

    Maybe it's an idea to place version info in the footer wich link to the blogpost. Something like this.


    So it would be something like this.

    Copyright (c) 2018 NodeBB | Contributors
    version (v1.8.0)

  • 0 Votes
    1 Posts
    ./nodebb reset plugin

    process.nextTick(function() { throw err; });

    TypeError: invalid data
    at WriteStream.Socket.write (net.js:617:11)
    at /opt/nodebb/src/reset.js:57:19
    at /opt/nodebb/src/database/mongo.js:108:6
    at /opt/nodebb/node_modules/mongodb/lib/db.js:1553:5
    at handleCallback (/opt/nodebb/node_modules/mongodb/lib/utils.js:95:56)
    at _callback (/opt/nodebb/node_modules/mongodb/lib/db.js:1469:5)
    at /opt/nodebb/node_modules/mongodb/lib/db.js:1512:7
    at /opt/nodebb/node_modules/mongodb-core/lib/connection/pool.js:724:7
    at /opt/nodebb/node_modules/mongodb-core/lib/connection/pool.js:702:11
    at finish (/opt/nodebb/node_modules/mongodb-core/lib/auth/scram.js:160:16)

  • 0 Votes
    6 Posts

    Thanks for providing much needed assistance @frissdiegurke 😄

    Welcome to the land of plugin creation @Doppy !!