I talk to computers all day. Sometimes they talk back
👋Hey chatgpt, I am a co-founder of NodeBB!
@tune-a-sandwich looks like custom css per user does exist, it was initially created by @[email protected] . I’ve updated it so it is available on 4.x as well. https://github.com/NodeBB-Community/nodebb-plugin-user-css. You can install it with npm install [@nodebb](https://community.nodebb.org/user/nodebb)/nodebb-plugin-user-css
You can lower it and old passwords will still work, new passwords will use the new rounds value.
Maybe try a higher value for first one, on this forum it is set to 300ms. You can read more about what those values are here https://github.com/STRML/node-toobusy?tab=readme-ov-file#tunable-parameters
With the default settings it shouldn’t what about the 2 values set at /admin/settings/advanced#traffic-management?
Did you modify bcrypt_rounds in config.json? Check cpu usage during login. You can tweak the traffic management values in acp to make it less sensitive as well.
I don’t know if there are any plugins that do these, but they are certainly possible as plugins.
Try disabling traffic management at /admin/settings/advanced#traffic-management and see if it’s caused by that.
Does the user running nodebb own the /opt/nodebb folder?
Have you tried using this end point? https://github.com/NodeBB/NodeBB/blob/master/public/src/admin/modules/change-email.js#L26-L29
That’s used to set a users email and confirm it as long as the calling user is admin.
Works for me right now, could be related to the CF outage this morning.
You can run ./nodebb upgrade after npm install and it will run any migration scripts if they weren’t run before.
./nodebb upgrade is a combination of updating package.json, running npm install and running upgrade scripts.
Yes it is possible, once you restore the database and point the 4.6.1 instance to it, run ./nodebb upgrade it will run the migration scripts required to update the database to 4.6.1
You can just create a static sitemap.xml and serve it with your load balancer. The nodebb generated one is dynamically generated to add new topics but the other parts of it are mostly static. If you change/purge category names those are updated as well.
LWSH6688 you can try applying this commit for a fix https://github.com/NodeBB/NodeBB/commit/9410f466d80b30f52e5f926e5d17a513beec1084
Yeah looks like it started with the change from connect-multiparty to multer in https://github.com/NodeBB/NodeBB/commit/385f4f12be4dbd41832bebbe043288ee524a1bee, will take a look. Thanks for reporting.
And it was working that way in 4.2.0? I will see if I can find the commit that changed that.
 on this it looks like this and on the backend it looks like below. Not sure if it’s supposed to be different.
Can you provide a sample text file? Maybe upload one to this post.
You can set the parent of a category in the category settings.
Or on the list of categories you can drag and drop it under another category.
While creating the category you can set a parent as well.