WordPress plugin update failed

New Page

The WordPress add-in update has fallen: cómo solutionarlo

Posted on August 4, 202August 15, 2020 by WPDT Personal

The WordPress add-in update has fallen: cómo solutionarlo WordPress plugin update failure: how to fix it

WordPress powered by 37% of the Internet . The appeal to many is the control it gives the user and how easy the design process is . WordPress can offer this feature through plugins. Plugins need to be updated, however, a common problem that many users experience is finding out that their WordPress plugin update has failed.

Whether it’s for your business, brand, or hobby, as a WordPress user you need to make sure your website is up to date. This is not only for operational and design reasons, but also for security. An outdated plugin is a liability for your WordPress site.

Si encuentra un error durante la actualización que indica que la actualización de su complemento de WordPress falló, ¿qué puede hacer?

Fortunately, there are fixes for this problem. Let’s now examine the different solutions in this article created by our team at wpDataTables.

DISCLAIMER: It is always a good idea to make a backup of your entire WordPress site before attempting any changes to your site! Search “WordPress site backup” in your search engine for a step by step guide on how to do this.

Échec de la mise à jour du plugin WordPress : Solutions

Définissez un WP_TEMP_DIR dans votre fichier Wp-Config.Php :

plugin failure plugin failure

Si la mise à jour de votre plugin WordPress a échoué, vous pouvez voir l’un de ces messages d’erreur :

“Échec du téléchargement”

 “An error occurred while updating (plugin name).”

 “Download failed. The destination directory for the file stream does not exist or is not writable.

In these cases, follow these steps to resolve the issue  :

wp-config wp-config

  • Open your wp-config.php file with the cPanel File Manager code editor
  • You should see this code near the top of the file:

*@WordPress package */ //**MySQL settings – You can get this information from our host**// /**The database name for WordPress*/ define(‘DB_NAME’, ‘demo_wpdt’) ;

  • Place this definition of defin e (‘WP_TEMP_DIR’, ABSPATH . ‘wp-content/’); between the lines mentioned above, it will look like this when finished:

*@WordPress package */ Define(‘WP_TEMP_DIR’, ABSPATH . ‘wp-content/’); //**MySQL Settings – You can get this information from our host**// /**The database name for WordPress*/ define(‘DB_NAME’, ‘demo_wpdt’);

  • Now save your wp-config.php file.

Try updating again. If the same error appears, check the file permission for your wp-content folder and make sure it is set to 755 so the server can write to it.

Change file and directory permissions

Définissez l’autorisation de fichier sur 755

ensemble-755 ensemble-755

Alternatively, the problem might not be due to the plugin itself, but rather the file permission on your server. This can lead to WordPress not being able to access the plugin folders and update the plugin correctly, leading to a plugin update failure.

Before suggesting some solutions, this is what your default permissions should already be set to:

  • 755 for all folders and sub-folders
  •  644 for all files

Understanding File Permissions

permissions permissions

These numbers control who is able to access, change, or manipulate files. These three classes of permission are known as Owner, Group, and Others.

To understand this clearly, it’s important to know that there are three types of permission that can be assigned to these classes. These are read, write, and execute. These are normally shown as:

  • r” if reading is permitted, “-” if it is not 
  • “w” if writing is permitted, “-” if it is not 
  • “x” if the execution is permitted, “-” if it is not

Numerically this translates to:

  • OWNER has permission “7” or “rwx” 
  • GROUP has permission “5” or “r-x” 
  • OTHERS has permission “5” or “r-x”

By using this logic, the file permission 755 reads as rwxr-xr-x. The first three letters show the permission for OWNER. The middle three letters show the permission for GROUP. The last three letters show the permission for OTHERS.

Change the Upgrade Directory to 777

ensemble777-1 ensemble777-1

Another possible solution for your WordPress plugin update failing is to change the permission of the field directory to 777.

This is similar to the previous suggestion, except that 777 allows your upgrade directory to read, write, and execute without restrictions.

To do this, use either your file manager in cPanel or your FTP client.

Find your upgrade directory in WordPress at wp-content/upgrade. Change the permission to 777 and update the plugin.

