WordPress Automatic Upgrade plugin update

Lots and lots of bugs and sleepless nights and no paid work later. Here is the next version of WPAU. I have fixed almost all of the bugs you have reported which I heartily thank each and every one of you for. Here is the NextG version of the plugin which works on most of the servers that have different users for FTP and web.Here is what I mean by that

On some shared servers the webserver (Apache) is the same for multiple user and in those cases the Apache user was not allowed to access files uploaded using a FTP client. To overcome the situation I added a preliminary check where it checks if the plugin is able to update the site or not.

If the error is due to FTP user and webuser being different you will be asked for your FTP credentials. We do not save any of this information with us and the information will be discarded at the end of the upgrade.

This is necessary if you need to run a automatic upgrade on your server, without this the information the plugin will not run.

What do we do with the FTP information?

With the FTP information you provide WPAU will change file permissions so that WPAU can write the files to your server. Once the upgrade is over WPAU will automatically change the permissions back to read only.

This step has been added so that you do not have to do the permission change manually. Only in certain rare cases will it fail to upgrade permission’s and ask you to do so manually.

Here are some of the bug fixes for the latest version.

  • Runs a premilinary check to see if your server is compatible so that WPAU can run
  • Advices to clear backups from past upgrades
  • Fixed errors for virtually hosted sites
  • Automatically change permissions for upgrade after asking FTP credentials
  • Fixed bug where DB error was reported when WPAU used to fail
  • Fixed bug where you could not see log when the WPAU used to fail
  • Updated FAQ to add the new questions
  • Fixed issues to only backup and upgrade core WP files (This was a issue when WP was hosted in root directory)
  • Fixed a issue where wp_redirect was not working due to header file already being included in the plugin
  • Cleaned up the code to make it better

That’s it folks, all your bugs and abuses are welcome since it helps me make this plugin better. I hope you will in future use this plugin to upgrade your wordpress installation without any errors and headaches.

Also with so much love and people reporting bugs I am so glad that I have been able to fix most of

Frequently Asked Questions

What is WordPress Automatic Upgrade?

WordPress Automatic Upgrade (WPAU) is a plugin that automatically upgrades your wordpress version to the latest files provided by wordpress.org.

Should I interfere with the WordPress Automatic Plugin Process?

No never, If the plugin fails it fails for a reason please do not interfere with any process that fails.

Do I need to change permissions on files?

No WPAU will ask you for your FTP credentials and do it automatically.

Why does WPAU run the preliminary checks?

WPAU runs the preliminary checks to determine in conditions in which it can feasibly update your site to the latest version provided by WordPress.

Why does WPAU ask me to clean up files?

When you run the plugin once we create backup files at the end of the process you need to delete these. If you missed deleting these files then WPAU will ask you to run cleanup before continuing.

Why use this plugin?

WordPress releases regular updates and security fixes to the software and after sometime makes it mandatory. Every time you have to manually upgrade your WordPress installation. This plugin helps

you to upgrade your installation without any efforts. We also ensure you will always download the latest version.

Which version of the WordPress does it upgrade to?

It upgrades to the latest version that WordPress has made available for download.

What is the lowest version from which I can upgrade?

The lowest version of WordPress I have tested this to work is with WordPress 1.5.

What files do you upgrade

This plugin only upgrades the files that are essential which includes the file in wp-includes, wp-admin and the root directory

I made some modification in the themes, will that be affected?

No, we do not touch those files at all. We only upgrade files in the root directory and wp-includes and wp-admin directory.

I modified the plugin files to play around and something went wrong, will you provide support for that?

No, this plugin is intended to run as it is. Support is free except when u modify it.

My site is in maintenance mode and the plugin did not complete. What do I do now?

Only under some rare condition will this happen. To get your site back online you need to do these things.

  1. Login to your site using FTP.
  2. Delete the index.php file.
  3. Rename the index.php.wpau.bak file to index.php

Performing these steps should remove the maintenance mode message.

Why does the plugin say that it cannot upgrade my site?

We run preliminary checks to see if the plugin can run well with your site. Only in certain cases it will tell you that it cannot upgrade your site because the functionality of the plugin depends on it.

Why I am asked for my FTP credentials?

Initially we try to check whether your WordPress installation is writable or not. If we find that its not writable we ask you for you FTP credentials so that we can do the necessary things to make it


What do you do when you get my FTP credentials?

First of all for security reasons we do not store your FTP Credentials. We only use it to change the file permission so that the plugin can run normally.

Once we run the appropriate steps to check that everything is alright only then will the plugin continue the further steps.

What do you do when I give you my FTP credentials?

When you provide us with your FTP credentials we log into your site using FTP and change the permissions on files and directories such that it can be written by a file running on your server.

