Codexonics

Thanks for contacting us. Sorry this feature is not supported. It is why there is no restore or export button on the primary/main site.

Prime Mover can only migrate site (or sub-sites) from one domain to another but not the main/primary site.

This is currently listed as one of the plugin’s limitations in our docs: https://codexonics.com/prime_mover/prime-mover/faq/#prime-mover-limitations

Yes, can you please delete all .part files inside /prime-mover-import-files/ directory?

Once you delete it, try restarting Apache and see if you can now access the Network Admin.

If the issue still persist (you still get no space left on device error), try deleting all files inside /prime-mover-import-files/, including the uploaded files. And then restart Apache again.

This should free up some space in your server and you should be able to access network admin.

If that won’t resolved, we need to understand this issue deeper in your site, in this case I suggest to contact us in our official site and request for technical support.

Since this is a public forum, and we could not debug issues here in details.

Yes, reducing file size helps a lot. There is also another possible solution which is available in the pro version. Prime Mover remote restore url feature:
https://codexonics.com/prime_mover/prime-mover/how-to-export-and-restore-using-pro-version/

It works like this:

1. Generate export package(you already done this)
2. Upload Prime mover package zip using your favorite SFTP client to your target site WordPress root directory. So that the resulting path is like https://yoursite.com/myprimemoverpackage.zip.
3. Activate Prime Mover Pro on your target site.
4. Go to Tools -> Migration Tools -> click Import -> click Restore backup zip from a remote URL and the paste the URL to your zip which is now inside your site.
5. Prime Mover fetches the zip which is now inside your server and it does the rest of the restoration process

The above solution is preferred when browser uploading is not reliable (especially for big files) and you have limited speed. SFTP uploading is usually better than plain browser uploading which can be slow.

Sure, but first I would like to know on what part does the error occurs. Does the error happens while uploading? Or does it happens only after uploading?

The 1.0.4 beta version deals with the fixes on server timeout on processes after the uploading part. So if it times out while uploading, you might want a connection with higher upload speed and see if it works.

Also with the size of 2GB, you can try to minimize that by deleting unused files in your uploads directory which is no longer needed on the target site.

OK I found the issue after checking the updated logs. Prime Mover checks the theme version used when exporting so it can be compared during restoration process to check for theme differences. It’s included as required footprint of the source site. It is why without this, it returns invalid system footprint error.

The exporting site is using a child theme Divi-child that does not include a theme version.

To fix the error, can you please add a version to your child (Divi-child)? This is done in the child theme style.css file.

For example from: (before)

/*
Theme Name:   Divi Child Theme
Theme URI:    http://xxx.com
Description:  Child theme, based on Divi
Author:       xxx xxx
Author URI:   http://xxx.xxx
Template:     Divi
*/

@import url("../Divi/style.css");

TO: (after -this is the right way – including theme version)

/*
Theme Name:   Divi Child Theme
Theme URI:    http://xxx.com
Description:  Child theme, based on Divi
Version:      1.0.0
Author:       xxx xxx
Author URI:   http://xxx.xxx
Template:     Divi
*/

@import url("../Divi/style.css");

Reference: https://developer.ww.wp.xz.cn/themes/advanced-topics/child-themes/#2-create-a-stylesheet-style-css

Try this one and the export error should be resolved. Let me know how it goes 🙂

Thanks but it seems it still showing the old log, did you activate the foot print logging plugin? Or did you save it to pastebin again?

The new log should contain the phrase Footprint keys for validation. Please review.

Thanks for reporting this issue and for all the logs. Usually this occurs when exporting a site that is already having configuration problems (by itself). For example, exporting a site without an active theme activated in dB but deleted, invalid site url, etc. Based on the log provided, it shows it indeed fails on footprint validation.

The current version 1.0.3 does not yet include a detailed logging to see the footprint data in details. We will add it on the future version. To understand the issue, we want to know what part of the footprint is missing or invalid. Can you please do the steps below:

1. Download this Prime Mover footprint logging plugin.
2. Log-in as administrator go to Plugins -> Add New and upload that plugin zip: prime-mover-footprint-log.zip.
3. Activate the plugin named as: Prime Mover Footprint Log
4. Enable all logs as what you have done first time when you report this issue
5. Now the footprint log is enabled, re-generate the export (to reproduce the error) so it will re-generate another set of logs (now including footprint which we need to analyze).
6. Update the log in your pastebin with the latest log containing footprint data: https://pastebin.com/VrN7PyfM

You will know that the footprint data is logged when it contains “Custom log for site footprint data” in the log. Let me know if this is added so I’ll re-check the log for analysis. Thank you !