I can see two plugins now:

Also, the plugins initially show up for a short time before they disappear and only the above two remain.

They appear fine in previous 1.19.x releases including 1.19.4. FWIW, this is on Cloudron (I was updating the package to have the latest NodeBB).

The plugin listing appears for a short time and then instantly disappears in 1.19.5.

If you go to /admin/extend/plugins#download, it appears like this:

There are no errors in the browser console.

@baris Is that link correct ? There is no DNS A record or CNAME for nodebb.org

$ host nodebb.org
nodebb.org mail is handled by 1 aspmx.l.google.com.
nodebb.org mail is handled by 5 alt1.aspmx.l.google.com.
nodebb.org mail is handled by 5 alt2.aspmx.l.google.com.
nodebb.org mail is handled by 10 aspmx2.googlemail.com.
nodebb.org mail is handled by 10 aspmx3.googlemail.com.

Indeed under Navigation in the ACP, I can see the routes are wrong:

Note that all I have done since today morning is just install the awards plugin (which didn't work). I also tried to create a group and assign some members to a group which was also failing. some users would get into the group, some won't i.e even though the groups UI will show them as members, the user page won't show their badge or ownership.

Sorry, I don't have anything concrete for you to fix yet. I am just writing things down as I find them.

I found the issue. In the database the routes are all "corrupt". Not sure what will cause the route to become this way.

rs0:PRIMARY> x.find( { _key: 'navigation:enabled' })
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac44"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-user\",\"route\":\"/users\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.users]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.users]]\",\"enabled\":\"true\",\"properties\":{},\"order\":\"5\",\"groups\":[]}", "score" : 5 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac40"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-tags\",\"route\":\"/tags\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.tags]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.tags]]\",\"enabled\":\"true\",\"properties\":{},\"order\":\"3\",\"groups\":[]}", "score" : 3 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac49"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-search\",\"route\":\"/search\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.search]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.search]]\",\"enabled\":\"\",\"properties\":{},\"order\":\"8\",\"groups\":[]}", "score" : 8 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac3b"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-list\",\"route\":\"/categories\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.categories]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.categories]]\",\"enabled\":\"true\",\"properties\":{},\"order\":\"0\",\"groups\":[]}", "score" : 0 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac3d"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-inbox\",\"route\":\"/unread\",\"class\":\"\",\"id\":\"unread-count\",\"text\":\"[[global:header.unread]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.unread]]\",\"groups\":[\"registered-users\"],\"enabled\":\"true\",\"properties\":{},\"order\":\"1\"}", "score" : 1 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac45"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-group\",\"route\":\"/groups\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.groups]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.groups]]\",\"enabled\":\"true\",\"properties\":{},\"order\":\"6\",\"groups\":[]}", "score" : 6 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac42"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-fire\",\"route\":\"/popular\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.popular]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.popular]]\",\"enabled\":\"true\",\"properties\":{},\"order\":\"4\",\"groups\":[]}", "score" : 4 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac47"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-cogs\",\"route\":\"/admin\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.admin]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.admin]]\",\"groups\":[\"administrators\"],\"enabled\":\"true\",\"properties\":{},\"order\":\"7\"}", "score" : 7 }
{ "_id" : ObjectId("5f80a6737b2770d2a0a4ac3e"), "_key" : "navigation:enabled", "value" : "{\"iconClass\":\"fa-clock-o\",\"route\":\"/recent\",\"class\":\"\",\"id\":\"\",\"text\":\"[[global:header.recent]]\",\"textClass\":\"visible-xs-inline\",\"title\":\"[[global:header.recent]]\",\"enabled\":\"true\",\"properties\":{},\"order\":\"2\",\"groups\":[]}", "score" : 2 }

I am seeing the same thing in our forum. It all started with installing the awards plugin (which never worked) and it all went downhill from there. Even removing the plugin does not seem to help. @Normando did you get to the bottom of this and how did you fix it?

I created https://github.com/NodeBB/NodeBB/issues/8547

@julian @PitaJ Thanks for the quick response. I will open a GitHub issue.

I maintain the NodeBB package on Cloudron. It was suggested earlier that I should try to use upgrade --package option to update the package.json to the newer NodeBB version and preserving the plugin module names at the same time. This works as expected.

However, I found that --package will not remove packages that are unused. For example, in 1.13.x NodeBB had a package called json-2-csv which was removed in 1.14.x. The --package will keep the old json-2-csv in package.json even though it's now gone.

I have a few questions:

• Is this behavior intentional or should we fix --package to remove extra deps? If not, how do I remove json-2-csv from package.json? Of course, I can npm uninstall the modules which are now gone in the newer NodeBB version manually but this means I have to manually diff package.json for every NodeBB upgrade (the situation I was trying to avoid in my first post). Having stale things in package.json is harmless but the issue is NodeBB does a dep check on startup (and json-2-csv is not installed).
• A related issue: I found the flag dep-check to skip the dep check on start up. However, the loader does not pass command line args to app (so, you cannot use --no-dep-check). This means you have to use env var but that doesn't work because nconf parses dep-check=false as a string instead of bool (issue) and the code in start.js compares a string against a boolean now. Effectively, I don't know how to pass no-dep-check via loader.js.

Thanks!

@PitaJ Thanks! upgrade --package is exactly what I was looking for.

Sorry for resurrecting an old thread.

@PitaJ If package.json stores the version information, then does it not get overwritten when i update the nodebb repo? Or do I have manually merge package.json every time I update nodebb?

@PitaJ Do you mean package.json of the plugins?

Would it make sense to store the plugin versions in the database? Currently, only the plugin name is saved:

> db.objects.find({ _key: 'plugins:active' })
{ "_id" : ObjectId("5c01945f24783cf614b4d40b"), "_key" : "plugins:active", "value" : "nodebb-widget-essentials", "score" : 3 }
{ "_id" : ObjectId("5c01945d24783cf614b4d095"), "_key" : "plugins:active", "value" : "nodebb-theme-persona", "score" : 0 }

For context, the Cloudron NodeBB package does not save the node_modules as part of the backups (as plugin code is source code after all which is immutable). What we do is to install the required npm modules using the output of "nodebb plugins". This has worked well since a long time but recently we hit a issue where restoring an old nodebb installation resulted in the installation of a new plugin version and thus breaking the installation.

Problem can be fixed if plugin version was stashed in the database. This way, we can then do npm install <plugin@version>.

Thanks! (wasn't sure if this belonged to github or here, so trying this first).

Thanks, that seems to work!

@pichalite I have tried that as well but that has no effect. What settings does this forum use? The above black image displays as 918px on my screen here. The default size as per the UI is 760px.

Wanted to check if this a bug or feature. https://community.nodebb.org/topic/9219/testing-big-image has a test image. Isn't the image way too big? I am using nodebb 1.1.0. I have tried to fix up the size in the Upload settings to 400px in my own forum but doesn't seem to affect the image size.