Is changing the permission on my site essential?

If you are asking in regards to WPAU absolutely. In order to complete the automatic upgrade we need write permissions to your site.

When will be asked for my FTP credentials and why?

You will only be asked for your FTP credentials when we cannot write to your server.


Some shared servers run different the webserver and apache as different users which is for security reason. In that case when we using the webserver cannot modify the files you have uploaded using a

FTP client.

In such a case we could ask you to do the steps required manually, but in the sense of automatic we want to make sure your upgrade is really automatic. When you provide us with those details we do

not store it (though we may ask you for this everytime we determine your server is unaccesible for us) we maintain a security level which no other plugins can exploit over and above the one

WordPress provides.

We are very much that this plugin should be automatic and only if our preliminary checks fail initially we will ask you for the FTP credentials. You will never be asked for that when the plugin can run

without the credentials.

If I am running on a server where FTP user and webserver user are different will I be able to overwrite / delete files using FTP

Yes absolutely. The plugin makes sure that whichever files it writes can be deleted by the user without having to contact the system administrator.

Why don’t you provide a option for me to upload the version I want?

Couple of things here. a. You should always upgrade to the latest version provided by WordPress. b. I do not want users to upload files that requires me to do multiple validations. The WordPress files that this plugin downloads is the best one I could use.

Will it remember the plugins that were active?

Yes it will remember the plugins that were active before upgradation and only activate those plugins.

How much bandwidth does the plugin use?

The plugin using about 2-3MB of your bandwidth to download files. You will use more than that in a regular upgrade process.

How long will my files and db backups be available?

This plugin is to be used for a continious process till completion, it provides you with backups which you should download before moving to the next step. If you do not download the backups, at the

end of the process you will be given an option to download it. Clicking clean up will delete those backup files.

Where are the files and db backup stored?

The files are db backups are stored in a folder called wpau-backup in the root folder of your site.

Does WordPress automatic upgrade provide a rollback?

No it does not, the function of WPAU is to seamlessly upgrade your versions. Rollback features will be added in future versions.

he bugs in this plugin. Though this plugin is still in infancy and all your bugs will help in bettering it and making it a real good plugin.

I sincerely thank everyone for using this plugin and telling me the bugs and hopefully this will be a real good way people would trust to upgrade their WordPress installation without battling a eye lid.


To do a new installation of the plugin, please follow these steps

  1. Download the wordpress-automatic-upgrade.zip file to your local machine.
  2. Unzip the file
  3. Upload wordpress-automatic-upgrade folder to the /wp-content/plugins/ directory
  4. Activate the plugin through the ‘Plugins’ menu in WordPress

If you have already installed the plugin

  1. De-activate the plugin
  2. Download the latest files
  3. Follow the new installation steps


  • Version 0.1 released Tuesday, July 17th 2007
  • Version 0.4 released Thursday, July 26th 2007


All files and their contents are licensed under the General Public License(GPL).


If you feel this plugin has helped you can leave a small donation towards further plugin development.


Download WordPress Automatic Upgrade v0.4 downloaded times

Please note this plugin is still in beta state and may have bugs. If you find any bugs or want to report any problems you have faced please feel free to leave your comments or you can send me a email at [email protected]

Published by

Keith Dsouza

