Codexonics

Thank you for using Prime Mover in your migration projects. We are happy to know that it saves you hours in your work. Thanks again for rating us 5 stars. Cheers 🙂

Thank you for sharing your experience with Prime Mover. We are glad to hear about its reliability and speed in completing migrations. Cheers!

Hello, thanks for using Prime Mover! The issue looks weird as it happens only on blog ID 8 but other sites unaffected. And it works if admin is logged into but not a public user.

Would it be possible for you to do these troubleshooting steps and provide us the data?

• Make sure Prime Mover is deactivated.
• Login to blog ID 8 subsite -> WordPress admin.
• Go to Tools -> SiteHealth -> Info.
• Click “Copy site info” to clipboard.
• Paste that to text editor and save it as blogid8-siteinfo.txt.
• Enable WordPress debugging and add this to your wp-config.php:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

• Make sure no debug.log is generated in /wp-content/
• Login to Network admin.
• Quickly network activate Prime Mover plugin.
• On another browser (logged-out) – visit the subsite (blog ID 8) as a public user to confirm the issue.
• Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. This will download your site info details including your Prime Mover settings data. This is your site information log.
• Once the site information is downloaded – network deactivate Prime Mover.
• Zip all three important logs (blogid8-siteinfo.txt, site information log generated, debug.log (if its generated in wp-content directory)
• Please send us the link to download this zip (containing these logs) to our support contact page. Please don’t share it here because it contains sensitive information.
• You can now safely disable WordPress debugging by removing the above code in your wp-config.php. And delete the debug.log in /wp-content/ directory.

Once you’ve send us the logs – please give us time to check and reproduce this issue. It’s possible there could be some plugin or theme conflicts that is causing this. Or it could just be a caching issue. Thanks!

• This reply was modified 3 years, 2 months ago by Codexonics.

Thanks for the update. Glad to see the issue fixed. Closing 🙂 Cheers.

Hi Chris,

Thanks again for this tip. We tried to test this on a legacy multisite server as follows:

• Activate Astra theme in subsite.
• Create a demo site using Starter Templates.
• Add test images with all legacy multisite image URL combinations.
• Check if site images and media libraries are set.
• Migrate that subsite to single site.

Results: It was able to migrate images from the multisite subsite (blog ID 895) in the following paths (using legacy multisite URLs) FROM :

https://legacymultisite.tld/my-subsite/files/2023/02/test3-1024x585.jpg

https://legacymultisite.tld/my-subsite/files/2023/02/test2.jpg

https://legacymultisite.tld/my-subsite/wp-content/blogs.dir/895/files/2023/02/test4.jpeg

https://legacymultisite.tld/wp-content/blogs.dir/895/files/2023/02/test5.jpg

TO single site:

https://singlesite.tld/wp-content/uploads/2023/02/test3-1024x585.jpg

https://singlesite.tld/wp-content/uploads/2023/02/test2.jpg

https://singlesite.tld/wp-content/uploads/2023/02/test4.jpeg

https://singlesite.tld/wp-content/uploads/2023/02/test5.jpg

The images were migrated successfully (without manual copying of images) from the multisite to single site (using Prime Mover complete export package).

In your case – you don’t see any images after migrating from legacy multisite to single site. I suspect your old legacy multisite might be using a different or highly customized configuration that is not yet tested with Prime Mover.

If you could provide us your legacy multisite site information using the procedure below, that would be helpful so we could reproduce your setup:

• Login to your source legacy multisite.
• Go to Network admin.
• Go to Prime Mover -> Advanced.
• Scroll down to the bottom.
• Click “Export site info” button. Zip this one.
• Login to your subsite admin dashboard. (this is the subsite that you have exported)
• Go to Tools -> Site Health -> Click “Info” tab.
• Click “Copy site info to clipboard“.
• Paste this to text editor (e.g.) , save and then zip also.
• Send both log result to tech support via our official contact form. Please don’t paste here because that log contains sensitive information.

We will analyze your site info and how it could result to no images being restored at single site.

For now – your suggested workaround should work for affected sites, closing.

Hello Chris,

Thank you for using the plugin and for reporting this issue. We are unable to reproduce this issue on our end. Would it be possible for you to share the WPRIME package that is exported from the multisite?

If this is OK for you – please upload this package to Google Drive and share us the link to download this via official contact form. This would greatly help us understand why it won’t migrate images and there are blank entries in the media library.

If you cannot share package, any debugging logs would help. You can check this tutorial on what logs to provide to tech support. It would be great if you could provide logs from the export process and the restore process. Please send all logs to our contact form because these contain sensitive information.

Cheers,

Emerson

Hi Denis,

Thank you for using Prime Mover! Based on your inputs – it looks like this is a front end caching issue. If it displays vanilla WP install unless you are logged-in as admin – it means that the some form of front end caching is enforced.

You need to clear or purge this cache so that it will be updated with your newly migrated site. You can check with your hosting documentation or support if they use some form of built-in caching, etc. or if you are using some caching plugins.

We have an official post migration troubleshooting guide which will guide you through each steps in case you see some visual glitches after migration. This should help you find the causes and some workarounds to fix it.

In case the troubleshooting guide helps in solving the issue – please mark this ticket as resolved. Otherwise – if you still need assistance, please provide as the following:

• Link to download the WPRIME package. Please share us the link to download – you can upload this to Google Drive, etc. We will use this package to reproduce the issue .
• Debugging, site information and migration logs – please generate it using this tutorial. We will use these logs to analyze if there is something wrong with the migration or check if there is an issue with your website configuration.
• URL of the source and target site, so we will know how the source site looks like and how it looks like in the target site.

Please send all the above details via the technical support contact form. Please share these information only with the support and don’t post publicly. Thank you!

Cheers,

Emerson

Thank you for updating the review to 5 stars ! It was nice to know that this file was indeed from your theme/add on version. Cheers 🙂