Unable to remigrate after "completed" migration
under review
B
Benjamin Tennant
I also find it very difficult to start the migration again once stalled or cancelled. Or I've had it where I migrate to the wrong account accidentally and I simply cannot get the migration tool to allow me to enter new connection details. It's really frustrating that there is not some kind of reset button.
Kevin Hoffman
under review
Kevin Hoffman
Hi Tim Paone. I'm the product manager of the WP Engine Site Migration plugin. Thank you for taking the time to provide feedback. I reviewed your migration from June 18th. I see the completed migration, and I understand you're being prevented from starting another migration.
Possibility 1
: There could be cached migration state in your browser. Here are steps you can take to rule out this possibility:- Right-click on the webpage and select "Inspect".
- In the Developer Tools pane, click on the "Network" tab.
- Check the box next to "Disable cache" (you'll see this option at the top of the Network tab). Note: This setting only applies while the Developer Tools pane is open.
- Refresh the Site Migration page in WP Admin and let me know if that allows you to start a new migration.
- Alternatively you can try logging in to WP Admin with completely separate browser to see if the browser cache is the cause.
Possibility 2
: There could be leftover migration state in the database that was not cleaned up as expected after the migration completed. Here are steps you can take to rule out this possibility:- Deactivate and delete the WP Engine Site Migration plugin. This will remove all options in the database starting with wpesm_.
- Reinstall and reactivate the plugin.
- Attempt to start a new migration.
Possibility 3
: I also see Object Cache Pro installed as an mu-plugin, so it's possible that a cached value is being returned independently from the plugin. Removing the mu-plugin from the source site may have an effect.Please let me know if any of these suggestions allow you start another migration. We also have an issue opened internally to attempt to reproduce it.