I am the editor-in-chief and owner of Techie Buzz. I love coding and have contributed to several open source projects in the past. You can know more about me and my projects by visiting my Personal Website.I am also a social networking enthusiast and can be found active on twitter, you can follow Keith on twitter @keithdsouza. You can click on my name to visit my Google+ profile.

  • ia

    FYI, the static pages somehow became blog posts. Upgraded from 2.0.4 to 2.2.2. Not sure if the wp-admin/upgrade.php was the culprit, though. Any clues? :) I should be freaking out right now, haha. But other than that, this will be a fantastic plugin once it’s perfectly stable. Cheers!

  • Pingback: links for 2007-08-09 | MY Vast Right Wing Conspiracy()

  • Pingback: The Pool Room » The Easy Way To Upgrade WordPress()

  • Steve

    Tried your plugin, which by the way is great despite the couple of errors I ran across. The first I have my WordPress installation files in a different directory as it can be set in the Options:General page. For example I have my WordPress installations files in domain.com/wp/ and my index.php in the root. So it failed putting the site in maintenance mode. I was able to get pass this just by copying the index into the domain.com/wp/ directory. Oh, also none of the download links were correct because of this too.

    The second error I came across was plugin re-activation. I use SBM, so the plugin that deactivates widget support needs activated first. I wonder if this causes K2 users woes as well? At any rate I received an error saying SBM couldn’t be activated and to do it manually, which I did and evrything was happy agian. However, because a plugin activation failed the upgrade failed to cleanup the backups and install files, which it kindly did after a prompting when I went back to the Manage page.

    Thanks for the awesome plugin. even knowing these couple issues, I’m definately going to continue to use it.


  • I’m always leery of upgrading WordPress because I’ve had some unfortunate events in the past. But I just used your Automatic Upgrade Plugin on my blog and it couldn’t have been easier! I haven’t tried posting anything yet so I hope I don’t get the problem an earlier commenter mentioned…but it seems that everything is fine.

    Thanks for a great addition to WordPress!

    • keith

      Hi Ryan,

      Glad it worked well for you. There are still some new bugs which have been reported today and I should fix those and release a new version shortly.


  • keith

    Hi Steve,

    Thanks for your feedback, it’s feedback like these that help me make this plugin more stable. I will definitely fix this issue and release a more stable version shortly.


  • Pingback: Le Blog d’IMS 13 plugins indispensables pour WordPress()

  • Pingback: GustavoPaes.Net — WordPress Automatic Upgrade()

  • Jeromy

    My web host does not allow 777 permissions on folder – they require 755 to achieve write permissions (they claim it’s safer) – php on my server will not run with permissions set to 777 – will ths plugin know that?

  • Pingback: Webqualité | WPAU: maintenez automatiquement votre blog WordPress à jour()

  • chris

    In regard to the 2.02b WP version – is it safe to use the latest WPAU upgrade? I’ve managed to restore most of my files to a new install of 2.02.

  • JAX

    This is a great plugin. Is it possible to have this plugin work with WordPress MU also?

    Best Regards

  • I love this plugin. It seems like deleting the WPAU-backup files might be quite important. I forgot to do that and recently had a problem with my theme reverting back to default WP theme (Kubrick). Based on the research I found that problem usually relates to a plugin, most people cite the WP Mobile Edition but I’m not using that. I thinking that it was the copy of WP in the WPAU-backup files somehow being called that caused a conflict in the db and the theme reverting back to the default (http://trac.wordpress.org/ticket/3907).

  • Carl

    I’ve been using WPAU on my personal blog since 0.1 and haven’t had a problem. When I copied the 0.1 folder over to another site, I got a blank page when I tried to go to the plugins page. I deleted the folder and that page came right back up. I downloaded 0.4 and put it on the site, same problem. The plugins page is the only one affected.

    I’m using php 4.3.9 with apache 2.0.52 on a linux server. It’s shared hosting. I’m running WP 2.1.3. I had tried upgrading to 2.2 when it first came out, but it made a mess of my site. I was hoping WPAU would be able to do it better. Any help appreciated.

    • keith

      Hi Carl,

      Do you see any errors while activating the plugin

      • Carl

        Keith, if only I could get to activate it :). All I’ve done is copy the wordpress-automatic-update folder to my plugins folder.

        • keith

          Hi Carl,

          Sorry I missed this from your earlier commetn the latest version now is 0.5 this has the latest patches you should try this one out.


  • Pingback: 17 plugins pour boosté WordPress()

  • Pingback: Weblog Tools Collection » Blog Archive » Winners - Wordpress Plugin Competition()

  • Pingback: WordPress Plugin Competition Blog » Winners - Wordpress Plugin Competition()

  • Pingback: Congratulations WordPress Plugin Contest Winners()

  • Pingback: Gewinner Plugin-Wettbewerb - Finger.Zeig.net()

  • Pingback: Nico Nemil | Filipino Web Developer | Pinoy Web Designer | Intermediate Graphics Artist » Winners - Wordpress Plugin Competition()

  • Pingback: Terminó la Competición de Plugins de Wordpress()

  • Pingback: Wordpress Plugin Competition “Winners Announced” » D’ Technology Weblog: Technology News & Reviews()

  • Pingback: WordPress プラãâ€()

  • Pingback: Wordpress: Lista de plugins no recomendados - Parte 2 » Buayacorp - Diseño y Programación()

  • Please check the security for this plugins.

    1. WordPress Automatic Upgrade: Permite a cualquier usuario no autenticado:
    * Generar y descargar los archivos de WordPress (incluye wp-config.php).
    * Generar y descargar una copia de seguridad de la base de datos donde está instalado el plugin.
    * Activar/Desactivar todos los plugins.
    * Actualizar la versión de WordPress.
    2. OneClick: Al ser vulnerable a CSRF, permite descargar plugins — o código malicioso — desde cualquier URL.
    3. Who Sees Ads: Es vulnerable a CSRF y XSS.
    4. MyDashboard: Es vulnerable a CSRF y XSS.