Translators

@bri They're fast in my mind

Try updating the plugin to 1.2.1, that might fix the crash.

The Q&A plugin is compatible with latest NodeBB, looks like you just forgot to run ./nodebb build.

@vstoykov additional caching is recommended to be handled by third party systems like nginx or varnish.

Scaling - NodeBB Documentation

For all those wondering... @nsuchy had a really large (i.e. 2mb+ of pure text) blacklist.

...

... don't make your blacklist that large

That's exactly it... they're system groups because they're relied upon internally and cannot be deleted or renamed.

The admin interface uses groups in the backend. Global mods are empty by default but any members in that group are automatically mods in every category.

That's all.

Regular groups can be renamed, its just the system groups that can't be renamed right now. The reason for that is the group name is the unique identifier right now. So when checking if a user is an administrators there is code like groups.isMember(uid, 'administrators', callback); To be able to freely change group names all the code needs to be refactored to use numeric ids instead of unique names.

@nsuchy We could use that as part of the test... if you disable all plugins except the bundled ones, does it upgrade to v1.6.1 without issues

@eda can you add this to the knowledge base at answers.nodebb.org please?

Sure thing, you can run npm run lint, or ./node_modules/.bin/eslint ., both trigger an eslint run.

Or you could be even more proactive and set up this git pre-commit hook:

#!/bin/bash

for file in $(git diff --cached --name-only | grep -E '\.(js|jsx)$')
do
  git show ":$file" | node_modules/.bin/eslint --stdin --stdin-filename "$file" # we only want to lint the staged changes, not any un-staged changes
  if [ $? -ne 0 ]; then
    echo "ESLint failed on staged file '$file'. Please check your code and try again. You can run ESLint manually via npm run eslint."
    exit 1 # exit with failure status
  fi
done

Then every time you git commit, it'll check for style issues ;)

The first two options check the entire codebase, so that might take awhile. The pre-commit hook only checks staged files so it is much faster, too.