Ok. I think I know what's going on.

We're using a plugin called support forum that looks like it hasn't been updated in quite a while. My guess is that it keeps a hard reference to the tid, even if it's moved to another category.

It's only 168 lines of source, but I don't know Node.js or NodeBB architecture enough to make heads or tails of it. Maybe I should put a bounty on it? Not sure how well those kinds of offers are received, though.

While using less in the custom CSS, is it possible to gain access to the colors used in the theme/skin (specifically the skin).

I'm trying to plop in a background image floating underneath the content but allowing users to change skins causes problems because the main content area is transparent. So either I can set it to something light, which messes up dark skins, or set it to something dark, which messes up light skins.

Ideally, I'd like to transplant the body background color to the #content div without modifying the theme or skins.

Thoughts?

Thank you, @baris

GitHub issue: https://github.com/julianlam/nodebb-plugin-support-forum/issues/7

ELadner created this issue in julianlam/nodebb-plugin-support-forum

closed Moving topic to another category has side-effects. #7

Re: Change all postings for a one user to another user.

I'd also like to know if it's possible to move one users posts to be owned by another (specifically for merging two accounts created by the same user into one user account).

@dunlix (and others)

Thanks, the disable plugins suggestion worked. Apparently it was the "sanitize html" plugging that was causing the problem.

Not even sure why we had that still installed.

Thanks all for the troubleshooting help!

I (admin) can go to Manage -> Categories.. If I hit the "+", enter a name, click "Save" - nothing happens. No new Category is created. I've tried creating a top level category and a category as a child of something else and same behavior.

I was running 17.x and was having the issue. I upgraded to 18.4 (I think) - whatever the latest as of the writing of this post. Behavior remained the same.

Any guidance on troubleshooting?

Thanks

@dunlix (and others)

Thanks, the disable plugins suggestion worked. Apparently it was the "sanitize html" plugging that was causing the problem.

Not even sure why we had that still installed.

Thanks all for the troubleshooting help!

@dunlix - This server has been running fine for almost two years through multiple upgrades. The problem didn't occur until applying the latest version (I can confirm no reverse proxy changes).

I eliminated the network as a culprit. Tried to edit from three different PC's on three wildly different networks (i.e. not like my wifi and the neighbor's wifi, but very different networks).

@phenomlab - no browser extensions. I even tested this in a vanilla browser with no plugins.

I did see an error on the backend finally:

Oct 13 08:05:37 www nodebb[10920]: 2021-10-13T08:05:37.630Z [4567/10931] - #033[31merror#033[39m: modules.chats.newRoom
Oct 13 08:05:37 www nodebb[10920]: Error: [[error:no-privileges]]
Oct 13 08:05:37 www nodebb[10920]:     at SocketModules.chats.newRoom (/opt/nodebb/src/socket.io/modules.js:56:9)
Oct 13 08:05:37 www nodebb[10920]:     at runMicrotasks (<anonymous>)
Oct 13 08:05:37 www nodebb[10920]:     at processTicksAndRejections (internal/process/task_queues.js:97:5)
Oct 13 08:05:37 www nodebb[10920]:     at async onMessage (/opt/nodebb/src/socket.io/index.js:164:19)
Oct 13 08:06:14 www nodebb[10920]: 2021-10-13T08:06:14.280Z [4567/10931] - #033[31merror#033[39m: modules.chats.newRoom
Oct 13 08:06:14 www nodebb[10920]: Error: [[error:no-privileges]]
Oct 13 08:06:14 www nodebb[10920]:     at SocketModules.chats.newRoom (/opt/nodebb/src/socket.io/modules.js:56:9)
Oct 13 08:06:14 www nodebb[10920]:     at processTicksAndRejections (internal/process/task_queues.js:97:5)
Oct 13 08:06:14 www nodebb[10920]:     at async onMessage (/opt/nodebb/src/socket.io/index.js:164:19)

@baris - Yes, I see a post to /api/v3/categories..

{name: "Test1234", description: "", icon: "fa-comments", uid: 1747, parentCid: "0", cloneFromCid: "0"}

After a while, it reports a net::ERR_HTTP2_PROTOCOL_ERROR

Also checked the Mongo logs for errors to rule out any backend storage problems. Nothing of note in the logs.

@pitaj - Nothing in either. Server logs going to syslog (running as a daemon). Running "nodebb logs" doesn't seem to show anything either.

Going to stop it and run it manually from the command line. Nope.. nothing there either. Command just goes off into the sunset and does nothing. Clarification: There is logging showing up, but nothing that looks like an error around the second or so after I hit the "save" button on the new Category.

Browser console shows nothing of interest in either case, also.

I (admin) can go to Manage -> Categories.. If I hit the "+", enter a name, click "Save" - nothing happens. No new Category is created. I've tried creating a top level category and a category as a child of something else and same behavior.

I was running 17.x and was having the issue. I upgraded to 18.4 (I think) - whatever the latest as of the writing of this post. Behavior remained the same.

Any guidance on troubleshooting?

Thanks

I've read this and this and I've validated my config.json url property is correct (that URL, if pasted into a browser properly reverse proxies through Apache to nodebb)

Is there some other setting that could be affecting that?

I've read all the docs and searched the forums several times over, but it's still not clear to me if you can upgrade across branches in one step.

For example, if I'm on 1.10.2, can I upgrade directly to 1.12.2?

In the past, I've always applied each interim release to get from point a to point b (i.e. in this case 1.10.2 -> 1.11.0 -> 1.11.1 -> 1.12.0 -> 1.12.1 -> 1.12.2).

If it's generally agreed that doing it one fell swoop is "no problem" (TM), it would save me some typing and time.