It’s important to remember to change your permission back to 644 once the process is complete.

If this doesn’t work, there is a work-around; delete upgrade directory and recreate it.

Simply delete the upgrade directory from the web-based file manager provided by the host or via FTP client. Once this is done, recreate it. Make sure the permission is set to 644.

Then try again to update the WordPress plugin.

Fixing a Stalled Update

maintenance maintenance

Often when updating your WordPress site, a notice may appear for the public stating that the site is briefly “unavailable due to maintenance”. Usually, this will disappear once the update or installation is complete. However, there are times when this notice does not disappear.

This may be due to your update stalling, leaving your website inaccessible from both the public end and the admin end.

Simply FTP into your website (or use your web host’s file manager) and navigate to the folder where WordPress is installed. Look for a file called “.maintenance” (notice the “.” in the file name) and delete it from the server.

Now refresh your browser, you should be able to access everything once again.

Make sure that everything is working properly. Then try again to run the update process.

Lack of Hard Disk Space

hard drive1 svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww

While it is rare for most websites, in some cases you may have run out of web hard disk space, which could lead to your WordPress plugin update failing.

Fortunately, there are solutions.

If you receive any of the error messages:

  • Could not remove the old plugin
  • Plugin upgrade failed at unpacking the update
  • Could not copy file /public_html/wp-content/xyz

It’s time to clear out the web hard disk. Do some maintenance, delete old files, and free some space. Try the WordPress plugin update again and it will update properly if this was the problem.

Other Fixes

disable svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww

If you have tried all of the above-mentioned fixes and are still encountering issues, there are a few alternative solutions to try.

  • Deactivate the plugin that’s giving your trouble, but DO NOT UNINSTALL IT, or you will lose your settings.
  • Download the updated version of the plugin directly from the WP repository

plugins ftp svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww

  • FTP into your site and overwrite the plugin files with the updated ones you unzipped earlier (usually found in [path]/wp-contents/plugins/[plugin-in-question]/[files|dirs to overwrite])
  • Note: if you choose to do that, it’s possible it will change and therefore the same problem will appear.. (However, since you are using an FTP you shouldn’t have that problem)
  • Re-activate the plugin from within the WordPress dashboard – it will update what needs to be updated

WordPress Plugin Update Failed: Problem Solved

If you try each solution stated in this article, you should find one that works. The advantage of WordPress is that it is used by a large percentage of the internet, hence most problems have already been encountered, therefore finding a solution is easy.

Always remember that no matter the problem, there is always the option to roll your website back to a previous version of itself. This method allows you to start again or try a different potential solution until you find the one that works.

Hey, did you know data can be beautiful too?

wpDataTables can make it that way. There’s a good reason why it’s the #1 WordPress plugin for creating responsive tables and charts.

wpdt_example svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2FwwwA real example of wpDataTables in the wild

And it’s really easy to do something like this:

  1. You provide the table data
  2. Configure it and customize it
  3. Publish it in a post or page

And it’s not only pretty, but also practical. You can create large tables with up to millions of rows, or you can use advanced filters and search, or you can go wild and make it editable.

“Yeah, but I love Excel too much and there’s nothing like it on websites.” Yes there is. You can use conditional formatting like in Excel or Google Sheets.

Did I tell you that you can also create charts with your data? And this is only a small part. There are many more features for you.

Si vous avez apprécié la lecture de cet article sur l’échec de la mise à jour du plugin WordPress, vous devriez consulter celui-ci pour savoir comment réparer “votre connexion n’est pas privée”.

We also wrote about a few related subjects like WordPress links not working, how to fix installation failed, could not create directory, how to fix the site is experiencing technical difficulties, how to fix sorry, this file type is not permitted for security reasons and the link you followed has expired.

  • WordPress

How to Fix WordPress Updating Failed / Publishing Failed Error

Last updated on October 19th, 2020 by Editorial Staff | Reader DisclosureDisclosure: Our content is reader-supported. This means if you click on some of our links, then we may earn a commission. See how WPBeginner is funded, why it matters, and how you can support us.

Comparte 110 Cuota Pío Cuota Facebook Messenger WhatsApp Correo electrónico

