Uh Oh! Content failed to save - help

Support
#1

Hi There,

I also seem to have the problem that my page is unable to save. The ‘‘Uh Oh’’ message is displayed whenever I try to save. However, sometimes it does save the page despite the message. I already looked through the different forum posts and followed that checklist with 9 bullet points to my best ability. Some of those points are too difficult for me to understand, I am not that advanced in website building. So I am hoping for some of your awesome skills.

  1. Ensure everything is up to date according to our version compatibility list here. Please follow the best practices when updating your theme and plugins. Click here for more information. > I did
  2. Go to X > Settings and click on the Clear Style Cache button. > Check!
  3. If you’re using a CDN, please clear the CDN’s cache and disable optimization services. > No idea what that is, I don’t think I am using it.
  4. Test for a plugin conflict. You can do this by deactivating all third-party plugins, and see if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time. > I did, the problem is still there.
  5. Remove custom CSS and Javascript from the options or Child Theme and test the case. This is something I don’t like to do. You guys created some custom Css and Java in the past for some issues I had regarding some forms and flipping cards. Removing this will create old problems I don’t want.
  6. Reset your htaccess file by renaming it to .htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button. I dont know where to find this
  7. Make sure that you’re running at least PHP v5.6.x or later to avoid any WordPress related incompatibility issues. If you’re not sure what your server configurations and settings are, install a plugin like WP-Serverinfo (https://wordpress.org/plugins/wp-serverinfo/) and check your server info by head over to Dashboard -> WP Serverinfo area.
  8. Check your PHP Max Execution Time and set it for 300 for optimal usage.
  9. Try increasing your PHP Memory limit. You can do this by editing your wp-config.php file which can be located under the root of your WordPress installation.
    Last 3 points are mumbo jumbo to me. I guess I am little out of my depth here. Hopefully, you can help me. Thanks in advance!
Summary
#2

Hi There,

Thanks for writing in!
As you have tried several troubleshooting processes and got no result. Also, I can confirm the issue on the site. The site is live and we can’t perform any troubleshooting process on your site. I am suggesting you few other points which may help you on the issue.

Incorrect setup of SSL. If you have an SSL certificate on your site. You should have the WordPress Site URL and Address URL settings set to HTTPS if you are loading the builder via HTTPS. This can be checked via your wp-admin > general > settings. If you aren’t using SSL you can ignore this step.

Caching. If you have a caching plugin activated or any form of server side caching please disable it to test for any possible conflicts. If you have server side caching or aren’t sure if you do, your host should be able to advise of this and disable it for testing purposes on your account.

Cloudflare. If you are using Cloudflare please disable this for testing purposes. Cloudflare by default enables an auto minfication function to compress the JS and CSS files of the theme. As the theme already serves minified files, re-minifying said files only causes to break the entire site.

Custom code syntax error. If you have a child theme, please enable the child theme and check if the issue still exists. If you have entered any custom JS or CSS into their respective editors. Please review the code for any syntax errors. A mis-placed semi-colon or a missing bracket will cause the issue you’re seeing.

If you could please try the above and if you still have the issue we’d be more than happy to assist.

#3

Hi There,

Thank you for the quick reply!

I have tried/checked the following:

  • Incorrect setup of SSL. > I have a SSL certificate in action. The https settings you suggest are in order.
  • Caching > I don’t have a caching plugin activated
  • Cloudflare> I do not use cloudflare
  • Custom code syntax error > I have a feeling that the problem lies in here. Like I mentioned before, you guys helped me out with some css code in the past, is it very possible that a missing bracket or such is creating this problem. Would you please be so kind to give it a quick glance, because I wouldn’t know where to start.

Thank you so much again

.x-navbar .desktop .x-nav > li > a:hover > span, .x-navbar .desktop .x-nav > li.x-active > a > span, .x-navbar .desktop .x-nav > li.current-menu-item > a > span {
box-shadow: none !important;
}
.x-navbar {
background-color: #ffffff;

}
.x-topbar {
background-color: #be1622;
}
.x-topbar .p-info {
color: #fff;
}
.x-topbar {
text-align: center;
}
.x-topbar .p-info {
float: none;
margin: 10px auto;
}

/* Hide social icons (optional) */
.x-topbar .x-social-global {
display: none;
}

@media ( min-width: 980px ) {
.x-navbar {
height: 100px;
}
}
@media (max-width: 979px) {
body .masthead-inline .x-btn-navbar {
color: #000;
background-color: #ffffff;
margin-top: 30px;
padding: 0.458em 0.625em;
box-shadow: inset 0 0 0 transparent, 0 1px 4px #000;
border-radius: 4px;
}

body .masthead-inline .x-btn-navbar:hover {
color: red;

}
@media (max-width: 979px){
.x-navbar-fixed-top, .x-navbar-fixed-left, .x-navbar-fixed-right {
position: fixed;
}
}
}
}

}
}
}
}

}
}
/*
// Buttons
*/

