Can't save page in Cornerstone after clicking "Edit with WordPress"

I have one specific page that will no longer save in Cornerstone after I clicked “Edit with WordPress” on the normal WordPress editor page:

Now on the WordPress editor page, I can’t see the normal “Edit with Cornerstone” option, instead it just shows shortcodes in the blocks editor.
shortcodes

I am seeing this error when I try to save the page now in Cornerstone:
saveerror

No other pages are having this issue and this page only started having this issue after I clicked “Edit with WordPress”.

I tried deactivating plugins but that did not fix. What is causing this and how can I fix it?

I sent login information in a secure note.

Thank you!

Hello @Hyperbits,

Thanks for writing in! Please be advised that you can only edit the pages built with the Cornerstone builder. Switching to the WordPress editor and going to the Cornerstone builder may corrupt cornerstone data which will then lead to an issue or conflicts. You may even not able to edit the page anymore. May I suggest that you revert to the old content of the page by utilizing the Revisions feature of WordPress.

Best Regards.

Hi @ruenel, I did revert back to a previous revision of the page from 5 months earlier and while the wordpress editor page is back to what it used to look like:

The page still will not save in Cornerstone, I am getting the same error:
saveerror

@ruenel, I just tested some other pages and it appears that there are some others that also can’t be saved in Cornerstone now. I updated the secure note with an example of another page that is doing this. On this new page I did not click the “Edit with WordPress” button but it is giving me the same error on trying to save that I was seeing for the previous page.

Hey @Hyperbits,

I am using MS Edge and Brave browsers. I cannot replicate the issue on my end. I can edit the mentioned pages loaded in Cornerstone without any issues.

  • See the screenshots in the secure note below.

I would recommend that you check out your browser extensions as it may have cause some conflicts. Try the mentioned browsers too.

Best Regards.

Hi @ruenel, I just tested on Firefox, Brave, Chrome and Edge after disabling my browser extensions and I am still getting the same error. I am getting a specific error in the console when I try to save in any of these browsers. You can see the error in this screenshot

Hi @Hyperbits,

I am able to replicate the issue while saving the content on a test page. After further investigation, I found that you are using the Classic element, which might be the reason for your problem. I would suggest you use the V2 element, i.e. use the Section, Row, and Column elements instead of the Classic element which is already deprecated.
If that does not help, please copy your live site to a staging server so we can troubleshoot freely without breaking your live site.
And give us access in the secure note including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.

Thanks

Hi @tristup,

Thank you for taking a look at this. I did create a duplicate page and deleted all of the classic elements and the page still would not save. I updated my secure note with login information for our staging site if you can login and test there.

Thank you!

Hi @Hyperbits,

I have saved the content Start to Finish w/ Hyperbits page as a template and added it to a test page. While saving it shows the error that you reported, by deleting the sections one by one I found that some of the elements are the reason behind your problem. As an example. in the FAQ section Second Column is the reason, in Pricing Official section Option Container is having the problem. It seems that the problem is with some of the content, I would suggest you delete sections one by one and check which are the reason behind your issue.
Please remember that content-related issues are not in the scope of Theme Support.

Hope it helps.
Thanks

Hi @tristup,

There might be classic elements in the Start to Finish w/ Hyperbits page/template that you copied, however, I created a duplicate of the page with the original issue and deleted every single classic element from the page so I am only using the V2 elements, but despite this I still cannot save. I updated my original secure note with a link to this duplicate page so you can see the issue. You will see that this page has classic elements on it because, despite deleting all of the classic elements in Cornerstone, I cannot save the page because of the error.

I am confused because if I am using only V2 elements now in the most up-to-date version of Cornerstone, why can I not save as expected? If there are only V2 elements left on this page, why would those be causing an issue saving with Cornerstone? Shouldn’t these be the only building blocks necessary for a properly functioning version of X theme?

Thank you

Many of our pages are now having this issue. Also, there does not seem to be any rhyme or reason to which elements allow the page to be saved. I created another duplicate draft of the original page and deleted everything except for this basic structure with no classic elements and the page still will not save:
structure

And one last note to add to this is that if I delete this “Blog” section but add back in other sections, it still will not save. However, if I keep the “blog” section but delete other sections, sometimes it will save with the “Blog” section in place, so that is why I say there does not seem to be a rhyme or reason for which sections allow the page to save and which do not.

Hi @Hyperbits,

I have updated the Pro to its latest version and activated the parent theme in your staging server. Now, all the pages are saved correctly except for the page mentioned in my last comment. Can you please check it once again and let us know for further investigation.

Thanks

Hi @ Tristup,

I went in and tried to edit the home page on the staging server again with the parent theme enabled, all plugins deactivated again and I went through and deleted all classic elements one more time and I am still getting the same error and am unable to save as shown below:

In the secure note this is the page at the “staging site url”.

It appears that it is the same error each time, is there a reason that Cornerstone throws this error specifically?

As this is now affecting multiple important pages on our site and we cannot make updates to these pages, we need to figure out a solution to this issue as soon as possible.

Thank you.

Hello @Hyperbits,

I tried to access your staging server website dashboard but the given login details are not working on my end. Please recheck and send us again.

Thanks

Hi @prakash_s,

Sorry about that. I just updated my original secure note with the login information.

Thanks

We tried editing the page Start to Finish w/ Syence , and it only saves correctly when we remove the Pricing: Enrollment Closed section. When we add the section back, we get the same error. This seems to be an invisible section – we can’t actually see it on the page. Have you tried recreating this section from scratch? Did you add the same section across the site?

Hi @Ismael, thank you for looking into it.

The Start to Finish w/ Syence is not the only page this error is happening on when trying to save with Cornerstone and most of the pages that are having this issue do not have the “Pricing: Enrollment Closed” section present (whether visible or invisible). For example, the first page I wrote in about does not have this section included and even if I delete all of the Classic elements from the page, I get the same error when trying to save. Here is that page on staging again:
https://wordpress-187232-598642.cloudwaysapps.com/cornerstone/edit/10725

What clues does this error give you about why Cornerstone is not able to save?

I would think this would be the most helpful because it appears to be the same error each time.

Thank you.

Thank you for the info.

We tried removing the suspected sections but the issue remains. Deleting all the classic elements on the homepage didn’t work either. Please provide the FTP details in the private field so we can enable the error logs and investigate the issue further.

Kind regards.

Hi @Ismael, thank you. I have updated the secure note with FTP details.