-
- 24,544 Posts
UpgradeMODX provides a dashboard widget that alerts you to new versions of MODX and (optionally) installs them from within the Manager. The docs are at
Bob's Guides.
The extra has been working fine for me, and should updgrade any MODX site except the SDK version (including hardened sites with moved and/or renamed directories), but it needs to be tested on a few more platforms before a pl release.
Version 1.0.1-beta1 had trouble on some versions of PHP, and version 1.2.0-beta1 didn't work unless you pre-created the Setup folder.
[ed. note: BobRay last edited this post 8 years, 7 months ago.]
-
- 24,544 Posts
Please report back here if you were able to successfully upgrade your site with this extra (or not).
-
- 49 Posts
Bonjour, hello
Server apache
PHP Version 5.5.25
tried to update since 2.3.1 to 2.4.0
The installation return to myssite.com/setup/index.php and display a 404. The setup folder dont seem to be here. A lot of files seem to be installed.
Then i put the setup folder manualy, launch it and all seem to be correct now.
-
- 24,544 Posts
Thanks. I've identified the problem and a new version should be out shortly.
In the meantime, a workaround is to create a directory called 'setup' in the MODX root directory before using the widget for an upgrade.
-
- 24,544 Posts
Version 1.2.0-rc released.
FYI, I just used it to upgrade a hardened production site from Revo 2.0.3-pl (in steps) to Revo 2.4.0-pl. I've tried to upgrade the site several times before without success. Setup asked me to manually edit the core path, but otherwise, it was a piece of cake.
I don't know where Setup gets its bogus core path, or why. It ignores all the config.core.php files (even the one in setup/includes) for no apparent reason.
Probably because in a new installation there isn't one, and they thought it a better idea to have the user manually enter the core path than to go around looking for files.
-
- 24,544 Posts
Yes, but setup knows it's in upgrade mode and one quick look at dirname(dirname(__FILE__)) . '/config.core.php' would solve it. There will always be a config.core.php file in the MODX root when upgrading.
It's kind of weird to recommend that people move the core above the web root and then have setup freak out when they do it.
-
- 24,544 Posts
That's really a suggestion rather than an error, though it's a pretty good suggestion.
Moving the core to a directory above public_html and editing the config.core.php files (MODX root, connectors, manager) to reflect the change makes your site *way* more secure. Delete all files in the core/cache directory after making the change. UpgradeMODX will still upgrade the site, though Setup will ask you for the core path.
The executable code for all extras is in the core/components directory. There could be a security vulnerability in *any* installed MODX Extra (and several have occurred already). Moving the core above the web root means that no bot or browser can execute any of the files there.
[ed. note: BobRay last edited this post 8 years, 6 months ago.]