General Discussion

0 readers

2 users here now

A place to talk about whatever you want

This is a forum category containing topical discussion. You can start new discussions by mentioning this category.

founded 6 months ago

How are you managing plugin compatibility across NodeBB updates? (community.nodebb.org)

submitted 3 months ago by codywebb@community.nodebb.org to c/general-discussion@community.nodebb.org

2 comments fedilink hide all child comments

Hey all,

I’ve been running a small NodeBB forum and really enjoy the flexibility of the platform. One thing I’ve noticed, though, is that with each new version update, some of my favorite plugins break or behave oddly until they’re patched.

How are other forum admins managing plugin compatibility when upgrading NodeBB? Do you freeze your NodeBB version until all plugins catch up, or do you just dive in and fix what breaks?

Thanks in advance!

top 2 comments

sorted by: hot top controversial new old

[–] codywebb@community.nodebb.org 1 points 3 months ago* (last edited 3 months ago)

@Cody Web said in How are you managing plugin compatibility across NodeBB updates?: > Hey all, > > I’ve been running a small NodeBB forum and really enjoy the flexibility of the platform. One thing I’ve noticed, though, is that with each new version update, some of my favorite plugins break or behave oddly until they’re patched. > > How are other forum admins managing plugin compatibility when upgrading NodeBB? Do you freeze your NodeBB version until all plugins catch up, or do you just dive in and fix what breaks? > > Thanks in advance!

...?

[–] baris@community.nodebb.org 1 points 3 months ago

Setup a staging environment and update it to the nodebb version you want to upgrade to. And then test the plugins if they are working. If everything looks good you can upgrade your real forum. From 3.x to 4.x there weren't any plugin breaking changes so plugins that were updated for 3.x will work on 4.x as well. They might not show up in the ACP because of the compatibility string in package.json. which needs to be updated and by the plugin author to mark the plugin as compatible.