Uh oh! Content failed to save issue

Like others, I’m having the same issue. I just updated X, Cornerstone and WP to the latest versions and now I cannot save any of my posts or pages.

I have followed all other posts but I cannot still get anything to save after I make a change to the page.

I can hit save and it goes through as long as nothing is changed on the page.

Please advise.

Hi @mvives,

Unfortunately, the username is not provided with the credentials for the privacy popup. Can you please check and get back to us with it.

Thanks

Sorry about that. I’ve added it to the secure note now.

Any updates on this? I updated the secure note with the username.

Hi @mvives,

I have checked your website and found that most of the pages are saving the modified data. Also it can create a new page successfully, and modify the content too. The pages are not saving the data, I would suggest you check by deleting the section one by one till the issue is fixed, and the last one you have deleted before the fix is the actual issue.

Hope it helps.
Thanks

Thanks @tristup.

I’m a little confused though. You initially mentioned that the pages are saving the modified data, but then a couple of sentences later, you mentioned the pages are NOT saving the data.

As for your recommendation, I’m a little unclear on what you’re mentioning to do. Are you saying I have to basically delete all sections of the page? Wouldn’t that defeat the purpose of modifying the page? It would basically mean I have to rebuild the page?

Hello @mvives,

Please go to Tools > Site Health > Status, make sure that there are no Performance Issues. You must resolve any of these issues. You may need further assistance from your hosting provider.

I have tested your site and when I save a page, there is a fatal error:

[Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2 
        
       POST https://yourdomain.com/wp-json/themeco/data/save?_locale=user 500
_ @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
f @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
b @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
b.method.r @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
t @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
y @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
t @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
P @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ app.6f62d0f.js:2
u @ app.6f62d0f.js:2
s @ app.6f62d0f.js:2
(anonymous) @ app.6f62d0f.js:2
(anonymous) @ app.6f62d0f.js:2
onClick @ app.6f62d0f.js:2
ki @ react-dom.min.js?ver=16.13.1:176
ji @ react-dom.min.js?ver=16.13.1:13
mi @ react-dom.min.js?ver=16.13.1:13
lf @ react-dom.min.js?ver=16.13.1:13
wi @ react-dom.min.js?ver=16.13.1:187
Kd @ react-dom.min.js?ver=16.13.1:32
pc @ react-dom.min.js?ver=16.13.1:32
Wf @ react-dom.min.js?ver=16.13.1:34
(anonymous) @ react-dom.min.js?ver=16.13.1:236
uf @ react-dom.min.js?ver=16.13.1:15
Qd @ react-dom.min.js?ver=16.13.1:42
sc @ react-dom.min.js?ver=16.13.1:41
unstable_runWithPriority @ react.min.js?ver=16.13.1:25
Da @ react-dom.min.js?ver=16.13.1:60
mk.Events.current @ react-dom.min.js?ver=16.13.1:236
Ei @ react-dom.min.js?ver=16.13.1:41
Show 16 more frames
app.6f62d0f.js:2 
        
       Failed to save. {code: 'internal_server_error', message: '<p>There has been a critical error on this website…arn more about troubleshooting WordPress.</a></p>', data: {…}, additional_errors: Array(0)}

It could also be from a plugin conflict or your Child theme custom functions. Please do the following:

Best Regards.

Thanks for the help.

I still can’t get things to work properly. Something is really off and I need more assistance.

I checked to see if it was a Theme issue. I used a default Wordpress theme, and after switching, I could make page changes and save properly.

When I switched back to the PRO theme (which I upgraded from X), the changes that I made and saved when using one of the default Wordpress themes was reverted. It returned back to what it was before, even though I saved it.

When I switch the theme back to the default Wordpress theme, the change is in place again! There seems to be some kind of theme issue.

All plugins have been deactivated and I still run into the issue. I cannot save anything with the PRO theme is activated.

Speaking of plugins, when PRO is activated, I see Cornerstone is installed as I can access it in the sidebar, but when I look under plugins, it shows Cornerstone is not even activated.

What’s going on here? I need some help getting my site functioning properly.

All I did was upgrade my original X theme and Cornerstone to the latest versions (after about 2-3 years), and now nothing is saving. As mentioned, I also upgraded from X to PRO.

Please advise.

Hello @mvives,

I will mention this again, please go to Tools > Site Health > Status, make sure that there are no Performance Issues. You need to update your PHP version to 7.4. You may need further assistance from your hosting provider to update your PHP version.

I checked your error.log file and this is what I found.

[27-Nov-2021 03:28:42 UTC] PHP Notice:  Undefined index: undefined in /home/688581.cloudwaysapps.com/kcqhdamzsc/public_html/wp-content/themes/pro/cornerstone/includes/classes/classic/elements/class-element-orchestrator.php on line 265
[27-Nov-2021 03:28:42 UTC] PHP Fatal error:  Uncaught Error: Call to a member function sanitize() on null in /home/688581.cloudwaysapps.com/kcqhdamzsc/public_html/wp-content/themes/pro/cornerstone/includes/classes/content/class-content.php:551
Stack trace:
#0 /home/688581.cloudwaysapps.com/kcqhdamzsc/public_html/wp-content/themes/pro/cornerstone/includes/classes/content/class-content.php(474): Cornerstone_Content->build_classic_element_output(Array, Array)
#1 /home/688581.cloudwaysapps.com/kcqhdamzsc/public_html/wp-content/themes/pro/cornerstone/includes/classes/content/class-content.php(562): Cornerstone_Content->build_element_output(Array, Array)
#2 /home/688581.cloudwaysapps.com/kcqhdamzsc/public_html/wp-content/themes/pro/cornerstone/includes/classes/content/class-content.php(474): Cornerstone_Content->build_classic_element_output(Array, Array)
#3 /home/688581.cloudwaysapps.com/kcqhdamzsc/public_html/wp-content/themes/pro/cornerstone/includes/classes/content/class-content.php(562):

I already reinstalled your Pro theme. The issue still exists. So I went ahead and created a test page. Surprisingly, I was able to save my changes. You can check out the test pages in the secure note below. You may also add sections to the test page and save your changes as well.

Best Regards.

Thanks @ruenel.

I uploaded the PHP version and all the other errors are irrelevant, e.g. deleting unused themes and plugins.

The site still does not save.

The pattern I noticed is that all old, existing pages do not save. However, all new pages created save. What’s going on here?

Hi @mvives,

It seems that it might be a problem with Classic elements you used on various pages. Besides you contact your Hosting Service provider as suggested by my colleague, try using the V2 elements in place of Classic elements and check if that resolves your problem.

Thanks