“An automated WordPress update has failed to complete – please attempt the update again now”– But there is no .maintenance file

I am trying to manually upgrade my wordpress to the latest version (3.0.3)– after autoupgrade fails.

After the upgrade everything works fine except for one little nagging message at the top of my admin area:

Read More

An automated WordPress update has
failed to complete – please attempt
the update again now

I search the Internet and everyone is saying that it is because of a .maintenance file located in the WordPress root folder, a relic of a failed auto-upgrade or a manual upgrade. In the second case one would just have to delete that file and everything would be fine.

But I search my wordpress installed directory, there is no such file. Any idea what contributes to this problem?

Related posts

Leave a Reply

3 comments

  1. I think what Rarst means is that it is a .file (or hidden file) much like the .htaccess file. If you are browsing your files, there is an option to show hidden files. Once that option is chosen, you will most likely also see the .maintenance file

  2. From the quick look at code:

    1. This message is triggered by maintenance_nag() function.
    2. The only condition to trigger is if $upgrading variable is defined.
    3. $upgrading variable is defined by including .maintenance file.

    So I reason that file is present, there is no other path to this message that I see in code.

    File starting with dot are regarded as system/hidden on Linux. It might be you simply don’t see the file, but it is present. How are you browsing directory? Can also try asking hosting to check for you if there aren’t enough permissions on your account or something.

  3. I had the same problem and I had shell access to the system so I was able to verify that there really was no file called ‘.maintenance’ anywhere on the system and yet still this message appeared. My WordPress is that provided by Ubuntu 16.04, so I don’t want to be perform updates myself as I am not interested in new features, and the responsibility for security-related updates lies with the Ubuntu/Debian package maintainers, so I really wanted to get rid of this message. My solution, which maybe isn’t the right one, but which worked for me was as follows. Obviously paths in your installation may differ.

    1. Edit /usr/share/wordpress/wp-admin/includes/update.php, locate the function maintenance_nag(), and directly after the following line:

      $nag = isset( $upgrading );
      

      add the following line:

      delete_site_option( 'auto_core_update_failed' );
      
    2. Reload the page and the message should be gone.

    3. Remove the line you just added.
    4. Reload the page and the message should still be gone.