This is what happened when I updated UpgradeMODX
I have openSSL turned off on the local server. Any suggestion how to disable this check welcome.
Just turn off the ssl_verify_peer property of the widget snippet. I had to set up openSSL on XAMPP to get it to work with that set to true on my local install.
It's less secure without it, but since it's just downloading, I don't know how serious a problem it would be. I suppose someone could spoof the MODX or GitHub server and you could download and install a version of MODX with a built-in back door, but it's probably not a high-probability threat.
Awesome, thank you!!
...Sorry for not reading the changelog and your awesome trobleshooting guide.
I'm glad you got it working.
First up, great plugin - although most of my MODX sites are on MODX cloud, I've used it previously on a couple of small test sites and it worked perfectly. I also tried this on a MODX cloud dev version of a larger site and it worked. However, I just tried to upgrade the same site on an external server and I got a 500 error and an error message (screenshot attached).
The site is currently 2.3.1-pl (traditional), mysql 5.1.73, PHP 5.3.3, Apache 2.0.
It has to be said that I have had issues with permissions on files before when installing plugins - I need to get the IT dept to change settings even though it appears to look like I can change the settings myself via Transmit. I managed to install the plugin with no problems and the widget appeared. When I actually clicked on upgrade, I was asked to set 'core/export/' and 'core/config/config.inc.php' to be writable. I did this via Transmit and proceeded but I got the error message and the site 500'd.
I had to get the IT guys to restore the website, but I was told that after they restored just the config.inc.php file the site became visible again.
So do you have any ideas what might have gone wrong? My best guess is that the 'core/export/' and 'core/config/config.inc.php' were not actually as writable as indicated to me, even though the plugin did proceed normally once I had changed the files to writable.
I'm afraid not. Your error messages look like data is not getting through to setup, but I don't know why.
I agree that permission issues are a good bet, but file and directory permissions depend on how the server is set up. In many cases, making the permissions more permissive makes the files and directories *less* accessible. For example, some servers that want 755 directory permissions will refuse to run PHP files in 777 directories. There could also be file ownership issues.
I don't have a lot of experience with that kind of thing, because I only use MODX-friendly hosts
Sorry I can't be more help.
I get the following errors:
Win 7, xampp local, php 5.4
Deprecated: Assigning the return value of new by reference is deprecated in C:\xampp\php\pear\PEAR\Autoloader.php on line 146
Fatal error: Method PEAR_Autoloader::__call() must take exactly 2 arguments in C:\xampp\php\pear\PEAR\Autoloader.php on line 210
Will report back when I figure out how to solve this!