Content Broken in PRO after migration

I created a staging site from a fresh wordpress install and used PRO to build a whole new site for our company.

When the time came to take it live I followed these instructions: https://askwpgirl.com/move-wordpress-subdirectory-root/

The staging site is http but the live site is https.

It was successful at first. After I copied the files over into the root the entire site looked like it loaded fine. The problem is those instructions have you do a few more steps including using the Velvet Blues Update URLs plugin. When I used that plugin per the instructions, all of our pages created with PRO stopped loading with the exception of the home page. When I go to edit one of the pages I see shortcodes instead of the big “Edit With PRO” button. When I click to edit with pro there are no sections or any content.

When it broke I restored the old site to the root and re-migrated the new site back to staging but the problem persists on the staging site. This leads me to believe that something changed in the staging site’s database.

Steps I have taken so far:

  • regenerate the htaccess page
  • checked the console (no errors)
  • deactivated all plugins
  • used Better Search Replace to ensure staging site was fully pushed back to http from https when I reverted.

Curiously, one page remained full intact and working through all of it. It was built with PRO and is still completely editable.

Is the any way I can recover the 60+ pages we built with PRO?

Hi Greg,

Thanks for writing in! Please follow our migration guide here (https://theme.co/apex/forum/t/cornerstone-content-builder-migration/126) and that should help you to migrate your site properly.

After the migration, make sure to clear full cache before testing. You can refer to the following guide here (https://www.wpbeginner.com/beginners-guide/how-to-clear-your-cache-in-wordpress/).

Hope that helps.

Thank you for the suggestion but how is that supposed to help with issue I am having with all the content I built not showing?

Also - this is not a caching error, nor am I using cornerstone…

@Prasant can you or someone take a look at this beyond just reading the title? My theory is that my pages may have had the post meta data deleted or messed up during migration.

Either way I need to know what I did wrong to make sure we don’t have this issue on the next migration.

Hi Greg,

Your theory is more likely to be true, did you able to restore your staging back to the working state (before migration attempt), if not please do so, that is the first step to restore your staging site, try contacting your hosting they might have a backup of your site.

Then redo the migration process, this time keep a backup of your database first before anything to play safe.

The moving of files from subfolder to root directory is straight forward, but the updating of the database is a bit tricky (well not really if you did this couple of times). Just follow the migration guide provided here.

Keep these steps in mind:

the link is relative //yournewsite.com and not http://yournewsite.com

Don’t worry about your https yet.

And this step, I think this is the one that you miss.

you should enter the path to where your new site is. For example /home/sites/yournewsite.com/public_html/, this should be the root of your new install, so if your site was in subdirectory it might be /home/sites/yournewsite.com/public_html/subdir/

Please read the whole guide I link above.

If you get mixed content issue after migration (http vs https), just follow the solution provided here.

Let us know how it goes,
Cheers!

1 Like

Yes! I’m sure that last step with changing the site path is what I missed. I will give it another try with your instructions and report back.

Thanks for your help!

Let us know how it goes!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.