Codexonics

The fix for the customer order history issue (orders not appearing in customer accounts after migration) was already added in version Prime Mover 1.4.8 (current release – both free and pro versions). If the site is migrated with Prime Mover 1.4.7 – a hotfix script was added to fix this (which you have successfully run already). So it’s strange you still have this issue.

You can also try clearing your site cache (either using a plugin or built-in cache) provided by the host. And see if it clears. It’s possible that a host uses some persistent cache that is not cleared after migration.

If you are referring to a new/different issue – please help me understand and describe the issue in details by showing some screenshots or examples. Thanks! 🙂

As an update – we are going to release version 1.4.9 tomorrow. This includes the latest WC related migration fixes (including the beta fixes). For now -it would be best to hold off the migrations until version 1.4.9 is ready.

I suggest that once this is released – please re-migrate the original package using 1.4.9 and check if you still have the issue. Also double check if the source site does not have this issue – otherwise the issue will carry over to the target site.

Once the source site does not have the issue and you have the issue only after migration using version 1.4.9 – let’s continue the discussion on the opened ticket you have in our system. Please let me know and we will then request more details on the issue. thanks!

As an update – we’ve sent the link to download the PRO beta versions (including free beta versions) to your email since you already have a PRO account. This forum does not allow links to paid versions. I’m closing here so we can handle the rest on our official email support channel.

We tested the beta versions and it should resolved the issue on API keys table user assignment.

Thanks!

I’m closing this one and there is a new release today (Prime Mover 1.4.8). Please upgrade to this version to get the most up-to-date fixes. If you still need technical assistance – please open a new ticket with details. Thanks!

Here is the multisite compatible version of the hotfix script.

This works exactly like the standalone version except that it is multisite compatible. You need super admin rights to execute this and should be activated on the target subsite (not network activated) where you need to do the adjustment.

Make sure to backup your dB before doing this and enable WP debugging. We tested this one here and works great. Thanks!

Hi Dev – we have now the latest Prime Mover beta version that will automatically adjust these data during migration. We recommend using the beta version instead of the hotfix script.

To fix this in any of your sites (whether from standalone to multisite or vice versa) – please take note of the following procedures:

At origin (source site):

• Download the latest beta version here.
• Deactivate Prime Mover 1.4.7.
• Delete Prime Mover 1.4.7
• Install and activate Prime Mover 1.4.8-beta version
• Double check that the WC order – customer data is correct before migration to another site. This will ensure source site data is already correct.
• Generate export using Prime Mover.
• You should have now the updated exported package.

At target site:

• Download the latest beta version here.
• Deactivate Prime Mover 1.4.7.
• Delete Prime Mover 1.4.7
• Install and activate Prime Mover 1.4.8-beta version
• Restore the latest exported package using Prime Mover 1.4.8-beta
• Wait until the restoration is completed.
• Once completed – all WC orders data should be correctly adjusted.

This should fix issues relating to WC orders/customers after migration as long as the source site data is already correct.

We will be releasing an official Prime Mover 1.4.8 version hopefully this week. But for now – please use our latest beta version in your projects. For your update. Thanks!

Hello Rosanne,
Thank you for using Prime Mover! Since you migrate from blog ID: 2 of subsite to single site. Prime Mover will only copy all media files from /wp-content/uploads/sites/2/ to your target single site /wp-content/uploads/ directory. It won’t copy files from other blogs or main site because it does not belong to blog ID 2.

Probably this is a caching issue at your single site after migration. Are you using a cache plugin? Please try purging the cache plugin and see if it resolves the issue.

Are you also using a page builder plugin? If you are using a page builder- refer to it’s documentation on clearing the cache or assets. For example in Beaver Builder – this is the procedure to clear it. In Elementor this is found in Elementor > Tools > Regenerate CSS.

If the issue persist after clearing all cache and you still need technical assistance – please send us the following:

• Your source subsite URL.
• Your target site URL.
• Go to your subsite admin dashboard -> Go to Tools -> SiteHealth -> click “Info” click “Copy site info to clipboard” and paste it to text file and label it with filename “source.txt”.
• Go to your target single site admin dashboard -> Go to Tools -> SiteHealth -> click “Info” click “Copy site info to clipboard” and paste it to text file and label it with filename “target.txt”.
• Sample list of image URLs in your subsite where it does not exist in your target site after migration
• [optional but recommended] – please share us the link to download WPRIME package (you can via Gdrive) that you use to migrate to single site. We will use this to reproduce the missing images issue in our local

Please send us all info via our contact form or via admin dashboard -> Prime Mover -> Contact Us. Thanks!

Hi dev, that’s weird. But if this cannot be deleted – it means WordPress still see this as active plugin on dB even though it appears already deactivated. WordPress stores active plugins information in WP options db table as active_plugins option.

Searching for this error on the Internet – seems not be migration related but caching related. WordPress might be getting cached value on active_plugins where that plugin is still active (despite already deactivated). This prevent the plugin to be deleted since it’s still active.

Check if your site uses caching. Purge cache whether its using a caching plugin or if caching is provided built-in by host – purge or clear it also.

Or you can temporarily deactivate all caching solutions first (including the ones provided by hosts if possible) before deleting plugin. This will ensure that the active_plugins info used by WordPress is updated and not cached.

The following links could help you resolve this issue:

Fix Error: You cannot delete a plugin while it is active on the main site

How to fix “You cannot delete a plugin while it is active on the main site” error?

This should resolve this deleting plugin issue. Thanks!