Plugin doesn't continue
under review
C
Chris Cook
Kevin - I believe I found the issue. The plugin was throwing the following error:
main.271d19af354e.js:1 Mixed Content: The page at 'https://www.domain.com/wp-admin/tools.php?page=wpe-site-migration' was loaded over HTTPS, but requested an insecure resource 'http://www.domain.com/wp-json/mdb-api/v1/migration'. This request has been blocked; the content must be served over HTTPS.
Reviewing the WordPress Address and Site URL, it appears that they were still set to http only. Updating to HTTPS has allowed me to move on to the next step of the migration.
Kevin Hoffman
under review
Kevin Hoffman
Hi Chris Cook. I'm the product manager of the WP Engine Site Migration plugin. If pressing "Continue" doesn't do anything, the cause is likely due to a failed REST API request to the endpoint registered by the WP Engine Site Migration plugin. A third-party theme, plugin, or environment condition may be preventing the request from being completed.
To confirm if this is the case, please try the following steps and share your findings:
- Open your browser's DevTools by right-clicking on the webpage and select "Inspect".
- In the Developer Tools panel, click on the "Network" tab.
- Refresh the Site Migration page. This will load all network requests in the Network tab.
- Click "Continue".
- Look for a failed request in the "Network" tab.
- In the request details panel, go to the "Response" tab.
- Right-click anywhere in the response content and select "Copy".
- Choose "Copy response" from the context menu.
C
Chris Cook
Hi Kevin - The response tab says "Failed to load response data: No data found for resource with given identifier". There is no "Copy response" menu
C
Chris Cook
Kevin - I believe I found the issue. The plugin was throwing the following error:
main.271d19af354e.js:1 Mixed Content: The page at 'https://www.domain.com/wp-admin/tools.php?page=wpe-site-migration' was loaded over HTTPS, but requested an insecure resource 'http://www.domain.com/wp-json/mdb-api/v1/migration'. This request has been blocked; the content must be served over HTTPS.
Reviewing the WordPress Address and Site URL, it appears that they were still set to http only. Updating to HTTPS has allowed me to move on to the next step of the migration.
Kevin Hoffman
Chris Cook: Thank you for following up. I will pass this along to our engineers to see if we can better handle the http(s) discrepancy and surface a more useful error in this situation going forward!