@crazycells It does seem like package updates don't always update nbbpm... I will investigate.
How to upgrade 1.17.o?
I am hosting on Nodebb only. When I clicked on upgrade to 1.17.0, it is directing me to the documentation. My forum is being hosted on Nodebb only. I don't have access to the shell. I am not finding any setting on the front end in the admin dashboard.
I'd you'd like your hosted forum upgraded to the latest version, contact [email protected] and they'll do it for you.
If you are one of our hosted customers reach out to us at
[email protected]with the email you created the forum with.
@baris I've upgraded my forum to 1.17 according to the upgrade script output, but admin panel still reports 1.16.2.
What is the matter and what logs should I explore?
@twissell have you restarted NodeBB?
@pitaj Yes, I've done restart many times, no effect.
As well as full rebuild.
@twissell what's the output of
version: 1.16.2 Node ver: v16.0.0 git hash: 023e4cfcee208a0bae121a6e343a8c53009fd090 database: mongo version: 4.4.5 engine: wiredTiger
That's weird enough...so how can I execute update procedure step by step and/or debug it?
I also ran my first upgrade with 1.17 and had the same problem. The solution was: I have to run the upgrade with the user nodebb is running under. For me this is the user "nodebb" so "su nodebb" and then start the upgrade script. If you run it as root, you may have to reassign the files to the user, e.g. "chown -R nodebb:nodebb *" in the appropriate folder. But beware, I am a nodebb beginner myself and found this out only by try-and-error. For me it worked like this.
@twissell We don't support Node 16 yet, you might need to downgrade your npm version.
What commands did you execute to upgrade? It doesn't look like you pulled the latest changes from git.
Using sudo and from domain's as well, result is the same.
Script reports success on upgrade, but version doesn't change.
You need to pull the latest changes from git like
git fetch git checkout v1.17.x ./nodebb upgrade
@pitaj You are right,
git checkout versionand nodejs downgrade did the trick.
Thanks a lot!