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
WPRIMEpackage. 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
I just figured this out. Looks like it was some hickup in other plugins which modified .htaccess upon restoring with prime mover. I wiped it out to be the default WordPress and things look good now!