Step 1 database The target machine has MongoDB 7 installed, not 8. To ensure no data errors occur, I will upgrade to version 8 later First, dump database and restore mongodump -u nodebb -p password -d nodebb -o database mongorestore -d nodebb nodebb/ -v Step 2 upgrade nodebb Force git to use HTTPS. This problem cost me hours trying to find a solution. https://stackoverflow.com/a/72391698 git config --global url."https://github".insteadOf git://github v1.12.2 -> v1.13.x/v1.14.x/v1.15.x failed nvm version 12, error on ./nodebb upgrade. The errors I'm seeing looks like compatibility issue between benchpress and Node.js version 12. v1.12.2 -> v1.16.x success nvm switch to 14, some error on ./nodebb upgrade. The upgrade process had some errors, but the outcome wasn't impacted. Once completed, ./nodebb dev works. v1.16.x -> v1.17.x -> v1.18.x -> v1.19.x success v1.19.x -> v2.x success v2.x -> v3.x failed v2.x -> v3.0.1 success some error on ./nodebb upgrade. The upgrade process had some errors, but the outcome wasn't impacted. Once completed, ./nodebb dev works. v3.0.1 -> v3.x doing nvm switch to 18.

@phenomlab I'm completely new to being a forum admin, so I'm not familiar with the tools and techniques. Is this common? I'd expect to be able to censor or lock the profile and warn or ban the user without putting words in their mouth. I suppose it's a moot point since I have access to the database and could do it from there if I really wanted to; I'm just shocked that it's so easy.

Note that our reason for implementing this has to do with maintaining privacy since its often relatively easy to reconstruct a social id/email from the username. We do allow users to 'alias' their names after registration, but users don't always realize the need to protect their identity.

@anchorite thanks for reporting, it is fixed in 4.2.1

Thanks for your reply. Unfortunately I tore down the two test instances, but I'll check out dev mode.