Re-install Revo 2.5.4?

Quote from: BobRay at Feb 02, 2017, 08:28 PM

Yes, that suggests a couple of possibilities:

1. You have an issue with file/folder permissions or ownership.

2. You're out of disk space.

It doesn't seem that there are any issues with permissions or disk space.
Could this have happened if there was an connectivity problem during upgrade?

I really want to re-run setup but I'm a little apprehensive.

Did you do the initial update manually, or did you use Bobs Upgrade MODX snippet?

Quote from: andytough at Feb 03, 2017, 04:33 PM

Did you do the initial update manually, or did you use Bobs Upgrade MODX snippet?

I used Bob's snippet

In that case I think the logs suggest, as you suspect, that some files failed to copy over during the upgrade.

I would wait to see what Bob says but, under the circumstances, I think two options suggest themselves:

1. Re-run Bob's snippet but consider allowing more time for the files to download. Andy you will need to trick the snippet into thinking there is an upgrade available.

See Bob's notes on both these: http://bobsguides.com/upgrade-modx-package.html .....

If either site is slow to respond, or you're on a slow internet connection, cURL or fopen will time out and the last check value won't be reset (you should see error messages in the widget if it's set to show all the time). UpgradeMODX will check again on the next load of the dashboard. Usually, reloading the dashboard page will solve it. This could happen over and over and cause slow loading of the dashboard until the sites respond within the time limit. If it's a significant issue, change the &githubTimeout and &modxTimeout properties and/or the &attempts property.

If you would like to hide the widget when no upgrade is available, change the

&hideWhenNoUpgrade

property.

OR...
2. Do the upgrade manually

Whatever you do make sure you have backups!

Connectivity couldn't have caused the copy failure.

The only error that might be related to that is this one (and it could possibly have been caused by the failure to copy the files):



At any rate, if the files can't be copied, the upgrade isn't going to work. Since permissions and disk space are OK, my money would be on file ownership, though that's not an area of expertise for me.

All that said, I would be tempted to just upgrade the old fashioned way as AndyTough suggests, using this method: http://bobsguides.com/modx-upgrade-faq.html. Be sure to manually delete all files in the core/cache directory before logging in.

[Update] This just occurred to me and it seems pretty unlikely, but if the file extraction timed out, maybe some of the files to be copied didn't get extracted, and thus didn't exist, and that's why the copy actions failed. Again, probably the best solution is to just do an old-fashioned upgrade. [ed. note: BobRay last edited this post 7 years, 2 months ago.]