Restore Failing

[baconfamily85Participant]

Hi,

This was working for me before, but not currently.

I backed up: https://www.columbiapregnancycenter.com/

Restored it to: https://www.sthelenspregnancycenter.org/

The restore completes but if you look at the web site it is very messed up, compared to the original.

I created two separate full manual backups, both did the same thing.

When I restore I up loaded all the zip files to the updraft directory, rescan and restore.
I check all the boxes except the config file option.

Thanks, Mike Bacon

[baconfamily85Participant]

A few weeks ago I updated to version: 1.7.3.10, beforeI was using 1.6.46.9.
This is the first restore I have tried for several weeks.

[udadminKeymaster]

Hi Mike,

I notice that you have a minifying plugin – does it make a difference if you turn this off on the ‘new’ side of the migration? Also de-activate any cacheing plugins, as mentioned in the migration instructions.

David

[baconfamily85Participant]

Hi David,

So I need to disable them before making the backup?

Thanks

[udadminKeymaster]

Hi Mike,

The migration guide recommends it – ‘Also, cacheing and minifying plugins are a common cause of migration problems (whatever method you use). Disable all of those before you create your backup – or alternatively, just be ready to turn them off if the migration stumbles.’ – https://updraftplus.com/faqs/how-do-i-migrate-to-a-new-site-location/

However, it’s possible you may get success just by turning them off and on again after migration (on the ‘new’ side) – you could try that to save time.

David

[baconfamily85Participant]

Disabled the caching/minifying didn’t help post-restore.

So I disabled the entire cache plugin, and then re-performed the backup/restore.
I had the same result.
Thanks

[baconfamily85Participant]

I think that was old cache in my system, refreshing a few times fixed it.

But I am unsure how to schedule backups if I have to have the caching/minifying disabled for them to work.

Any suggestions?

[udadminKeymaster]

Hi,

It sounds like you just need to turn the cacheing/minifying plugins off, *and empty the caches*, post-restore, and you’ll be fine? (i.e. before you just didn’t empty the caches?).

In a future update we’ll empty some common caches automatically, as it never hurts.

David

[baconfamily85Participant]

Hi David,

To get the restore to work when backup has cache/minify enabled, I had to turn off minify post restore and leave it off.

After I clear all cache and turn off minify and the restored site is working. If I then re-enable minify, the minify plugin complains about filename length being over 150. There is no such error on the site from which the back was made.

I was able to turn off that filename length “check” in the plugin and get around the error, and minify seems to be working.

However, I am curious why this error would show up on the restored site and not the original site? The domain name is shorter that the original site.

Thanks, Mike

[udadminKeymaster]

An excellent question, but it sounds rather like one for the author of the minifying plugin! I’d guess that the path where your website lives on the migrated side is longer than on the old, and hence triggers the 150 limit due to the larger prefix. But I can’t give you an authoritative answer on that, of course.

David

[Author]

Posts