Prevent "initialization failed" error
complete
Y
Yvonne Cariveau
Below is a screenshot of what we see every time we try to use the new migration tool. The old plugin works great, every time. We have not had the new one work once. This site environment was created yesterday, tried the migration this morning and got this same result - note the Migration ID on the screenshot in case that's helpful.
Kevin Hoffman
complete
As of WP Engine Site Migration 1.0.0, REST API endpoints that previously used
PUT
or DELETE
now use POST
for compatibility with more server configurations.Kevin Hoffman
in progress
We've identified the cause of this error to be the server blocking
PUT
requests to the WP REST API endpoint that the plugin uses to run the migration. This may be common for certain Linux distributions. If you open your Dev Tools Console and see "403 (Forbidden)" errors, this is a sign that your server is blocking those request types. To address the issue, we are replacing PUT
and DELETE
requests with POST
requests in an upcoming release.Kevin Hoffman
under review
Kevin Hoffman
Hi Yvonne Cariveau, I'm the product manager of the WP Engine Site Migration plugin. Thank you for sharing this feedback. I've reached out to you via email to see if we can get an admin account created on the source site to troubleshoot the migration further.
Y
Yvonne Cariveau
Kevin Hoffman I've replied with that account information - using the Migration planner tool and secure password tool provided to us by your team when we were originally starting these migrations. I appreciate your attention to this!
Y
Yvonne Cariveau
It seems that this new version that fixes the issue with servers that don’t allow PUTs hasn’t been officially released on the portal yet.
Today, I tried to re-migrate a site that I’d successfully migrated last week and it gave an error. Ultimately, we figured out the error was due to the WPEngine site having the 1.0.0.r.3 version of the plugin and me using the 1.0.0.r.4 version that you sent on the source site. I had put that r.4 version in both places, but there was a delay and during that delay SPM updated over the WPEngine version of the site with the 1.0.0.r.3 which it thinks is the current version.
So, please can we get the updated version as the official, latest release soon? Thanks!
Kevin Hoffman
Yvonne Cariveau: Hi Yvonne, the latest 1.0.0 release (released April 4th) does include the PUT change. You can download the latest version or visit WP Admin > Dashboard > Updates to trigger a new check for plugin updates. You should then see an update for version 1.0.0 available.
My guess is that the pre-release version we provided you was overwritten because SPM checked for the latest official version. That should not happen going forward.
Y
Yvonne Cariveau
Kevin Hoffman The version that was there was 1.0.0...no version number change? I'd recommend doing that so that folks can tell there's been a new version issued. I'm running into problems migrating a site today - tried the 1.0.0.r3 and 1.0.o.r4... getting errors and migration failures. The tech person in chat is telling me they can't help me and I should manually migrate sites. Can I get some help with this?
Kevin Hoffman
Yvonne Cariveau: The version that we provided you was 1.0.0-rc.4 which means it was a release candidate prior to the official 1.0.0 release. WordPress will see 1.0.0 as a newer version compared to 1.0.0-rc.4. I'll email you now to see how I can help.
Y
Yvonne Cariveau
Kevin Hoffman Ah, got it! Thanks for that info. I was able to get the migration to work after re-reviewing what you said above and making SURE that both versions on the source and destination site were the latest releases. THANKS!
Kevin Hoffman
Yvonne Cariveau: I'm glad to hear that. I'm going to close this out since the change to POST requests in version 1.0.0 should prevent this issue going forward.