Are you trying to fix the WordPress updating failed or publishing failed error on your website?

Sometimes when editing a post or page, you may see the updating failed or publishing failed error. This error does not give any clues, which makes it particularly difficult for beginners.

In this article, we’ll show you how to easily fix the WordPress updating failed error. We’ll also explain what causes this issue, and how to avoid this in the future.

Fix Refresh Error or Post Error in WordPress Post Editor Fix Failed to Update or Failed to Post in WordPress Post Editor

What Causes Updating Failed or Publishing Failed Error in WordPress?

Failure to communicate with the WordPress REST API causes the ‘Updating Failed’ or ‘Publishing Failed’ error in WordPress.

Refresh error or post error in WordPress post editor Update failed or post error in WordPress post editor

Basically, WordPress sometimes uses a set of APIs (programming methods) called ‘REST API’ to send and receive requests to the WordPress database.

If it fails to send and receive those requests, then some parts of your WordPress website may not be able to function. This includes the WordPress block editor, which uses the API to send update and publish requests to WordPress.

Why WordPress is Unable to use REST API?

Now you might be wondering, that if I didn’t make any changes to my website, then why did the REST API stop working on its own?

There are a number of scenarios that may prevent WordPress from using the REST API. For example, you may not be connected to the internet or have lost connectivity.

Other reasons may be a little more complicated. For instance, you may have accidentally changed the site URL, a WordPress plugin may be causing the issue, or a third-party service may be blocking the API calls.

That being said, let’s take a look at how to troubleshoot and fix the WordPress updating failed error.

Step 1. Check Your Internet Connection and Site URL

The most common cause for updating failed error in WordPress is losing the WiFi connection. If your computer loses the internet connection as you are writing a blog post, then WordPress will fail to save your changes.

Make sure you are connected to the internet by visiting other websites in a new browser tab.

If your internet is working fine, then the next thing you would want to check is your WordPress site URL setting.

Simply go to Settings » General page and make sure that the Site Address and WordPress Address options are correct. For most websites, you should have the same URLs in both fields.

WordPress Site URL Setup WordPress Site URL Setting

If your site URL settings look ok, and you are connected to the internet, then you can move on to further troubleshooting.

Step 2. Check REST API Status Using WordPress Site Health

WordPress comes with a built-in site health tool, which shows important information about your site’s security and performance.

Simply go to the Tools » Site Health page to view the report. If REST API is not working, then you will see it under recommended improvements as ‘The REST API encountered an unexpected result’.

WordPress site state REST API error REST API error in WordPress Site Health

It may also show you some debugging information which may explain what happened when WordPress made the REST API call. Studying this may give you some clue on which plugin or third party service may be causing the issue.

However, if it doesn’t give you any clue, then you can move on to the next step.

Step 3. Disable All Your WordPress Plugins

If a WordPress plugin is causing the REST API to misbehave, then the easiest way to find it out is by deactivating all your WordPress plugins.

You can go to the Plugins » Installed Plugins page and check the box to select all plugins. After that, use the Bulk Actions drop down to deactivate all plugins.

Disable all WordPress add-ons Disable all WordPress plugins

After that, you can go to the post edit screen and try to update. If the Updating Failed error disappears, then this means that one of your plugins was causing the issue.

You can now start activating your WordPress plugins one at a time and try to reproduce the error. Once you find the plugin causing the issue, you can seek support from plugin author or find an alternative plugin.

On the other hand, if disabling all WordPress plugins didn’t make the error go away, then continue to the next step.

Step 4. Check Website Firewall Service

If you are using a website firewall service like Sucuri or Cloudflare, then there is a chance that these services may block REST API requests.

This could happen if their firewall filters consider your IP address to be suspicious. They may also block REST API requests if your website is under an on going DDOS attack.

If you are using Cloudflare, then you can temporarily disable Cloudflare to see if this resolves your issue.

Normally, you’ll find Cloudflare settings under Domains section of your hosting dashboard. Bluehost users can find under My Sites » Manage » Performance tab.

Temporarily Disable Cloudflare and Bluehost Temporarily Disable Cloudflare in Bluehost

