@julian I confirm the issue is resolved, many thanks for the quick support ️

I notice a different file hierarchy between them:

en-GB/
├── admin
│   ├── dashboard.json
│   └── settings
│       ├── languages.json

en-US/
├── admin
│   ├── general
│   │   ├── dashboard.json
│   │   ├── languages.json

Here is the comparison of both admin folders

~/nodebb/build/public/language$ rsync -r --ignore-existing -i -n en-GB/admin/ en-US/admin
>f+++++++++ dashboard.json
>f+++++++++ settings/homepage.json
>f+++++++++ settings/languages.json
>f+++++++++ settings/navigation.json
>f+++++++++ settings/social.json
>f+++++++++ settings/sounds.json
~/nodebb/build/public/language$ rsync -r --ignore-existing -i -n en-US/admin/ en-GB/admin
cd+++++++++ general/
>f+++++++++ general/dashboard.json
>f+++++++++ general/homepage.json
>f+++++++++ general/languages.json
>f+++++++++ general/navigation.json
>f+++++++++ general/social.json
>f+++++++++ general/sounds.json

that explains why...

I just did and same issue:

Also I noticed that if in /user/<my_user>/settings if I change the Language > Admin Page Language to en-GB instead of en-US, the ACP displays correctly translated in english.

Hi,

After upgrading from 1.13.1 to 1.13.3 by doing git pull (on the master branch),
now when I browse the ACP, nothing is translated, I see the translation key instead of strings and in the log there are those lines

Missing translation "admin/dashboard:running-version"
Missing translation "admin/dashboard:up-to-date"
Missing translation "admin/dashboard:keep-updated"
Missing translation "admin/dashboard:notices"
Missing translation "admin/dashboard:restart-not-required"
Missing translation "admin/dashboard:search-plugin-installed"
Missing translation "admin/settings/languages:language-settings"
Missing translation "admin/settings/languages:description"
Missing translation "admin/settings/languages:default-language"
Missing translation "admin/settings/languages:auto-detect"

My browser is configured in en-US, and the rest of the forum is displaying fine (in english US).

I have no clue how to fix this problem, may someone help?

Hi,

I would like to delete all users with 0 post, 0 chat and 0 group, in order to purge leeches and spammers.

Is that achievable using the ACP or Redis?
I asked mods to do it manually user by user, but it's a tedious task
Alternatively, is it possible to delete users having a website on their profile?

That would be handy!

Cheers

Alright, the redis database seemed find at first look (KEYS *), but checking with DBSIZE, the number of keys was only 1300, whereas it was 10 times bigger before, so I rolled back a previous dump, and it's working fine now. Don't know what happened, anyway, it's back to normal
Sorry for the trouble!

And keep up the outstanding work

@Tiktak
After adding "benchpressjs": "^1.2.5" to the package.json, and running npm install, I still have this error:

[benchpressjs] Unable to build or find a suitable native module, falling back to JS version

I ran ./nodebb build again, still no luck =/

How could I fix that?

Edit:

~/nodebb$ cat config.json
{
    "url": "https://*******.com",
    "secret": "********-****-****-****-************",
    "database": "redis",
    "port": 4567,
    "redis": {
        "host": "127.0.0.1",
        "port": "6379",
        "password": "",
        "database": "0"
    }
}

My config.json seems correct

Thank you for coming back to me,

Alas, I tried that

~/nodebb$ ./nodebb build
[benchpressjs] Unable to build or find a suitable native module, falling back to JS version
  started
2019-04-16T11:34:21.841Z [4567/24540] - info: [build] Building in parallel mode
2019-04-16T11:34:21.842Z [4567/24540] - info: [build]         plugin static dirs  build started
2019-04-16T11:34:21.845Z [4567/24540] - info: [build]          requirejs modules  build started
2019-04-16T11:34:21.846Z [4567/24540] - info: [build]           client js bundle  build started
2019-04-16T11:34:21.847Z [4567/24540] - info: [build]            admin js bundle  build started
2019-04-16T11:34:21.848Z [4567/24540] - info: [build]         client side styles  build started
2019-04-16T11:34:21.848Z [4567/24540] - info: [build] admin control panel styles  build started
2019-04-16T11:34:21.848Z [4567/24540] - info: [build]                  templates  build started
2019-04-16T11:34:21.849Z [4567/24540] - info: [build]                  languages  build started
2019-04-16T11:34:21.849Z [4567/24540] - info: [build]                     sounds  build started
2019-04-16T11:34:21.861Z [4567/24540] - info: [build]         plugin static dirs  build completed in 0.019sec
2019-04-16T11:34:22.229Z [4567/24540] - info: [build]                     sounds  build completed in 0.38sec
2019-04-16T11:34:32.839Z [4567/24540] - info: [build]         client side styles  build completed in 10.991sec
2019-04-16T11:34:41.183Z [4567/24540] - info: [build]           client js bundle  build completed in 19.337sec
2019-04-16T11:34:41.183Z [4567/24540] - info: [build]            admin js bundle  build completed in 19.336sec
2019-04-16T11:34:41.200Z [4567/24540] - info: [build]                  languages  build completed in 19.351sec
2019-04-16T11:34:56.715Z [4567/24540] - info: [build] admin control panel styles  build completed in 34.867sec
2019-04-16T11:34:57.839Z [4567/24540] - info: [build]                  templates  build completed in 35.991sec
2019-04-16T11:34:58.452Z [4567/24540] - info: [build]          requirejs modules  build completed in 36.607sec
2019-04-16T11:34:58.453Z [4567/24540] - info: [build] Asset compilation successful. Completed in 36.61sec.

