WordPress Editor Updating Failed [SOLVED]

THIS POST MAY CONTAIN AFFILIATE LINKS. PLEASE READ MY DISCLAIMER FOR MORE INFO.

In this article I’ll show you how to fix the error “Updating Failed” in the WordPress page and post editor. In most cases this is a very simple fix.

Done-For-You Option

Want us to fix this and other website issues for you!? If you’d rather not take the time to mess with these technical issues, We’re happy to do-it-for-you! You can feel confident knowing you’ve got an on-call developer when you hire us to take care of your website!

The Why

This error has become quite common with the recent release of WordPress 5.0 which included the new Gutenberg editor.

The WordPress support team at WP Mantis has probably resolved this issue 100 times since the update.

So far in most cases this issue was caused by a conflict in the new WP Gutenberg editor and a 3rd party page builder/theme.

Because this was so common, we did some independent testing. And so far the only page builder we have not seen this issue with is Elementor.

These page builders have had the issue:

  • WP Bakery
  • Beaver Builder
  • Divi

How To Fix It – A Couple Tricks

This first fix is not ideal if you like using Gutenberg, but if you are using a 3rd party page builder, you can use this option without issue.

Most 3rd party page builders (as listed above) do not use the Gutenberg editor so disabling it isn’t going to effect your site.

DisableΒ the Gutenberg Editor:

  1. Install the Classic Editor plugin
  2. Activate the Plugin
  3. Done!


I have also seen just the activation and deactivation of this plugin work to correct the issue.

Toggle Permalinks

This is another simple trick you can try if you prefer to not use the classic editor plugin.

You can try two different approaches this fix.

  1. Simply go to permalinks in the Settings and click save!

If that doesn’t resolve the issue, then try this.

  1. Go to Permalinks in Settings
  2. Select “Plain” (remember you current settings)
  3. Click Save
  4. Switch back to your previous setting (ideally “Post Name”)
  5. Click Save

If Those Fixes didn’t Work (techie stuff)

It’s time to do the typical WordPress troubleshooting.

I recommend you use the Site Health Check plugin which will enable you to easily troubleshoot issues without affecting the live version of your site and what visitors are seeing.

Once you have it installed and activated follow this screenshot to find the Site Health tools:

After clicking on “Site Health”, the first screen, “Status” will show you any critical issues. Which may point you to the underlining issue.

If you notice issues with Rest API, or if a specific plugin is listed, I’d recommend starting there.

Use the steps below to use this plugin to help you troubleshoot plugins and theme issues.

You can also try activating debug mode to see if that helps you identify the cause. Here is a quick video to show you how to do that. Note this does require FTP access.

define('WP_DEBUG', true);

To turn off debug mode you can remove the code or simply change “true” to “false”

define('WP_DEBUG', false);

Still Having issues?

Done-For-You Option

Want us to fix this and other website issues for you!? If you’d rather not take the time to mess with these technical issues, We’re happy to do-it-for-you! You can feel confident knowing you’ve got an on-call developer when you hire us to take care of your website!

Have any questions, feel free to leave a comment or use our live chat =>

Advertisements

23 thoughts on “WordPress Editor Updating Failed [SOLVED]”

    • Well Ron, this is a solution! However, if you would like one that doesn’t require the use of the Classic Editor plugin you should contact your theme/plugin provider for whichever page builder solution you use and ask if they have a more permanent solution.

      Be sure to let them know that you don’t want a “lousy work-round” since they are likely to suggest activating the Classic Editor plugin.

      Please don’t use the comments of this blog again and please avoid coming here if you want to be a jerk!

      – Chris

      Reply
      • Hey Tim sorry to hear that! Did you backup your site before implementing my suggestion?

        Always a good idea to do backups before troubleshooting or testing fixes.

        Did deactivating the plugin not take things back to the way they were?

        – Chris

        Reply
    • Changing the site URL (added www.) also fixed my problem. The issue is that my multisite server no longer forwards non www. requests to my particular site. So I can edit posts when I have the www. and then remove it after I have finished editing. This is an annoying workaround and will hopefully find the final solution.

      Reply
  1. The problem is with the Permalink, Changing the permalink is fixing the issue. (I think that is what Heather was talking about in the previous comment)

    But not for me, since the permalink that is causing the problem is the one I need to have. And I need to have the new editor, not the old one so I am back to square one.

    Reply
  2. Thanks Chris for the insight

    Your info led me to find a plugin “Disable Gutenberg” and installed it. This removed all the Gutenberg stuff. Worked for me, but lost the additional tools Gutenberg provides. I reactivated Gutenberg and the problem came back so I disabled it completely for now until WordPress fixes the problem

    Thanks

    Reply
  3. In my case, enabling the Apache2 rewrite module fixed the problem, allowing me to continue using the block editor and post name style permalinks.

    Reply
  4. Thanks a lot, I was tired trying everything from updating PHP to deactivating plugin but nothing work,
    Thank God, I came to this visit and was able to get the solution for post not updating on WordPress.
    Thanks installing the classic editor solved my problem

    Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.