Uh oh failed to save - again

Support
#1

Hi

At www.uggerhoej.dk we are running latest WP and CS and when trying to save, we now get the famous ’ Uh oh failed to save’. Suggestions?

Thanks!

#2

Hello @mediegruppen,

Thanks for writing to us.

It seems that there might be an issue of plugin conflict. I would suggest you troubleshoot with a few of the common issues before we investigate your settings.

  1. Testing For Theme Related Issue
  2. Testing For Plugin Conflict
  3. Theme Update
  4. Child Theme
  5. Css/Js Customization
  6. Increasing Php Memory Limit
  7. Disabling Cache
  8. Disabling Cdn
  9. Permalinks
  10. Version Compatibility

If none of those work, It would be best if you could copying your live website to your staging area. and send your details in a secure note so that we can investigate your setting without breaking your live site. Please provide the following details

  • WordPress Login URL
  • Admin level username and password
  • FTP Details

You can find the Secure Note button at the bottom of your posts

secure-note
secure-note1040×250 15.3 KB

Thanks

#3

Hi there

Thanks. I’ve been through the process and I can confirm, that the widely used ‘Yoast SEO Premium’ is creating the conflict. Here are some info for you to debug on:

WP: 5.8
Yoast SEO Premium: 11.9
Theme X: 9.0.8
Cornerstone: 6.0.8

Please let me know, what you think.

Thanks!

#4

Hi @mediegruppen,

Glad that you are able to find the exact reason behind your issue. As this is a 3rd Party plugin issue, I would suggest you contact the Plugin Author on this and let us know the feedback from them.

Thanks

#5

Hi

Let me understand this correct: We have a plugin conflict between Cornerstone and another big plugin, Yoast, and you’re not interested in trying to solve this? Please let me know, so I can advice my client on usage of CS in the future, thanks.

#6

Hi @mediegruppen,

Sorry for the confussion. It has been found that the issue is only with the 3rd Party plugin and i.e. Yoast, for which we don’t have any control over the code. That is why I suggested you contact the Plugin Author and let us know their feedback on this.

Thanks

#7

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