Cloned Site Not Being Viewed In Cornerstone Builder

Support
#1

This happens all the time but not always completely in a site. Some pages do. Some pages dont. How do we make sure this never happens again?

#2

Hi There,

If you are using X you can use the plugin ALL IN ONE MIGRATION to perform the cloning.

Hope it helps

#3

we use managewp. its not an issue of cloning the site. its an issue of the cornerstone not playing nice on the new location.

#4

Hi there,

If your tool fails to modify or update serialized data in database, then it will always happen. Cornerstone is dependent to serialized data, hence, it’s always affected if that process fails. If you have other plugins that dependent to serialized data, then they will be affected too.

It’s not because it’s cornerstone, it’s because of your chosen tool. You can try BlogVault service, been using that and I don’t have issues with cornerstone editing after cloning or migration.

Thanks!

#5

Probably not the way to respond to a customer of your theme btw.

Is there no other way that this could occur at all? how can you explain why some sites merge half the pages correctly and half not then?

I’ll investigate the serialized data piece also. Managewp is easily one one of the most complete cloning tools available so I’m sure it can handle the migration correctly.

Thank you for your help

Eric

#6

Hi there,

Sorry if that sound’s off :slight_smile: but regardless of theme and plugins, the result will be the same, all serialized-data dependent features will be affected if the migration/cloning fails. That includes missing widgets, some corrupted form data, and so on. Serialization is not done by the theme or plugin (they have no capability to do that), it’s done by Wordpress itself ( and the tools too ). It’s like saving the array of data in the database, but it’s not possible since it’s array, so Wordpress will serialize it.

Plus, the tools being used may have a different effect too, which is why I said it’s due to the tools you’re using since it’s the only tool you’ve been using.

The only solution is to re-migrate or clone it. Maybe something fails in the middle of migration process, that happens :slight_smile:

Thanks!