Existing page content not loading in Cornerstone page builder

[jmnly]

My site is hosted on wordpress.com

I’ve disabled all plugins except Kismet Anti-spam and Jetpack (can’t disable either of those), and the problem persists.

I don’t see any jetpack-related error messages in the dashboard.

I’ve already tried clearing caches.

I can see the shortcodes and content on the home page with another theme, and also in the pages themselves in the wordpress editor. However, when Pro is activated and I edit the page with Cornerstone, I only see the default cornerstone template with no content in it.

I can create new pages and the builder and front end load that content properly, but there seems to be a database disconnect between the existing page content and Pro/Cornerstone.

Wordpress version: 6.9.1
PHP version: 8.3.30

[jmnly]

Note: the original pages were built using shortcodes. At some point the theme was deleted. When I reinstalled the most-recent version of the theme (6.7.13), the Cornerstone Content Storage default was set to HTML. I switched back to shortcodes, but even though I click save and it says it’s been successful, if I reload the page, the Cornerstone Content Storage default is still set to HTML.

[ruenel]

Hey Jim,

We would love to log in and investigate your issue further. You can create a secure note in your next reply with the following info:
– Link to your site
– WP login URL
– WP username
– WP password
– WP Administrator Role
– Confirmation that we can access and make changes to your site

To know how to create a secure note, please check this out: How The Forum Works

Best Regards.

[christian]

Hey Jim,

The login doesn’t work. Please check.

[jmnly]

Hi @christian Strange. I just tested this login and it worked. The username associated with this account is: jmnly

[prakash_s]

Hello Jim,

I am another staff I tried to access the site dashboard, but the credentials are not working on my end. Please recheck and send us again.

Thanks

[ruenel]

Hey Jim,

We still cannot log in. I have sent a Login Email link. You can forward it to info@theme.co so we can try to log in again.

Thanks.

[jmnly]

I’m just seeing this. These links expire in 1 hr from generation, so if you generate another, I’ll be online for the next few hours to forward it.

[ruenel]

Hello Jim,

Nothing comes to our email. Invite info@theme.co as another user to your website instead?

Thanks.

[jmnly]

Sent invite just now. Thank you.

[ruenel]

Hey Jim,

Finally, we were able to log in. I have checked the page and I have loaded the page in Cornerstone:

I also see this in some of the pages:

Did you import these pages from a site built with Cornerstone? Please note that only pages originally created using Cornerstone can be edited with the Cornerstone Builder. Imported pages may only display shortcodes in the WordPress Editor or appear blank in the builder.

To ensure the pages can be edited in Cornerstone, you’ll need to migrate the site content properly. For detailed instructions, refer to our guides:

• https://theme.co/docs/pro5-to-pro6-migration
• https://theme.co/docs/content-storage

Do you still have access to the original site where these pages were created?

[jmnly]

This is the original site. It was built in Pro/Cornerstone. Something happened with wordpress hosting and the site had to be restored from a Jetpack backup. Now none of the original content loads in the builder or the front end. If the content is there, why can’t the theme/pagebuilder access it?

[ruenel]

Hello Jim,

If the pages were built with the shortcodes, chances are that the post metadata or cornerstone data is corrupted. Do you have a backup of this site? When was the theme deleted? Is that an older version before X theme 10.5 version?

Thanks.

[jmnly]

The site was built with shortcodes. I’m not sure what version of the theme was used. I don’t have a backup. Is there a way to install an older version of the theme to recover the pages?

[ruenel]

Hello Jim,

Once you have updated the database, you cannot revert it, even by using the old theme version; it will just return a fatal error. Could you not contact the hosting and revert it back prior to the time you made the update?

Thanks.