Reply to myself for others with the same issues: If you go to the github above, you will find these files for each skin: https://github.com/thomaspark/bootswatch/blob/v5/dist/darkly/_variables.scss Those are the variables you can use to create a skin or to modify under the setting (which is what I am using as the custom skin did not work for me). For the ones that you do not want to modify, just delete them and the forum will use the default. I was able to replace almost everything I needed and now the forum has a look and feel different which is what we needed.

@julian That sounds like a nice improvement, so the user (and new admins like me) are not lost. Thanks!

@julian Thanks. I will try and see how that works.

Found the issue. No matter what the settings are, it is also required to change the default privileges on the /admin/manage/privileges global setting for all type of users. I was expecting that changing the setting will update that list, or at least a notification on the setting to clarify how it works.

So I did a fresh install. Now I had no errors during install and everything was smooth. So I am pretty sure everything is ok. Server is loading, console is ok, no errors on firefox and everything works. The only thing is this error on the nodebb log: NodeBB v3.8.4 Copyright (C) 2013-2024 NodeBB Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For the full license, please visit: http://www.gnu.org/copyleft/gpl.html Clustering enabled: Spinning up 2 process(es). 2024-08-03T19:48:55.570Z [4567/61787] - info: Initializing NodeBB v3.8.4 https://MYDOMAINREDACTED 2024-08-03T19:48:56.904Z [4568/61788] - info: [socket.io] Restricting access to origin: https://MYDOMAINREDACTED:* 2024-08-03T19:48:57.071Z [4567/61787] - info: [socket.io] Restricting access to origin: https://MYDOMAINREDACTED:* 2024-08-03T19:48:57.087Z [4568/61788] - info: [api] Adding 0 route(s) to `api/v3/plugins` 2024-08-03T19:48:57.106Z [4568/61788] - info: [router] Routes added 2024-08-03T19:48:57.110Z [4568/61788] - info: 🎉 NodeBB Ready 2024-08-03T19:48:57.112Z [4568/61788] - info: 🤝 Enabling 'trust proxy' 2024-08-03T19:48:57.114Z [4568/61788] - info: 📡 NodeBB is now listening on: 0.0.0.0:4568 2024-08-03T19:48:57.115Z [4568/61788] - info: 🔗 Canonical URL: https://MYDOMAINREDACTED 2024-08-03T19:48:57.275Z [4567/61787] - info: [api] Adding 0 route(s) to `api/v3/plugins` 2024-08-03T19:48:57.305Z [4567/61787] - info: [router] Routes added 2024-08-03T19:48:57.311Z [4567/61787] - info: 🎉 NodeBB Ready 2024-08-03T19:48:57.312Z [4567/61787] - info: 🤝 Enabling 'trust proxy' 2024-08-03T19:48:57.314Z [4567/61787] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 2024-08-03T19:48:57.314Z [4567/61787] - info: 🔗 Canonical URL: https://MYDOMAINREDACTED node:events:497 throw er; // Unhandled 'error' event ^ Error: spawn REDACTEDMYFOLDERINSTALL/node_modules/sass-embedded-linux-x64/dart-sass/src/dart EACCES at ChildProcess._handle.onexit (node:internal/child_process:286:19) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Emitted 'error' event on ChildProcess instance at: at ChildProcess._handle.onexit (node:internal/child_process:292:12) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { errno: -13, code: 'EACCES', syscall: 'spawn REDACTEDMYFOLDERINSTALL/node_modules/sass-embedded-linux-x64/dart-sass/src/dart', path: 'REDACTEDMYFOLDERINSTALL/node_modules/sass-embedded-linux-x64/dart-sass/src/dart', spawnargs: [ 'REDACTEDMYFOLDERINSTALL/node_modules/sass-embedded-linux-x64/dart-sass/src/sass.snapshot', '--embedded' ] } Node.js v20.16.0 I search the forums, read everyhthing I could find for the past 5 days and nothing. Anyone can tell me if this is a bug or if everyone has this and people just ignore the logs errors? Shall I worry or shall I ignore it? Thanks!

Thank you for both suggestions!

Mongo likes to expand its memory footprint because it saves everything in RAM when queried. So sometimes on particularly active forums with really low memory, your Mongo or Node.js process might get OOM-killed. Experiment with system resources and see. CPUs are quite good at context switching and even one CPU can ably run Mongo, redis, and NodeBB and still be fairly responsive if you don't have too many users querying at once.

@julian Fantastic. Thank you for your fast reply.

@eeeee My plan is to use a third party payment processor (probably Stripe) and use the Stripe webhooks and the Nodebb API to move the user from the paid group to the "free" group and the other way around when the payment fails. The forum we are building expect a lot of traffic so we need to automate this. We are still on "thinking and planning phase" so no real code to show you yet.

@julian I look forward to the day when this part of NodeBB is released.

Yes, in Admin can set which Widget code runs on which category (or topic) and where on page it sits (header / footer / side etc)

@darkpollo Thanks for the feedback. Yes, some sort of user/admin manual would be a good idea. Unfortunately we do not have the technical writers available to do this sort of work Getting technical documentation is already a feat In the meantime, we did have @jay-moonah put together the "Answers" category, which contains quite a bit of admin-related materials.