[Solved] Cannot change settings

Giorgio Chiodi

@Marco Ciao, are you using redis as a database?

Marco

@Giorgio-Chiodi nope, I had a problem with Redis, so I use MongoDB. I also use a proxy (NGINX) which I configured according to the wiki so that I can use Port 80 for all incoming traffic to the server (PHP, Node,...)

julian

@Marco Does the ACP work properly when you access your instance with a port?

Marco

@julian nighttime is the best time of the day^^ well, I changed the configuration so that I can access nodebb directly (without NGINX) and got the same result: I cannot change the settings, upload anything, use custom CSS rules, edit categories,...

Marco

@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

Giorgio Chiodi

@Marco I did scare me. So is this fixed when pulling the fresh code from Nodebb? @julian

Marco

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

Giorgio Chiodi

@Marco did you just do this command?

  npm i nodebb-theme-vanilla@latest nodebb-theme-lavender@latest

I think I'm missing something. Did you also do another

./nodebb upgrade

?

Giorgio Chiodi

@Marco @julian Ah yes it's working now. So basically the theme files weren't updated in the github package?

julian

The themes are downloaded separately, when you do npm install the first time. Problem is it seems sometimes npm doesn't install the latest theme files.

Giorgio Chiodi

@julian

Ok, I just made a new AWS install, and the bug is not there anymore.

npm i nodebb-theme-vanilla@latest nodebb-theme-lavender@latest

also fixes the problem