This page may contain affiliate links. Please read my disclaimer for more information.

WordPress Editor Updating Failed [SOLVED]

In this article I’ll show you some possible fixes for the error “Updating Failed” in the WordPress page and post editor. This issue can be caused by different situations, and I am keeping this post updated as we discover more causes.

At the time of this update, we have identified a handful of different causes, and have tried to provide the best solutions.

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.

jQuery Migration Helper

This solution is not a fix. It is a work around that will get you back up and running. You should still work to identify and resolve the underlining issue. If you need help with that, feel free to contact us or WP Buffs.

As of the WordPress 5.5 update the jquary-migrate tool is disabled by default. As a result, themes and plugins that are not being updated to me the current coding standards will experience issues.

As a result the WordPress team published a plugin to help patch the issue. All you have to do is install it and activate it. There are no settings or configurations.

You can install this plugin from the WP Admin. From in your dashboard go to Plugins => Add New. Then search for Enable jQuery Migrate Helper and activate it.

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

Unlicensed Premium Plugin Updates

If you had someone build your website for you, or you purchased your theme from a site like Theme Forest (not recommended), you are possibly using premium plugins that are not registered, which means you are not getting update notifications and without a license youโ€™re unable to update the plugins.

These plugins could be causing the conflict and to resolve the issue my need to be updated.

This is what you might see for a premium plugin that needs an update:

In some cases you my not even see the update notice. If that is the case you will need to do one of two things.

  1. If you bought a theme from Theme Forest.

The developer will often have instructions in the original files on how to update these premium plugins. They likely have purchased a license and then provide an updated file for those that have purchased their work.

  1. Built for you.

If there is no update notification, you are going to need to do a little research.

First youโ€™ll need to determine what version you have installed, see image below

Once you know your version, youโ€™ll need to find the developers version logs, change logs, or update logs. I have found that they call them different things.

But whatever they call it, you will want to look at these logs to get the info you need to determine the current version of the plugin.

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 Service

Want us to fix it for you!? If you don’t want to waste time with these tech issues, we’re happy to do-it-for-you! You can feel confident knowing you’ve got an expert fixing it for you!

Have any questions, feel free to leave a comment or use our live chat, or comments below.

30 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

      • I have tried these things and using a
        cloudflare ssl. Please guide as unable to update pages . Getting the message “Updating failed.You are probably offline

        • If youโ€™re using cloud flare you likely have the caching enables as well. Have you tried disabling the caching and purging the cache?

      • 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

    • 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.

  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.

  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


  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.

  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


Leave a Comment

Join The Mantis Report

Get weekly WordPress news, resources, tutorials, and other tips from our experts.

This field is for validation purposes and should be left unchanged.

Skip to content