Failed Migrations / Search-Replace – Introduce Database Character Set Check & Warning

I’ve experienced several times migrations not changing the URLs correctly because the search and replace fails.

It fails because the database being imported and the destination database are different character sets which can lead to the special characters in URLs being percent encoded, and therefore fail search and replace.

From a workflow perspective, it is frustrating to have to check database character sets before performing migrations.

Even more frustrating is when a migration is reported as successfully performed, yet the truth is that many URLs in the migrated site are still the old site URL as it wasnt actually migrated successfully.

Is there some kind of check you could build into Updraft Plus that would alert users to this issue? Similar to the WP version & PHP version warnings.

This would make the product a lot more robust, and prevent migration failures happening on a regular basis.

 

 

 

twitterlinkedinFacebook

Submit a Comment