This is just feedback. In the past year or so Kadence becomes the default theme when the transfer is complete. AND sometimes another them can’t be activated Unless Kadence is deleted via SFTP. This should not happen.
]]>I tried doing a direct migration, following all the correct instructions.
Migration was complete but the new site says “There has been a critical error on this website.”
Is this because it still says the custom nexcess url and not the primary source url?
]]>Just tried to migrate two sites and ran into this error:
“Unable to access wpconfig file. Please check if WordPress is installed on the destination address. Also, check if you have permission to access the folder.”
Nexcess support said there were some errors and to try https://www.ads-software.com/plugins/migrate-guru/ . Which did work…
Whats the difference and why did that one work and not LiquidWeb’s own plugin?
]]>I noticed that after using this plugin the Customzer / Appearance / Menus Menu item CSS classes did not get copied over to the migrated website. Just an FYI. Please fix.
]]>This plugin works great but it would be nice if it didn’t leave behind extra database tables. Would love to hear if you are working on a solution
]]>Love this plugin as it allows us to easily migrate from our staging to production environments.
It would be so much more flexible with a start-and-completed webhook setting instead of email though, as email is so 1990’s.
]]>When going to the “Migrate My Site to LiquidWeb” options page in WordPress, the tutorial video at the top of the page shows this video:
(How to Take Your Site Live on Liquid Web’s Managed WordPress)
Since we’re taling about “Migrating”, it should instead be…
How to Migrate Your WordPress Site to Liquid Web’s Managed WordPress
Suggest to fix this video embed to the correct link.
]]>First off – great plugin and service. We’ve run into an issue though where custom tables generated by a plugin are not being migrated over correctly. The plugin is WP-Cerber (https://www.ads-software.com/plugins/wp-cerber/) which creates new custom tables in the database (non-pefixed) to store it’s data. Unfortunately this migration plugin doesn’t capture these custom tables correctly, requiring us to manually create the tables and insert their data post-migration.
]]>