If you are using Sucuri, then you can reach out to their support team, and they can whitelist your IP address or let you know what’s causing the issue.

Plugins and Firewall services are the most common cause of the updating failed error. However, if you are still seeing the error, then there are a few more things you can do.

Step 5. Enable and Review WordPress Debug Log

WordPress comes with built-in feature to keep a log of all WordPress errors. It does not log the REST API errors, but it will help you see if there are some other issues that may be causing the error.

Simply add the following lines to your wp-config.php file.








// Change WP_DEBUG to true


define( ‘WP_DEBUG’ , true );


// Keep a log of WordPress errors


define( ‘WP_DEBUG_LOG’ , true );

Don’t forget to save your changes and re-upload the file to your server. You can now intend to publish or update a post in WordPress to reproduce the error.

After that, you can connect a WordPress download account using an FTP client and on the mat /wp-content/. Desde aquí, puede descargar el archivo debug.log a su computadora.

Debug log file in WordPress Debug log file in WordPress

You can open the trace file in a plain text editor such as Notepad. You may contain some errors, warnings or notices detected by WordPress while you were working on your site or a user was visiting your site.

Debug log file showing PHP errors in WordPress Debug log file showing PHP errors in WordPress

If you see something that directs you to a plugin or theme file, then this can be a useful clue. You can then mention this error when requesting support on the WordPress.org forums or from your hosting provider.

Step 6. Cambia temporally the classic WordPress editor

Una solución temporal a este error es habilitar el editor clásico. It is the old editor of WordPress which is not based on REST API for updating and publishing content.

You can enable it simply by installing and activating the Classic Editor plugin. Pour plus de détails, check out our step-by-step guide on how to enable the classic editor in WordPress.

Upon activation, you can simply edit the post you were working on. I could save it and publish it without seeing the update error or post error in WordPress.

classic editor classic editor

Finale Step : Request support

If all else fails, you may need to request assistance. You can start by contacting your hosting provider directly. They have access to server logs and additional tools. It could also be caused by a misconfigured server or a failure on your end.

You can also seek help on the WordPress.org forums or the WPBeginner Facebook group, where other experts and users can help you fix the error.

For more details, see the following article on How to Properly Request and Get WordPress Support.

We hope that this article will help you solve the WordPress update error or the publication error. You can also bookmark our complete guide on the most common WordPress errors and how to fix them.

If you’re invited to this article, subscribe to a new YouTube channel for WordPress video tutorials. Also puede encontrarnos on Twitter and Facebook .

Appearance 110 Fee Tweet Fee Facebook Messenger WhatsApp Email

Google Google translator

Google Google Translate

Video WordPress plugin update failed

Related Posts

Fatal error require failed opening required

Contents1 Fatal error of PHP No se pudo to open the archive requerido2 Subscribe to RSS3 About WPML3.1 From day one, our priorities have remained the same…

Your media file could not be processed.

Contents1 Fixed: Twitter Error “Your media file could not be processed”1.1 freno de mano1.2 ClipChamp Créer1.3 FilmoraGo1.4 adobe sparkle2 Video Your media file could not be processed….

Gravity forms not sending email

Contents1 [SOLVED] Why doesn’t Gravity Forms send email?1.1 How does Gravity Forms send email?1.2 Résoudre les problèmes liés aux formulaires Gravity qui n’envoient pas d’e-mail1.3 Configure Gravity…

This webpage is not founderr_file_not_found

Contents1 Install and manage extensions1.1 Install trusted extensions1.2 Agregar o eliminar el acceso a un sitio específico1.3 Hide extensions1.4 Show extensions2 5 Ways To Permanently Fix Chrome…

Continue to this website not recommended missing

Contents1 Ignore the “Continue to this website (not recommended)” message1.1 publication information1.2 Information1.3 Contents1.4 Admin Items2 Internet Explorer 10 ‘Continue to this website’ is missing option2.1 Similar…

Error loading stream id not found on server

Contents1 JWPlayer 6 error message “Error loading stream: ID not found on server”1.1 Inscrivez-vous ou connectez-vous1.2 Post as guest1.3 Post as guest2 Subscribe to RSS3 Problems with…