$ ./nodebb slog

Starting NodeBB with logging output
Hit Ctrl-C to exit
The NodeBB process will continue to run in the background
Use "./nodebb stop" to stop the NodeBB server

Clustering enabled: Spinning up 1 process(es).

2019-04-16T11:35:04.054Z [4567/24580] - info: Initializing NodeBB v1.12.1 https://*******.com
[benchpressjs] Unable to build or find a suitable native module, falling back to JS version
2019-04-16T11:35:06.105Z [4567/24580] - info: [socket.io] Restricting access to origin: https://*******.com:*
2019-04-16T11:35:06.164Z [4567/24580] - info: Routes added
2019-04-16T11:35:06.181Z [4567/24580] - info: NodeBB Ready
2019-04-16T11:35:06.184Z [4567/24580] - info: Enabling 'trust proxy'
2019-04-16T11:35:06.188Z [4567/24580] - info: NodeBB is now listening on: 0.0.0.0:4567

Not luck, it's still just a grey website for now =/

And if I click login, I can't even log in :s

Hi,

I found my forum like this today:

Logs are fine, redis database is fine, I don't understand what's happening

I pulled the latest code and upgraded, it didn't change anything, nothing works...

Would anyone have an idea?

Hi, after invoking git pull and ./nodebb upgrade, I'm encountering an error while upgrading:

admin@xxx:~/NodeBB$ ./nodebb upgrade

Updating NodeBB...

1. Updating package.json file with defaults...  OK

2. Bringing base dependencies up to date...  started
audited 4626 packages in 10.851s

3. Checking installed plugins for updates...  OK
4. Updating NodeBB data store schema...
Parsing upgrade scripts...
OK | 2 script(s) found, 65 skipped
  → [2018/11/10] Navigation item visibility groups...
2018-11-12T15:51:00.342Z [2104] - error: uncaughtException: Cannot read property 'adminOnly' of undefined
TypeError: Cannot read property 'adminOnly' of undefined
    at /home/admin/NodeBB/src/upgrades/1.11.0/navigation_visibility_groups.js:19:30

How can I solve this?

Thanks, it worked flawlessly

@pitaj Latest, 1.7.4
I'm using this script to update

cd NodeBB-1.X.X
./nodebb stop
cd ..
redis-cli save
sudo cp /var/lib/redis/dump.rdb ~/dump-1.X.X.rdb
wget https://github.com/NodeBB/NodeBB/archive/v1.X.Y.tar.gz
tar czf backup-1.X.X.tar.gz NodeBB-1.X.X
mv NodeBB-1.X.X NodeBB-1.X.Y
tar xf v1.X.Y.tar.gz
cd NodeBB-1.X.Y
npm update
./nodebb upgrade or ./nodebb build
./nodebb start

where X.X is the current version and X.Y is the newer version

but I would prefer to have just to git pull of course ^^

@pitaj I haven't installed NodeBB with git sadly
I'd really like to know how can I start using git on a non git install, if that's possible!

Damn, I lost users because of this, first time I'm a little disappointed by NodeBB

Here is a quick fix for webmasters experiencing this persona skins issue

cd NodeBB-*
sed -i 's#bootswatch/latest#bootswatch/3.3.7#g' public/src/client/account/settings.js src/middleware/header.js
./nodebb build
./nodebb restart

Hope this helps

Edit: Sorry I might have been a little rude here, NodeBB rules of course, keep up the great work

@Telokis
What's up with the plugin?

@ChaosYamYT
True, but that's a not very convenient workaround, I was talking about the content of posts actually

@rod
Very good idea!
Done
https://i.imgur.com/PA6Zbbl.png

Hey @Telokis
I did not investigate further more, so you can challenge yourself and try to make it

I was annoyed by users registering with disposable/throwaway/temporary email addresses (like mailinator),
so I decided to develop a plugin to prevent that.

The ACP is just a textarea where you can paste your email domains that you want to blacklist (one per line).
Example of a maintained blacklist.
Edit: It can now also use isTempMail API to check the domain.

If an user register (or update his email address) with an email address that is blacklisted, it will block the registration with an error message.

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

GitHub (github.com)

npm install nodebb-plugin-email-blacklist

nodebb-plugin-email-blacklist

nodebb email blacklist. Latest version: 3.0.0, last published: 8 months ago. Start using nodebb-plugin-email-blacklist in your project by running `npm i nodebb-plugin-email-blacklist`. There are no other projects in the npm registry using nodebb-plugin-email-blacklist.

npm (www.npmjs.com)