No content on published page after editing with Cornerstone

[meoptometry]

Hello,

I am playing catchup during this quarantine and finishing a migration from WP bakery to Cornerstone for each page of my site. I am basically recreating each page by building it in cornerstone. This worked well a couple years ago when I started the migration.

Just now, after publishing a page recreated with cornerstone, the page is empty/blank. The content appears in cornerstone editor and in the native WordPress editor, but the published site is empty.

I have cleared the cache on my site. I can provide credentials if needed.

Thank you,

MEO

EDIT:

Here is a comparison view of the versions:

[lely]

Hi MEO,

It might be blank if the content is corrupted or edited outside cornerstone.

If you can still access it, please try saving the page as template then create a new page and then try loading the save template.

If the issue persists, we can check to confirm if it is corrupted or not. Please share credentials and page URL inside a secure note.

[meoptometry]

I tried the above suggestions and unfortunately nothing changed. Please login via supplied credentials and troubleshoot.

Thank you,

MEO

[friech]

Hi MEO,

It seems your version of X and Cornerstone are not compatible, I’m not entirely sure though since both are way outdated.

Your version:
X 4.6.4 and Cornerstone 2.1.7 

Normally, in this case, I would just suggest reinstalling your Cornerstone to make sure it is compatible with X. You can simply do this by deactivating and deleting the Cornerstone, then navigate to X Addons and X will reinstall it automatically.

However, since you already updated your Wordpress to the latest version (5.4), then you need to follow that and update everything to the latest versions, including the child theme.

Please follow the guide I provided here.

Remember to clear all your caching features ( Plugins, Autoptimize, Better WordPress Minify, WP Super Cache, server-side, CDN, and browser’s cache) after updating so that the code from the latest release is always in use. This will help you to avoid any potential errors. It would be better if you can deactivate all your caching features at this stage

And remember do not edit your Cornerstone pages outside of Cornerstone.

Let us know how it goes,
Cheers!

[meoptometry]

Those versions of X and cornerstone are compatible as I’ve them for the past few years to edit/convert pages. The reason I have not updated them is when i tested on my staging site, I had difficulty viewing/converting the WP Bakery created pages to cornerstone, and I also believe my child theme customizations broke part of the sites. Could someone please take a look at them and see how they can be updated so the site doesn’t break if i update?

It seems that it is more likely a change in newer versions wordpress that are causing this issue.

Short of making those huge changes and likely breaking my site…is there anything else i can do incrementally? Ultimately the goal is to get everything up to date, but I’d like to that while minimizing disruption to the site.

MEO

[friech]

Hi MEO,

Unfortunately, you can not do this incrementally and avoid the issues since a lot of stuff changes from the versions you have, not only with the Theme and Plugins but to the Wordpress itself.

You need to set up a Clone/Staging Site and do the update there first. That way your live site won’t have downtime while you’re updating the site in staging.

How to Easily Create a Staging Site for WordPress (Step by Step)

Yeah, I saw that customizations on your child theme, you need to copy those on a newer child theme, you can download a fresh copy of child theme in the following link. Copy those customization one at a time making sure none of those cause an error on the site.

How to Download X or Pro Child Themes

Regretfully, there is no shortcut on this, you need to go through on each issue that may occur after updates.

Updating Your Themes and Plugins

Remember to clear all your caching features (plugin, server-side, CDN, and browser’s cache) after updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

Thanks,