I'm glad it's working for people.
I'm loving this upgrade extra. It has worked well on several sites. I just encountered one, however, that blew up.
Attempting to upgrade Modx 2.2.10-pl
Shared Hosting: Hostmonster
Made it all the way to the system checks. All were OK. When I clicked continue to begin the installation I got a white screen. The front-end was a white screen as well.
This was in server error log:
[24-Sep-2015 14:17:52] PHP Fatal error: Call to a member function get() on a non-object in /home2/xxxxxxx/public_html/core/model/modx/modrequest.class.php on line 192.
I restored the site to the previous day from the cpanel backup/restore.
I'm going to try upgrade in the usual way.
The upgrade done the usual way worked just fine.
[ed. note: terrybarth last edited this post 5 years, 8 months ago.]
Once you're in Setup, UpgradeMODX doesn't have much to do with things, unless it failed to download or extract some file to the right place. If it's a vanilla MODX install, that's pretty unlikely.
Perhaps the server doesn't have the PHP version that 2.4.x needs?
So, people have different workflows in order to upgrade MODx, some are more elaborate than others, other methods are just plain weird and often guarantee a crash.
Anyways, I was loving my method, since it always worked...and skipping all of that was...I mean the thought of skipping all those steps filled me trepidation, strangely!
Then came UpgradeMODX.
I have never been more afraid to click a button.
I think my greatest fear was this extra would leave my MODx subfolder, enter the root of my domain and delete my account, and while at it, add a few more ../ and delete the internet.
You all know how officious PHP can be.
"But surely Bob Ray is more careful and more awesome than that!?", I thought to myself in order to cure my unassuagable fright.
...SUSPENSE ...SUSPENSE ...SUSPENSE
I clicked, saw and was conquered!
I just lost maintenance fees ...don't let clients find this Extra.
: Complete back/frontend content solution.
Harden your MODX
site by passwording
your three main folders: core, manager, connectors
and renaming your assets
(thank me later!)
5 ways to sniff / hack
your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
You think you were worried. Imagine me worrying about the extra trashing countless sites.
I've been using this plugin for the past few weeks, and it sure makes things easy! On one site I just installed this on, however, I'm getting this error message after selecting the modx version from the file list and clicking the big Upgrade button:
Could not get downloaded filename
What's up? What do I need to check? The site was 2.2.16 initially. I updgraded manually to 2.4.0 and still get the same error.
UpgradeMODX downloads the file to a /temp directory. That error occurs when it can't read that directory, so it's likely a problem with the permissions or ownership of that /temp directory. IIRC, it should be below the directory with the UpgradeMODX files.