2.2.5, huh? I don't envy you
You don't have to logout before starting an upgrade, the sessions table should get wiped clean automatically.
400 errors could be because of cookies. Try clearing the ones in your browser to see if that helps. Otherwise, just start updating and hope the update fixes it? :p
Make sure to check the plugins and users after you're updated to make sure you haven't been hacked by the < 2.5.2 vulnerabilities.
discuss.answer
-
- 24,544 Posts
I'd recommend upgrading to 2.3.0, 2.4.0, and 2.5.0 before upgrading to the current version
-
- 93 Posts
Many thanks, I will get upgrading later.
-
- 93 Posts
All worked fine - thank you again for help.
For anyone else, I downloaded 2.3.0 merged / sync'ed using SmartFTP. Installed fine. Logged in using Chrome (for some reason Edge screwed up the Manager CSS) and then downloaded the Extra - UpgradeModx. Back to the Dashboard and then went straight for the latest version. Boom, it worked and now I can complete the content update.
Regards, D
-
- 93 Posts
Arrrghhh, spoke too soon.
Clicked in to the resource tree and each page is giving the below error;
Fatal error: Call to a member function get() on array in /davidjury.com/html/manager/controllers/default/resource/resource.class.php on line 152
But a quick check on the Forums says upgrade TinyMCE and all good.
Thanks !
-
- 24,544 Posts
Just a note, upgrading by transferring the files individually with FTP often results in missing or corrupted files. Maybe you got lucky, or maybe quirks will show up later.
You'll definitely want to check out the
UpgradeMODX extra which should make life a lot easier.