@jw-sbat Always make sure the plugins you are using are working fine before deploying to production. Even if the plugin doesn't specify compatibility directly it could still work. That property specifies a minimum nodebb version.
Upgrade v1.0.2 to v1.4.2
-
I'm doing something wrong, or an error is correct?
11/1 21:56:05 [67685] - info: Beginning database schema update 11/1 21:56:05 [67685] - error: [upgrade] NodeBB upgrade could not complete, as your database schema is too far out of date. 11/1 21:56:05 [67685] - error: [upgrade] Please ensure that you did not skip any minor version upgrades.
Do I need to pull every minor version and run
./nodebb upgrade
? -
@Nicolas yep
-
Oh boy. I am going to be in the same boat.
What is the best git command to get them?
-
You'll likely have to check out an earlier tag from git... going from v1.0.2 to v1.4.2? Yikes, what a jump!
From git, try
git checkout v1.1.0
, does that work? Upgrade.Then repeat, substituting
v1.2.0
, then v1.3.0, and then finallygit reset --hard HEAD
again and upgrade once more from the latest commit. -
@julian Thank you.
I have been updating my dev site periodically to test my customizations and plug-ins. I really should have been keeping my production updated a bit more. Oh well.
-
I thought minor version will be friendlier for the upgrades
-
Good news is the incremental updates from
v1.0.2
tov1.4.2
worked in my dev environment. I captured the few changes I will need to make when I do this in production. Which I should do this week. -
@Nicolas said in Upgrade v1.0.2 to v1.4.2:
I thought minor version will be friendlier for the upgrades
Yeah one'd think... we're thinking of switching back to versioned branches again...
v1.5.x
and such. -
And finally upgraded to
v1.4.2
for my production site. -
This post is deleted! -
This post is deleted!