NodeBB 3.2.0

<baris>

Hello everyone !

I forgot to make an official announcement for 3.2.0, some of you are already using it .

3.2.0 was released last week and we followed it with 3.2.1 yesterday with some bug fixes.

3.2.0 has a lot of bug fixes but the biggest change in this release is the redesigned admin pages. The ACP was built over the past 9 years and a lot of the pages weren't consistent.

The new ACP comes with a sidebar for navigation and also has a better table of contents on settings page. The old one pushed all the content down the page making it harder to navigate different settings pages.

Some of the settings were also merged into other pages

Home page moved to General>Home
Language moved to General>Site Settings
Social moved to General>Post Sharing
Guest moved to User>Guest settings

Dashboard

Settings

Groups

Group

Users

Please report any issues and bugs you find

FrankM

@baris Thanks for the work. I like the new admin interface.

omega

Ha ha... you know what I'm going to say next don't you... single column layout use case FTW!

omega

@baris

I managed to get the thing updated to 3.2.1 finally, but I'm getting weird styling on the admin panel, a bit retro, did a build, and it restored some f the missing elements not he left, but still the same look for the side panel, none of the new styling, not sure if it's a bug or my brutal sysadmin setup skillz, I just never know.

<baris>

@omega looks like your css isn't loading

omega

@baris Yea and also the rebuild + restart doesn't seem to work from the admin panel.

omega

@baris Got this error at the very end of the build.

2023-07-07T14:38:13.804Z [4567/1697] - info: [build] Bundling with Webpack.
[92%] sealing (asset processing TerserPlugin)
2023-07-07T14:40:20.377Z [4567/1697] - error: uncaughtException: Something went wrong. It took over five seconds to find the next execution time for the cron job.
							Please refer to the canonical issue (https://github.com/kelektiv/node-cron/issues/467) and provide the following string if you would like to help debug:
							Time Zone: "" - Cron String: 0 * * * * * - UTC offset: 0
							- current Date: 2023-07-07T14:40:10.798+00:00
Error: Something went wrong. It took over five seconds to find the next execution time for the cron job.
							Please refer to the canonical issue (https://github.com/kelektiv/node-cron/issues/467) and provide the following string if you would like to help debug:
							Time Zone: "" - Cron String: 0 * * * * * - UTC offset: 0
							- current Date: 2023-07-07T14:40:10.798+00:00
    at CT._getNextDateFrom (/home/dir/nodebb/node_modules/cron/lib/time.js:272:12)
    at CT.sendAt (/home/dir/nodebb/node_modules/cron/lib/time.js:185:17)
    at CT.getTimeout (/home/dir/nodebb/node_modules/cron/lib/time.js:202:29)
    at CJ.start (/home/dir/nodebb/node_modules/cron/lib/job.js:119:31)
    at Timeout.callbackWrapper [as _onTimeout] (/home/dir/nodebb/node_modules/cron/lib/job.js:172:11)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {"date":"Fri Jul 07 2023 14:40:14 GMT+0000 (Coordinated Universal Time)","error":{},"exception":true,"os":{"loadavg":[9.6,3.81,1.69],"uptime":1412.94},"process":{"argv":["/usr/bin/node","/home/dir/nodebb/nodebb","build"],"cwd":"/home/dir/nodebb","execPath":"/usr/bin/node","gid":1000,"memoryUsage":{"arrayBuffers":64173568,"external":67491191,"heapTotal":213450752,"heapUsed":177761520,"rss":297197568},"pid":1697,"uid":1000,"version":"v18.16.0"},"stack":"Error: Something went wrong. It took over five seconds to find the next execution time for the cron job.\n\t\t\t\t\t\t\tPlease refer to the canonical issue (https://github.com/kelektiv/node-cron/issues/467) and provide the following string if you would like to help debug:\n\t\t\t\t\t\t\tTime Zone: \"\" - Cron String: 0 * * * * * - UTC offset: 0\n\t\t\t\t\t\t\t- current Date: 2023-07-07T14:40:10.798+00:00\n    at CT._getNextDateFrom (/home/dir/nodebb/node_modules/cron/lib/time.js:272:12)\n    at CT.sendAt (/home/dir/nodebb/node_modules/cron/lib/time.js:185:17)\n    at CT.getTimeout (/home/dir/nodebb/node_modules/cron/lib/time.js:202:29)\n    at CJ.start (/home/dir/nodebb/node_modules/cron/lib/job.js:119:31)\n    at Timeout.callbackWrapper [as _onTimeout] (/home/dir/nodebb/node_modules/cron/lib/job.js:172:11)\n    at listOnTimeout (node:internal/timers:569:17)\n    at process.processTimers (node:internal/timers:512:7)","trace":[{"column":12,"file":"/home/dir/nodebb/node_modules/cron/lib/time.js","function":"CT._getNextDateFrom","line":272,"method":"_getNextDateFrom","native":false},{"column":17,"file":"/home/dir/nodebb/node_modules/cron/lib/time.js","function":"CT.sendAt","line":185,"method":"sendAt","native":false},{"column":29,"file":"/home/dir/nodebb/node_modules/cron/lib/time.js","function":"CT.getTimeout","line":202,"method":"getTimeout","native":false},{"column":31,"file":"/home/dir/nodebb/node_modules/cron/lib/job.js","function":"CJ.start","line":119,"method":"start","native":false},{"column":11,"file":"/home/dir/nodebb/node_modules/cron/lib/job.js","function":"Timeout.callbackWrapper [as _onTimeout]","line":172,"method":"callbackWrapper [as _onTimeout]","native":false},{"column":17,"file":"node:internal/timers","function":"listOnTimeout","line":569,"method":null,"native":false},{"column":7,"file":"node:internal/timers","function":"process.processTimers","line":512,"method":"processTimers","native":false}]}dir

omega

@baris All good, after I ran some system updates, then did another build and this time, no error!