Outdated themes caused major problems (cannot edit settings, change categories,...) with a fresh(!) installation of NodeBB for me. I had to wait for days to finally get the solution. This is really bad and might scare away admins who think about using NodeBB and don't even know that their themes are outdated (because they just installed the latest version as described in the docs)
I would suggest to add a row "Components up2date" to the box which checks the version in the ACP. If something is not up2date, it should be displayed in a indented row below the "Components up2date" row. Colors might be green (ok), orange(unchecked) and red(outdated).

See example GUI:

@julian I followed the docs. I got an outdated version labeled 0.4.3. No one ever told me to update the themes. It really does not matter if everything worked fine for a long time. This should just show you that you need more testing. You obviously did not test installing version 0.4.3 as described in the docs directly.
I know it's not easy to find bugs, but please seriously consider this request as it will prevent a lot of headaches in the future and show admins what might not be working. I cannot make a good bug report if I am using outdated software. I did not even know that it was outdated. You won't be able to solve future bugs if people use outdated software without knowing.

BTW.: as I already wrote on github, renaming the branches won't help anyone if it contains outdated software or the docs are insufficient. I would be really glad to see my request beingf implemented and help thousands of people setting up a very nice forum.

@Giorgio-Chiodi In my case it is fixed. Still doing some testing, but it looks good

Outdated themes caused major problems (cannot edit settings, change categories,...) with a fresh(!) installation of NodeBB for me. I had to wait for days to finally get the solution. This is really bad and might scare away admins who think about using NodeBB and don't even know that their themes are outdated (because they just installed the latest version as described in the docs)
I would suggest to add a row "Components up2date" to the box which checks the version in the ACP. If something is not up2date, it should be displayed in a indented row below the "Components up2date" row. Colors might be green (ok), orange(unchecked) and red(outdated).

See example GUI:

@julian @baris @psychobunny @Giorgio-Chiodi Problem solved. I updated the themes npm i nodebb-theme-vanilla@latest nodebb-theme-lavender@latest (julian's proposal) and now I can change my settings again, disable categories, etc.
So I would suggest that you add up2date themes to the current installation of nodebb or - even better - have nodebb check if all used themes and plugins are up2date and warn the user about it (will make feature proposal for this)

As I said, I installed a clean new copy of nodebb (as described in the docs) and I could not use it at all. This problem might scare away admins, so it would help everyone if it got fixed

@julian yep. Did that several times after resetting the plugins. And no matter how often I stop and start nodebb, it won't magically work. That's a real problem
I can invite you to take a look at it via TeamViewer. But I cannot show you more than you already know and see.

@Guiri Yep. There are many ways. I prefer having a nice script which can do start/stop tasks when I call it in one place with all the other start/stop scripts. You prefer a solution which is more behind the scenes. But at the end of the day, both will work The OP will have to choose what he wants to do

@markkus Sorry, I did not get that from your first post. If you want to run a script forever, use forever. If you want it to start after system boot, all you have to do is change the script I posted a little bit to use forever instead of nodebb.

@a_5mith I don't think forever or supervisor start nodebb after system start. Please correct me if I am wrong.

There are different possibilities. Unfortunately, I don't know much about Ubuntu. But I guess, it should be the same as on Debian.
In /etc/init.d there are scripts which are run on system startup with start as parameter and stop on system shutdown. All you have to do is make such a little script which takes 1 parameter and either starts nodebb if the parameter is start or stop nodebb if the parameter is stop.

#! /bin/sh
# /etc/init.d/nodebb

case "$1" in
  start)
    echo "Starting NodeBB..."
    /srv/www/community/nodebb start
    ;;
  stop)
    echo "Stopping NodeBB..."
    /srv/www/community/nodebb start
    ;;
  *)
    echo "Usage: /etc/init.d/nodebb {start|stop}"
    exit 1
    ;;
esac

exit 0

@julian I already tried that. No changes. I disabled them on my installation for you to further investigate.

@Giorgio-Chiodi That's interesting. I stopped/started my nodebb countless times.