.x-btn {
font-weight: 700;
}

.x-btn.x-btn-alt,
.button.x-btn-alt,[type=“submit”].x-btn-alt {
border-color: #02aed6;
background-color: #e8bd5e;
box-shadow: 0 0.25em 0 0 #0b8ead, 0 4px 9px rgba(0, 0, 0, 0.75);
}

.x-btn.x-btn-alt:hover,
.button.x-btn-alt:hover,[type=“submit”].x-btn-alt:hover {
border-color: #0b8ead;
background-color: #e8bd5e;
box-shadow: 0 0.25em 0 0 #097690, 0 4px 9px rgba(0, 0, 0, 0.75);
}

/*
// Dropcap
*/

.x-dropcap {
background-color: #e8bd5e;
}

/*
// Headings - Dark section
*/

.dark-section h1,
.dark-section h2,
.dark-section h3,
.dark-section h4,
.dark-section h5,
.dark-section h6,
.dark-section h1 a,
.dark-section h2 a,
.dark-section h3 a,
.dark-section h4 a,
.dark-section h5 a,
.dark-section h6 a {
color: #fff;
}

.dark-section h1 a:hover,
.dark-section h2 a:hover,
.dark-section h3 a:hover,
.dark-section h4 a:hover,
.dark-section h5 a:hover,
.dark-section h6 a:hover {
color: #fff;
opacity: 0.65;
}

.x-card-outer .x-face-inner {
height: auto !important;
}

/*
// Sidebar
*/

.widget a {
color: #02aed6;
}

@media ( max-width: 767px ) {
.yikes-easy-mc-form label.label-inline {
float: none !important;
width: 100% !important;
padding-right: 0px !important;
}
.yikes-easy-mc-form .submit-button-inline-label {
width: 100% !important;
float: none !important;
}

/*
// Contact Form 7
*/

.wpcf7-form {
margin: 0;
padding-left: 20px;
padding-right: 20px;
}

#4

Hello @Vectorific_Design,

Thanks for updating the thread. :slight_smile:

I can confirm that Cornerstone is not loading properly. Sometimes it works without any issues but in my testing there have been some instances when Cornerstone was giving issues. To test see server configuration I installed WP Serverinfo plugin. Can you please make following changes:

  • Try increasing your PHP Memory limit. You can do this by editing your wp-config.php file which can be located under the root of your WordPress installation.

Add the following lines into that file.

define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

You can add it before the line
/*That's all, stop editing! Happy Blogging. */

  • Increase PHP Max Execution Time and set it for 300 for optimal usage.

If you are uncomfortable in doing above changes then you have the option to get in touch with hosting provider and ask them to make above changes.

Thanks.

#5

Hi @Prasant,

It worked! Cornerstone is saving without ‘‘oh oh’’ messages! Thank you sooo much, I am doing a happy dance :wink:

#6

Glad it’s okay now and you’re most welcome!

#7

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