Codexonics

As an update, we’ve identified the issue and sent you a hot-fix version of the Prime Mover plugin. Please do another restore by starting with a fresh WordPress installation. And then restore the package using the hot-fix version provided.

Details of the procedure to restore your site was included in our bug report replies. We’ve tested the procedure using the provided package and it works now without any runtime errors. Please confirm in your end. Thanks! 🙂

We have replied to the site details report you’ve sent. We tried reproducing but unable to see the problem. I’ve noticed you have used some premium plugins that we are unable to test.

Did you try to see if there are JS console errors when you try to click “Export” ?

If you see console errors, please share. It would be worth trying each of the following to narrow down the problem:

1. Try enabling JS debug in WordPress by adding this to the wp-config.php<

define( 'SCRIPT_DEBUG', true);

Once added, clear cache and then try again.

2. Deactivate each of the plugin at a time, clear cache. Check if deactivating some plugin can activate the export now button. This way, you can isolate if some plugin is causing this.

Let me know how it goes. Thanks!

• This reply was modified 5 years, 7 months ago by Codexonics.

Thanks that’s very strange. We never encounter issues like this before. We need to find out what is causing this. First; we need to reproduce this issue and it’s possible it has something to do with third party plugin conflicts. To help us resolve this issue, can you please do the following:

1. Login to your WordPress admin /network admin and go to Prime Mover -> Contact Us.
2. Submit a formal bug report to us by filling up the details. And select “Bug” type.
3. Go Tools -> Site health -> Click “Info” tab -> And click “Copy site info to clipboard“.
4. Send us all these details using that form, so we will know what plugins/setup/configuration you are using and we will check.

Thanks!

Thanks for the reply. I see that you have obtained a PRO license. We already replied to you via PRO support channel. We will close this ticket to avoid duplicating issues. Please reply it there.

WordPress forum does not allow support for PRO products here.

Thank you for understanding.

Hi Joe,
Thank you for using Prime Mover as your migration solution. I see that you have done the export and now you are attempting to import the package to your single site installation.
And that during this import, it appears stuck and not making any progress.
If this is the case, the best solution would be stop the import by doing the following:

1. Refresh the browser where the import is ongoing – this will automatically stop the import
2. Clear your browser cache.
3. Login using SFTP or FTP and clean up all temporary files in the path /wp-content/uploads/prime-mover-import-files/. This will regain disk space by deleting these files
4. Now please repeat the import process by following the steps in this tutorial: https://codexonics.com/prime_mover/prime-mover/how-to-restore-large-packages-with-prime-mover-free-version/

Summary of this solution: Usually most import issues are associated with large packages upload and restore. The alternative solution is upload the package using SFTP/FTP client (e.g. Filezilla) directly to the Prime Mover export directory and then restore it easily within WordPress admin.

If you still see issues, please contact us directly by reporting the bug within WordPress admin -> Prime Mover -> Contact Us.

Thank you and let me know how this goes 🙂 Cheers.

Thank you for the 5-star review! Glad you found the plugin very easy to use 🙂 Cheers!

Thanks for reporting this issue. We tried to reproduce this scenario (doing a subsite to subsite migration) but it appears fine. I suggest to do the following quick troubleshooting to isolate the problem. Skip the any step if you already done it:

• Make sure you are using the latest version of Prime Mover that is version 1.1.9 on both sites.
• If you are uploading, your connection might have been disrupted. Try restoring within server by following this tutorial. It requires you to upload the package using FTP to the target multisite server.
• Try restoring a db-only package (not a complete package) to see if it completes restoration

I see that you contacted us via the plugin bug report form. I will follow-up. Thanks.

• This reply was modified 5 years, 8 months ago by Codexonics.

Hi Leo, Thanks a lot for the 5-star review 🙂