Codexonics

Hi, thank you for using Prime Mover! It looks like you are migrating to a WordPress single site. Can you please try the following steps?

• Create a single site export (if you still have not done this).
• Wait until the export is successfully done. You should see confirmation that the export is successful.
• Download the package to your Desktop using FTP/SFTP to make sure it will not get corrupted. You can download it from the Prime Mover export directory. Please refer to these steps on how to download the package.
• Once you have downloaded the package – you can restore it to your target single site. In this case – you will need to have Prime Mover latest version also installed in your target site. We recommend to have a fresh WordPress installation if possible. To restore the package – you will need to upload the package using SFTP to your target site export directory of Prime Mover.
• Login to your target site and go to Prime Mover -> Packages. If the package is not corrupted- you should see it there. Otherwise – you should see a corrupt package error. If the package is corrupted – you will need to re-create the package again , download and restore (repeat the above steps).
• Wait until the restoration is completed.

If you still having issues or the above steps does not work -please share with us the link to download the WPRIME package in our contact page. We will use this to reproduce the issue that you have reported in our test servers. Please also include relevant screenshots, site information and migration logs.

If the above steps works for you – please mark this ticket as resolved. Thank you!

Hi Nicholas,

Yes please refer to our troubleshooting guide on this issue.

In general – this is usually caused when an AJAX process is unable to start. It is because of conflicts or errors. It could be as simple as an expired login session or could be caused by PHP errors. The troubleshooting guide provides all the details on the common possible reasons as well as the workaround.

If you are still having issue – please contact us and provide all the logs as suggested by the troubleshooting guide. We will follow-up there and closing here.

Thank you again!

Cheers,

Emerson

Hello Nicholas,
Thank you for using Prime Mover! Strange – the first 3 sites are migrated and the fourth is stuck. Can you please do the following troubleshooting?

• Please make sure you are restoring using latest version of Prime Mover.
• If you have access to your PHP or server – try restarting it.
• If you have access to your MySQL or database service – try restarting it also.
• Once restarted – clear your browser cache.
• Login again to your target multisite.
• Repeat the restore for the target fourth subsite.
• If you are doing all the site restorations in a single day – try taking a break and do the restore on the next day. This will allow your hosting to reset some limits that might be reached after your continuous migration.

Example of hosting limits that can be reached includes number of SQL queries that can be executed in day, etc. This might not be appear in the PHP error logs as this is only a hosting specific resource control.

If the issue is still reproducible – please send us the following to via official contact form.

• Link to download the fourth WPRIME package where you have issues restoring. You can upload this to Gdrive or Dropbox. We will use this to diagnose the package and do a test restore to see if this issue is reproducible in our end.
• Please generate debug and migration logs and do a screenshot of the error.

Once we have all the information – please give us time to analyze it. Thank you again and have a great day!

Thank you for using Prime Mover and for rating us 5 stars! We are happy to hear your multisite migration experience with the plugin 🙂 Cheers!

Hi Kieran – Thanks for sharing your experience in using Prime Mover and for rating us 5-stars! Cheers.

Hello Nianuu, thank you for using Prime Mover and for rating us five stars! Cheers 🙂

Hello Elsmore,

Thank you for using Prime Mover in your projects! Usually when import hangs it has something to do with lack of memory or a runtime error. Strange you didn’t catch any errors in the log (with debugging enabled).

Can you please try doing he restore using our latest Prime Mover 1.6.1-beta2 version? Please re-test as follows:

• Download the latest Prime Mover 1.6.1-beta2 to your Desktop.
• Deactivate Prime Mover 1.6.0 and uninstall delete that old version.
• [OPTIONAL] Since you are restoring to a single site – it would be great if you can start with a fresh WP single-site installation to make sure the dB is clean. If this is not possible skip this step.
• Install/upload Prime Mover 1.6.1-beta2 and activate it to your site (network activated if multisite).
• Restore the package.
• Check if the restore still hangs on the import database process with 1.6.1-beta2 version.

The beta version has bug fixes on database restore errors we’ve seen during testing. It would be great if you can try that to see if it works.

If you are still having the issue after using the latest beta:

• Upload the WPRIME package to Gdrive or Dropbox.
• Contact us here and provide us the link to download the package.
• If you can attached any migration or updated error logs that would be great.

We will try to reproduce the issue on import DB hang on our test servers using your package and then debug what is causing it.

If the beta version fixes the issue – please use that version for now and mark this ticket as resolved. An official stable version will be released in a couple of days.

Thank you and have a nice day!

Cheers,
Emerson

Hi John,
Thank you for using Prime Mover in your projects! Since the site is now migrated and every thing is working – Migration code does not anymore run at this stage. So this is not something related to Prime Mover. We also don’t find this reproduced in our test site.

Looking at the error – it looks like it has something to do with WooCommerce ActionScheduler table. Maybe it would help refreshing the Scheduled action table to see if it works. Simply go to WooCommerce -> Status -> Scheduled Actions. Visiting this page will auto-refresh scheduled actions table.

WooCommerce also includes several tools to refresh data. You can find this in WooCommerce -> Status -> Tools. Sometimes these data are cached and stay in the database which could result intermittent errors after a migration. So using these tools will help clearing things up and adjust to it’s latest state.

These are just suggestions if you could encounter this error. And it’s recommended to backup your database before using these tools – to be sure. However it would be helpful if could share this error to WooCommerce support to get their input on this error. Maybe it’s a just caused by residual cached data after migration (which are cleared using WooCommmerce tools).

If these things help and you don’t need anymore technical assistance. Please marked this ticket as resolved. Thank you!

Cheers,
Emerson