NodeBB Plugin and Theme authors
@retipster it means both of those things, depending on how you set it up.
For only Group A can post, other users can view. Group A would have post, reply, view privileges on the category. Group "Registered Users" would have only view privilege.
For only Group A can post and view. Group A would have post, reply, view privilege. Group "Registered Users" would have no privileges for that category.
There's a "Require E-Mail verification" option in the ACP that will prevent unverified users from posting, but will still allow them to login.
Privileges are tied to groups. You can create a category that a certain group would have exclusive access to. They're isn't a way to do this automatically, yet.
Please try dropping all dbs in your new mongo install. Then try the mongorestore process again. See if that works.
Can you describe what steps you took after the clean install to restore your database? It's my guess that restoring over the fresh db from the clean install may be the source of your issues.
How did you install NodeBB on the new server?
@silvanet those registry entries should be overwritten. Do you know what version of node you were using before? Just install that version if you know, otherwise install the latest LTS. Rarely are there any breaking changes that affect actual code.
I'd just go to https://nodejs.org, download the installer, and reinstall it.
You're requiring it wrong. You should be doing require(['file-explorer'], ...) if you're defining the module as file-explorer.js in plugin.json.
Also, the define must match so define('file-explorer', ...). Or you can change them all to azure/ like so:
define('azure/file-explorer', ...)
require('azure/file-explorer', ...)
"modules": {
"azure/file-explorer.js": "static/lib/file-explorer.js"
}
I think after changing mongod.cfg you shouldn't be able to connect without authenticating correctly. Please post your mongod.cfg and the output when you run net stop MongoDB and net start MongoDB