Answered UpgradeMODX

Hi, I'm having problems with the UpgradeMODX package

On one server using https I'm getting:
websitepath/modx.zip is empty -- download failed

curl is enabled

And on another server without https it worked ok, and on another I'm getting that 2.5.1 is the latest and it's not showing an upgrade button at all.

Any suggestions? [ed. note: natedin last edited this post 7 years, 5 months ago.]

The first problem may be from a slow response from either MODX or GitHub, but you can try changing the forceFopen property of the UGM widget snippet.

The second problem is fairly common, but I haven't been able to figure out what's causing it. It's usually temporary. Check the lastCheck and latestVersion properties of the widget snippet. Manually changing the second one to 2.5.2-pl might work.

Hi Bob, I've tried and it did work on a few sites however on localhost it's still not working. I've tried disabling open_basedir in php.ini and that still brings up the 'Return to Manager' page. Is there anything else I can try? It seems to download a modx.zip which is cannot be opened (10,912kb) "error: central directory not found"

I'm running WAMPSERVER Windows 10, PHP v5.4.12, cURL enabled, fopen enabled, Apache 2.4.4 newest veresion of UpgradeMODX package.

Thanks

I had a little trouble with using it on Localhost at first. As I recall, it had to do with SSL certification, which is tricky to set up.

You could try using cURL and changing the ssl_verify_peer property. I don't recommend leaving it off, but if it fixes things, you know it's a certificate problem.