Codexonics

Hi Rapidasia, thanks for asking this question. Actually there are two ways to change the target blog IDs.

The first one can be done with a free version. You simply need to create a new subsite (Sites -> All Sites -> Add New). After the site is created, a new blog ID should be automatically generated by WordPress for that target subsite. You can then get the target blog ID of this subsite for use with Prime Mover. Once you get this new blog ID, you can then use this to create a new multisite package for restoring to the target site (please refer to Workaround #1 for doing this.)

The second one is a PRO feature. This is similar to the first solution, except that you can actually specify blog IDs when you create the new subsite. The first solution does not allow you to specific blog IDs as it is provided automatically by WordPress. The second solution allows you to do this as long as the blog IDs are still not used with any subsite (IDs should be unique to each subsite in a multisite).

In summary, here are relevant documentation for further reading:

1. Can I change the exporting Blog ID to another site importing blog ID?
2. How to get multisite target blog ID ?

I hope this answers your inquiry, please let me know if you have something to clarify. Thanks! 🙂

• This reply was modified 5 years ago by Codexonics.

Thanks Laurence, we received the long logs in our debug report system. We’ve replied already so please check. Let’s follow-up there thanks!

Hi Laurence,
Thanks for using Prime Mover! First, if the package does not appear on the package manager – it appears corrupted. It cannot be restored since it is incomplete.
Can you please do an export again on the source site and make sure it completes? Once you see Export done or Export completed – try doing a restore again using FTP method and it should appear in the package manager.
If you have problems re-creating the package or it still does not complete, please send us a bug report via WordPress admin/network admin using Prime Mover -> Contact Us and fill-in all the required for us to troubleshoot this issue. Alternatively, you can use this contact form.

Hello Saffa, this ticket is now more than a week old and we have a new release today (version 1.3.4). This issue is now outdated and we are closing this one. If you can upgrade to new version and test – please let us know the results. You already submitted bug ticket to our system so let’s follow-up there. For now, we are closing this one. Thanks!

Hi Saffa,
Thanks for the update. Regarding domain mapping, there will be several possible causes (server related, configuration related, etc.).

Some good suggestions on fixing this can be found: on this thread. And also this one.

Please try each of them to see if it works. If it does not work and you still need assistance, please submit official bug report to us via Prime Mover -> Contact Us -> Then click “Bug” as the contact us type. Fill in all the details required for us to troubleshoot and we will prioritize this one tomorrow morning (support time zone is GMT + 8).

Thanks for using Prime Mover plugin and for giving us 5-stars! Cheers 🙂

Hi Carlitos, it is nearly two weeks and have not heard from you. There is a new release – Prime Mover version 1.3.3 that includes several new bug fixes and improvements.

As an update, we have tried to reproduce what you have experienced with XAMPP Mac – however all is working fine on our end.

I’m closing this one as is now bit outdated. Feel free to open a new ticket with new and more details so we can see on our end.