That is a warning. That should not be causing issues for when you visit your site. Check for other errors in the nodebb log and in your browser console.
SOLVED easy nodebb upgrade process
Yes, I'll admit the write up is a little verbose, but that's how I am when I write text
The gist of it is...
git checkout v1.x.xif not already there
git pull && ./nodebb upgrade
So if I'm upgrading from v1.0.0 to v1.0.1 does that mean I should replace the x.x for the command you provided with
git checkout v1.0.1?
phit last edited by
@charles no, it stays
git checkout v1.x.x
that's the branch name for the latest 1.x.x, so right now 1.0.1
I thought it was clear, but didnt work for me i upgraded, it appeared to work, but still when i go into the dashboard it says 1.0.0
@ViolentCrumble I'll be testing it and will let you know what works so you can also try.
tried commands below and works for me. Now logged in and version showing v1.0.2
git checkout v1.x.x git pull ./nodebb upgrade
@charles Not sure what i am doing wrong, but this happens
charles last edited by charles
@ViolentCrumble I was confused with commands too.
git checkout v1.x.xexactly as shown. do not add any numbers. after that you can use the other commands shown in my previous reply.
./nodebb restartand then check the version again
@charles Whelp, now it's showing 1.0.0 and isn't showing any stats
@ViolentCrumble that is strange that you have
when I try
git checkout v1.x.xI get
Already on 'v1.x.x'
Your branch is up-to-date with 'origin/v1.x.x'.
@charles I think i might have broken something when i was attempting to backup my forums using git...
When i type git remote -v
i get my own personal git directory. i think i done and gone broken something
@charles ANy ideas how to fix this?
What do you get if you type git remote -v
origin https://github.com/NodeBB/NodeBB.git (fetch)
origin https://github.com/NodeBB/NodeBB.git (push)
@charles ok removed old origin and set new origin. now it shows correctly but now it doesnt work still
I don't know enough about git to know what else to look at?
Danny McWilliams last edited by
@ViolentCrumble that happened to me the last two updates. Restarted the forum from ACP, refreshed the browser, went back to ACP and it updated.
Charly86 last edited by
I just upgraded from 1.0.0 to latest (Control panel told me new version 1.0.1-auto0) so I did
./nodebb stop git fetch git reset --hard origin/v1.x.x ./nodebb upgrade #(could take up to 5 min) ./nodebb start
Now control panel tells me I'm on V1.0.2 all is fine