26
Jul

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

writable.

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.

Why?

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.

Installation

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

ChangeLog

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

License

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

Support

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

Download

Download Wordpress Automatic Upgrade v0.4 downloaded 59533 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 wpplugins@techie-buzz.com

534 Responses so far | Have Your Say!

  1. Manu
    July 27th, 2007 at 3:56 am #

    Thanks for the update, will try it out and post back.

    BTW, the readme.txt file in the plugin folder says “Stable tag: 0.3″ and the “wordpress-automatic-upgrade.php” lists the version as 0.3.

    Because oif the WP plugins page also displays version as 0.3 even though you are calling it version 0.4 in the changelog.

  2. TechZilo
    July 28th, 2007 at 1:58 am #

    Thanks for the plugin….
    I havent tested it yet, ‘coz i got fantastico to install WP for me. However, for the upgrade to WP 2.3, WPAU is my saviour :D

  3. chris
    July 29th, 2007 at 7:41 am #

    I downloaded and used the plugin on a test installation of wp 2.02 beta at yahoo, all went well. Then using it on real site all seemed to go well until I tried to write a new post. No longer able to use previous Catagories or create new ones. New pages will all be Uncatagorized! HELP!
    In place of the Catagory listings is this message:
    WordPress database error:
    [Unknown column ‘link_count’
    in ‘where clause’]
    SELECT cat_ID FROM
    wp_categories WHERE
    category_parent = 0 AND (
    link_count = 0 OR
    category_count != 0 OR (
    link_count = 0 AND
    category_count = 0 ) ) ORDER BY
    category_count DESC

    I rebuilt the database and upgreaded all links, but no luck, turning off all plugins made no difference,

  4. keith
    July 29th, 2007 at 9:53 am #

    Hi Chris,

    I tried to search the release archive but I did not find any release version 2.02. From where Can I download the version?

    Please let me know so that I can help you fix the problems.

    Keith

  5. WordPress Plug-in Advice
    July 29th, 2007 at 8:05 pm #

    There are so many ideas about so many things. It does sometime happens that an idea really seems worthless, only to be proved later on to be a million $ idea.

    Having said that, I beleive the wordpress automatic update plug in is not the plug in I would want to have installed on my blog. The reason is simple. I dont want to have something that is not tested entirely by the community. Although the WordPress itself is such a great application, However with absolutely no third party audits, no body knows what may come out of wordpress in any NEW release. I would not want to, nor recommend anyone just to go ahead and update to newer versions of wordpress as soon as they are released.

    This However would not apply to my test sites. I may want to test any new product on the test version of my blog. BTW everyone of you should have a test version of your blog. Most of us dont.

  6. Chris
    July 30th, 2007 at 1:56 am #

    Hi back Keith,

    Yes you are right there is nothing in the archive; the only place 2.02b resides is on Yahoo.com. But I could send you the copy of my test install of 2.02b which has only 2 posts - tests. All users of WP on yahoo are stuck with that version - yahoo refuses to upgrade, and manually upgrading is a disaster in the making. The testblog zip is 1.1 megs - I use a mac if that’s a problem for you. I exported the db and it is 52kb - .sql.gz

    Let me know, and contact me

  7. Britt Malka
    July 30th, 2007 at 4:57 am #

    Hi Keith

    I tried your latest version of the plugin (0.4), but I get an error message. A new one this time.

    It sais:

    Warning: ftp_mkdir() [function.ftp-mkdir]: Aucun nom de repertoire specifie in /usr/home/xxx/money-online101.com/htdocs/tips/wp-content/plugins/wordpress-automatic-upgrade/wpau_prelimcheck.class.php on line 393

    Warning: ftp_site() [function.ftp-site]: Aucun nom de fichier specifie in /usr/home/xxx/money-online101.com/htdocs/tips/wp-content/plugins/wordpress-automatic-upgrade/wpau_prelimcheck.class.php on line 399

    “Aucun nom de fichier specifié” means “no file name has been specified”.

    My webserver is FreeBSB, PHP 4.4.

    Does that tell you anything? Feel free to contact me by email, if you like.

    Kind regards,
    Britt Malka

  8. Britt Malka
    July 30th, 2007 at 7:38 am #

    Hi WP-iA

    You wrote: “I dont want to have something that is not tested entirely by the community.”

    Isn’t that rather selfish? I mean, just letting others do the hard work, experience problems, resolve problems, and when everything is fine, you join the game and get it all for nothing?

    After all, you are talking about a “community”.

  9. WordPress Plugin Advice
    July 30th, 2007 at 8:47 am #

    No dear, it is not selfish, becasue you misunderstood me. I am not talking about not testing something myself, what I am talking here is that on any serious site … you don’t put stuff that has not seen the test of the times.

    Please read the last paragraph of my comment.

  10. Britt Malka
    July 30th, 2007 at 9:08 am #

    Okay, I see. But I don’t agree with you. I consider JohnChow.com’s blog for example for a very serious blog. After all, he makes more than $10,000 per month with it, and I know that he has tried plug-ins that was totally new. Yes, some has given him problems, but still his blog is serious.

    If you have a backup - which every serious blog should have - you should have no problem testing new plug-ins with your blog.

  11. WordPress Plugin Advice
    July 30th, 2007 at 9:47 am #

    Although I even disagree in trying a BRAND new plug-in right away on a production level site. John Chow might only be lucky. He might have tested that on his test site or have just gone though the comments of the people who tried that within that day. Who knows. This is pure speculation what a 3rd person did or did not.

    But still think about it. Updating the whole of WordPress core with a snap is far more different then trying a new plug-in.

  12. Jason Hendricks
    August 1st, 2007 at 8:27 pm #

    Two words for you about this plugin…KICK ASS! I upgraded two sites all the way from version 1.5.2 to the latest 2.2.1with no problems whatsoever. Thanks, a beer fund donation is on its’ way. :)

  13. Karen Bryan
    August 2nd, 2007 at 4:30 am #

    I wanted to say thanks for your Automatic update plugin. As a non techie person I couldn’t cope with doing the upgrade which I urgently needed to do as my travel website was hacked through my Wordpress blog. The hackers changed the homepage of my website. It was an awful thing to happen to a small business. I rely on my son for my IT support and he’s not always available so the more things I can do on my own the better. I’ve stumbled this post and I’ll write about your plugin in my other blog about blogging for business.

  14. keith
    August 2nd, 2007 at 7:29 am #

    Hi Karen.

    Thanks for the appreciation. I also recieved your email and am trying to figure out the problem for the other blog.

    Keith

  15. Karen Bryan
    August 2nd, 2007 at 10:33 am #

    Thanks, Keith, for trying to assist with the upgrade of my other blog.

  16. Jeremy Curry
    August 2nd, 2007 at 6:29 pm #

    Wow - I was scared to do this, just in case anything broke down, I’ve done a lot of customization here and there over the last few years, and I didn’t remember where and what not I had done stuff - but I tried the plug-in anyway, and it worked seamlessly! Very Nice plugin! Thank you!

  17. MTO
    August 4th, 2007 at 2:50 am #

    I had this same problem. Same errors. I’m using linux server, so nothing to do with that.

    Apart from those error warnings all seemed fine, it does say “done WPAU is ready to roll”, but in view of the above errors I didn’t know if it would be safe, so I didn’t proceed.
    I have no idea what to do, what can be done?

    Thanks.

  18. g
    August 6th, 2007 at 12:56 am #

    Great functions. you’ve made my admin life easier.

    just one feature request. the ability to style the maintenence page.

  19. Rk
    August 6th, 2007 at 9:40 am #

    This is the greatest plugin (in the first place, it should not have to be plugin at all ..the WP guys should have made this automated install a part of WP itself..going by the frequent releases they are making)
    Anyways, thanks a lot. It worked like a dream !

  20. Dakar
    August 7th, 2007 at 4:58 am #

    Hi,
    I’m a very active member of the Israeli WordPress community.
    In order to work with WordPress in Hebrew (i.e. RTL) we do some translations and lots of changes in the code for every WordPress version.

    Will it possible to change the plugin to work with our repository ?
    (code wise and permission wise)

  21. keith
    August 7th, 2007 at 10:22 am #

    Hi Dakar,

    I have plans to make this plugin compatible for other languages once I fix the major bugs with it.

    Thanks
    Keith

  22. keith
    August 7th, 2007 at 10:23 am #

    Thanks RK I am glad it worked for you, hopefully it should be perfect in coming weeks

  23. Jean-François CASANOVA
    August 7th, 2007 at 11:21 pm #

    Congratulations for this plug-in !

    We have used it for 2 of our blogs and that went very well. It is really well done.
    We will soon talk about it on our blog (in French) : http://blog.infomedsolutions.com

    Keep up the good work !

  24. ia
    August 8th, 2007 at 12:51 pm #

    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!

  25. Steve
    August 9th, 2007 at 7:35 am #

    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.

    Steve

  26. Ryan
    August 9th, 2007 at 8:05 am #

    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!

  27. keith
    August 9th, 2007 at 8:15 am #

    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

  28. keith
    August 9th, 2007 at 8:16 am #

    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.

    Keith

  29. keith
    August 9th, 2007 at 8:22 am #

    Hi Jean,

    Glad it worked out well for you and thanks for the appreciation.

  30. Jeromy
    August 12th, 2007 at 4:10 pm #

    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?

  31. chris
    August 18th, 2007 at 6:45 am #

    Keith,
    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.

  32. JAX
    August 18th, 2007 at 11:08 pm #

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

    Best Regards
    JAX

  33. Jeff
    August 20th, 2007 at 7:42 am #

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

  34. Carl
    August 20th, 2007 at 10:10 am #

    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.

  35. keith
    August 20th, 2007 at 4:02 pm #

    Hi Carl,

    Do you see any errors while activating the plugin

  36. Carl
    August 20th, 2007 at 4:14 pm #

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

  37. keith
    August 20th, 2007 at 6:39 pm #

    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.

    Keith

  38. David Carrero Fdez-Baillo
    August 26th, 2007 at 10:07 pm #

    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.

  39. BillSaysThis
    August 27th, 2007 at 8:04 pm #

    Oddly, this installed and ran just fine on two of my blogs but on the third I cannot activate the plugin, it gives a fatal error every time. I have 2.2.1 on this blog (2.2.2 on the ones which worked). Not a very descriptive error report but any ideas on correcting it?

  40. Dave Zan
    August 28th, 2007 at 1:21 am #

    Sigh, I installed this latest version. But I’m still getting that fatal error message whenever I try to activate it.

    Is it because of my host, maybe? I’m using Jumpline.

  41. Britt Malka
    August 28th, 2007 at 1:31 am #

    Hi Dave Zan

    I had the same error with other plug-ins, until I changed the .htaccess file and gave WordPress more memory to work with. I put this code in the start of the file:

    <FilesMatch "\.(php|html?)$">

    php_value memory_limit 32M

    </FilesMatch>

  42. BillSaysThis
    August 28th, 2007 at 7:03 am #

    I’m having the same issue with the fatal error, and using Britt’s idea resulted in a 503 error. This is a WP 2.2.1 install, I had no difficulties activating and running WPAU on two WP 2.2.2 instances on the same server (though they’re in a different doc root).

  43. Shriram
    August 28th, 2007 at 10:11 am #

    WOW!
    This plugin works like a breeze. Everything seems ok on first glance.

    All this while, I didn’t upgrade coz I found the process too cumbersome. You have done a great job Keith.

    Hats off to you :)

  44. James
    August 28th, 2007 at 10:30 am #

    Two issues.
    I seem to be missing this from the url which causes it to fail “edit.php?”. On build .4. This seems to happen on each step. I have to add it manually to advance.
    http://www.*****.com/wp-admin/page=wordpress-automatic-upgrade/wordpress-automatic-upgrade.php&task=files&_wpnonce=8f40fd7a57

    Once i get to DB backup i get this issue.
    CGI Error
    The specified CGI application misbehaved by not returning a complete set of HTTP headers.

    Not sure what that is all about. Wanted to let you know about these, thanks!

  45. Ajay
    August 28th, 2007 at 1:05 pm #

    Does the plugin knock off all the contents of the wp-includes and wp-admin folders before adding the new files?

  46. keith
    August 28th, 2007 at 1:45 pm #

    Hi Ajay,

    The plugin does not delete old files, it overwrites all the existing files with new ones. The first step always backs up the new files so you have access to the older files too.

  47. Dave Zan
    August 28th, 2007 at 9:53 pm #

    Thanks, Britt! Plugin activated, script worked, blog updated. :)

  48. Billy Dennis
    August 29th, 2007 at 2:03 pm #

    Thank you for this plugin. Well done! I’m wondering, hoping against hope actually, that this can be tweaked to work with WordPress Multi-User (WPMU)?

  49. keith
    September 2nd, 2007 at 3:33 am #

    Thanks Billy, but I have yet tested it out with multi user

  50. Finis Price
    September 3rd, 2007 at 4:47 pm #

    I tried the auto upgrade and it says it failed at Step 3, anyone have any ideas how to fix that?

  51. Finis Price
    September 4th, 2007 at 3:36 am #

    I get an error saying the update failed while downloading the update, Step 3. Anyone know what to do to get by this?

  52. Pat
    September 5th, 2007 at 5:33 pm #

    I am having the issue where the site got stuck on maintenance mode. I followed the instructions:

    Login to your site using http://FTP.
    Delete the index.php file.
    Rename the index.php.wpau.bak file to index.php
    Performing these steps should remove the maintenance mode message.

    It got rid of the message indicating that the site is in mailtenance mode, however I am simply left with a blank white page with no data.

    Has anyone else run into this issue? and is there a solution?

  53. effemmeffe
    September 7th, 2007 at 5:53 am #

    I tried your plugin: everything goes well, but at the end the blog was still in maintenance mode so I tried to follow the FAQ, but when I connect with FTP there was no index.php.wpau.bak file…
    I replaced the index.php with the backup one and all comes back, but I want to file this bug to you.
    Regards.

  54. Alex
    September 9th, 2007 at 5:51 pm #

    I went from 2.2.2 to 2.2.3 no problem. On another blog, set up the same way on the same server but in a different subfolder off my account root (/site1 and /site2, you get the idea), my upgrade of the v2.0.6 blog takes me after the “ready to roll” page to a 404 page on my blog and dies.

    I have no idea where to look to start troubleshooting this. I was choosing the “manual” step-through-it-one-step-at-a-time link to proceed.

    Ideas? Thoughts? It really was pretty slick the first time I ran it, and I’m kinda bummed it’s effing up on this one. :(

    Thanks for any help!

    -alex

  55. Pablo Pasqualino
    September 10th, 2007 at 6:11 am #

    Hi Keith, thanks for the plugin, its really helpful!

    One tip for the people that still get the FATAL error when trying to activate the plugin even adding Britt’s tip to increase “memory_limit”.
    You also need to have Short Open Tags enabled on your php (Keith, if you remove the use of short open tags, it will improve the compatibility for different php installations).
    You can add Short Open Tags support creating an .htaccess file on your wordpress admin directory (wp-admin) with the line:
    php_flag short_open_tag on

    I hope it helps!

  56. ncollision
    September 12th, 2007 at 3:29 pm #

    Great plugin - works without a hitch on my two installations so far! Thank you!

  57. Ying
    September 12th, 2007 at 5:13 pm #

    Thank you for the plugin! It’s save a lot of time :)

  58. September
    September 13th, 2007 at 1:29 am #

    hey. may i know what is ftp host?

  59. September
    September 13th, 2007 at 1:32 am #

    Hey. may i know what do i fill in in ftp host?

  60. P|xeL
    September 13th, 2007 at 4:13 pm #

    Nice plugin. Thanks for your work! ;-)
    Bye,
    P|xeL

  61. Doug Smith
    September 14th, 2007 at 2:34 am #

    Has anyone used this plugin with blogs created at Network Solutions? They are languishing at a version before 2.2 and don’t seem to have plans to move up.

  62. Sachin Sagar
    September 15th, 2007 at 1:56 am #

    I tried to install this in my wordpress 2.2.2
    But the installation failed saying error:
    Plugin could not be activated because it triggered a fatal error.
    Ain’t this plugin compatible with WP 2.2.2 or is there any other hidden steps?
    Sachin

  63. conancat
    September 18th, 2007 at 3:40 am #

    hey thanks for the great plugin!! :D i’m really web illiterate when it comes to ftp or mysql sorta stuff, the manual at the website really makes me dizzy haha… this really helps a LOT!! :D thanks!

  64. Simon
    September 18th, 2007 at 4:52 am #

    Won’t work for me. Installed and active. Now what? What happens? Links are to blank pages. call me dumbb and all, but are there any clear explanations of what to do?

  65. john
    September 25th, 2007 at 2:33 am #

    Will this work to upgrade to 2.3?

  66. keith
    September 25th, 2007 at 7:43 am #

    Yes john this will upgrade to 2.3 too

  67. John Tracy
    September 27th, 2007 at 4:38 am #

    Holy crap!
    This was the easiest time I have ever had upgrading my wordpress install.
    I look forward to all of the new releases now!

    THANKS!

  68. Martin
    September 27th, 2007 at 1:33 pm #

    thanks for making this, hope it works as well as everyone says!

  69. nika
    September 28th, 2007 at 10:59 am #

    oh man, I am not getting this darn thing to work.

    Plugin seems to enable ok. When I click “Click here so that we can start the upgrade.” I get a file not found error with this:

    The requested URL /wp-admin/page=wordpress-automatic-upgrade/wordpress-automatic-upgrade.php&task=files&_wpnonce=SECRETNUMBERS was not found on this server.

  70. Doug Smith
    September 29th, 2007 at 2:22 am #

    I ran the utility and the next day I started seeing this serious database error. I am sure Network Solutions is going to tell me I’m on my own now since I upgraded the product myself. Is there a script available that I can use through my database widget to crate the missing table?

    WordPress database error: [Table 'wp_00478a7_0.wp_post2cat' doesn't exist]
    SELECT cat_ID AS ID, MAX(post_modified) AS last_mod FROM `wp_posts` p LEFT JOIN `wp_post2cat` pc ON p.ID = pc.post_id LEFT JOIN `wp_categories` c ON pc.category_id = c.cat_ID WHERE post_status = ‘publish’ GROUP BY cat_ID
    80

    When I ran the utility it did its preliminary check and found no issues. It wasn’t clear to me which button to use to start so I clicked on the first start option which took me to the front page of my blog. That screen sat there for about 30 minutes so I clicked back and selected automated. The knobs, dials, bells and whistles finally began. One screen had to do with updating the database. It completed without error.

    I created a few posts after the upgrade and didn’t see this occur yesterday. I’m going to disable Admin Tiger (I think its called) to see if that is related to this issue. That widget was installed after the upgrade.

    Network SOlutions does not allow us to access the WP database except through WOrdPress widgets. I have access all day to databases I create using the database PHP interface but not WP.

    I’m new to WP and know just enough to be very dangerous. Any help would be appreciated.

    Doug Smith
    edior@popularwireless.com

  71. keith
    September 29th, 2007 at 8:36 am #

    The error you may be seeing is because of incompatible plugin with WordPress 2.3 to solve this I would suggest you disable one plugin at a time and see if the error goes away.

    If the error persists you can re-enable that plugin, but I would be quite sure that you will be able to resolve the issue by using this method, since I myself had a issue and disabling few plugins those errors went away.

  72. keith
    September 29th, 2007 at 8:36 am #

    @Nika you should find this fixed in the latest version.

  73. Karthik
    October 4th, 2007 at 12:26 pm #

    AFAIK, Fantastico also offers automatic upgrades?
    Correct me if I’m wrong…

    Nice plugin all the same!

  74. keith
    October 4th, 2007 at 3:28 pm #

    Yes Karthik it does but not all hosting providers have Fantastico

  75. Karthik
    October 4th, 2007 at 9:15 pm #

    Absolutely - I was just answering Sumesh’s comment ;)

    The plugin is a much needed one, especially with the frequent updates that WP releases - full credit to you!

  76. christen
    October 5th, 2007 at 3:12 pm #

    This is a handy plugin alternative to going through the steps of upgrading. I’m looking for an easy way to set up maintenance for a client’s site, so I tried upgrading my site to test out the plugin.

    The first time I tried running the plugin there was a little hiccup because I was running php in safe mode and hadn’t realized it until that moment. This stopped the upgrade process. I fixed the issue and continued, but once the upgrade was finished I was stuck in “maintenance mode”.

    I ran the plugin a second time, and that time things went great resulting in a site upgraded from 2.2 to 2.3.

    I’m still not sure if this is a plugin I would recommend to someone who isn’t confident or hasn’t ever tried upgrading WP manually. In my case, it did speed up the process by a few minutes, which is cool.

  77. keith
    October 7th, 2007 at 2:32 pm #

    Glad you liked it christen.

  78. Alex
    October 8th, 2007 at 7:23 pm #

    I’m getting the error below after click “click here to run the clean up process before continuing”:

    Fatal error: Call to undefined function: current_user_can() in /home/blue/public_html/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 999

    Can you help me with this error message??? I tried to find a solution before ask, but I coul not find it.

    Thanks
    Alex
    Bluetoothlounge.com

  79. daniel
    October 9th, 2007 at 9:54 pm #

    Absolutely GREAT
    Thank you MONSIEUR
    combined with oneclick this is the tool for dummies like me

    Wish you a nice day

  80. keith
    October 10th, 2007 at 8:02 am #

    Thanks a lot daniel.

  81. Max
    October 13th, 2007 at 3:21 pm #

    Great concept.

    I have tried to upgrade my Wordpress v1.5.2 using your plugin v0.7 but it fails with the error “Could not backup your WordPress files. Failed at Step 1.”

    Any ideas where I’m going wrong?

  82. Doug SMITH
    October 17th, 2007 at 3:21 pm #

    I ran the plug in on my first blog inside my Network Solutions account and it ran perfectly without having to supply FTP information. I installed a second blog one directory level deeper for another URL within my account and the plug in wants my FTP information. The FTP information is provided but fails each time. The same login information is used for WS_FTP Professional and I can get into the sub-site just fine. Network Solutions uses an FTP address for the account that does not contain the domain praweb.org.

    According to the FTP client the directory permissions are 765. The same as the permissions for the first blog. First blog lives at

    /htdocs/blog1 and the new one at htdocs/pra/prablog the second domain praweb.org points to htdocs/pra so I guess /pra is the default directory for that domain. (Doing this with a second domain is new to me so that may be the issue.

    Why is FTP asked for in this case and why would it fail? This is a virgin blog, just created it with the blog creator at Network Solutions. Nothing different from the first blog except that this one is one level farther down.

  83. sldesigns
    October 17th, 2007 at 6:34 pm #

    BRILLIANT. Just great. Will recommend and use for my other sites.

    Not related to plugin: te100.kontera.com is REALLY slowing down my browser tonight

  84. sldesigns
    October 17th, 2007 at 6:57 pm #

    Brilliant plug in.

    This site though is SUPER S L O W. Contributed for your work. But please get rid of kontera

  85. Dave
    October 21st, 2007 at 6:38 pm #

    Thanks for the plug-in. Most hosts are still stuck providing 2.2 with the auto installers.

  86. MJ Klein
    October 24th, 2007 at 9:06 am #

    plug in worked amazingly well! took up a total of 5 minutes of my time, including d/l the backup files and upgrading the database. scary!

    thanks for a great plugin Keith!

  87. mo
    October 27th, 2007 at 4:39 am #

    supper cool!!!
    Thank you for all the hard work - the ftp login was like icing on the cake..

    YAY!!!

  88. nyunyu
    October 27th, 2007 at 11:04 am #

    Hi keith, Thanks for this wonderful plugin. Seeing so many positive feedback makes me want to try. I have local installation of wordpress on my vista, after activating and tried to upgrade, it failed at step 2 which is it failed to backup my database. Any suggestion on where did I’ve done wrong? your reply is very much appreciated.

    Thanks again.

  89. Anna
    November 5th, 2007 at 9:45 am #

    Hi. I could not even get past giving my credentials. I gave the site my ftp user and password, and the directory which looked to be only/html. I did not see the words, public at all. Is that is okay? Used the ftp host as my http://ftp.mysite.com It kept saying wrong credentials. I know the user and password works because I tried it on myphp admin file. Help! Thanks.

  90. Billy Dennis
    November 5th, 2007 at 11:14 am #

    Spoke too soon, I think. I’m running 2.2.2 now and I’m trying to upgrade to 2.3.1. The process now fails at Step 2 (backing up the database). It does the same whether if I doing it automatically, and step-by-step. I can manually backup the database just fine using DB Manager. Any advice anyone?

  91. valerie
    November 6th, 2007 at 11:40 pm #

    Can’t activate the plug:

    Parse error: syntax error, unexpected $end in /home/…/public_html/wphome/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 1222

  92. azwanhadzree
    November 9th, 2007 at 10:40 pm #

    Tried and it works. Great work on this plugin :) . It makes upgrading to the latest version a breeze.

    Anyway, I got a problem with the backup files that your plugin made. both the wordpress php files and database backup. After downloading the zip files, I can’t extract it. Downloaded it twice but still the same. I use both enzip and winrar to unzip. Any idea?

  93. srini
    December 13th, 2007 at 1:19 pm #

    I have experienced the same problem. I am trying to upgrade from version 1.5.2. What should I do differently?

    I did run it on another WordPress installation on the same domain, and it worked just fine, though I was just testing the plugin on a brand new installation of the latest WP version.

    Thank you.

  94. Anna Hackman
    December 14th, 2007 at 5:26 am #

    I figured out why I could not even start. It does not show properly under IE 7. The boxes are too small so you can’t put any of your info in the boxes. Plus maintenance mode does not even work with IE 7 either only firefox.

    I can’t get past putting it into maintenance. I saw above that someone had the same issue but my index.php is in my root directory. I did notice where the new wp files got put did have a blank index.php and index.htm. They showed up in the a separate folder called wp in the backup files. Could this be the problem? How do I get my site back to the way it was. My newest post is all there is right now. anna

  95. Kirk M
    December 24th, 2007 at 12:24 pm #

    Hi Anna,

    I came across your question and I don’t know if it’s been answered yet but I can almost guarantee that Bad Behavior is causing the problem by blocking WAUP from properly querying your blog and it’s database. Bad Behavior has a very bad habit of blocking legitimate queries as well as those automated SpamBots and also causing corruption in the database just enough to throw all sorts of different errors and there’s no way you can know what’s causing these problems. I ditched Bad behavior because of this.

    Anyway, I see your website has all the posts back but if you wish to use WAUP I suggest you deactivate Bad Behavior first before attempting the upgrade. Personally I suggest also that you lose Bad Behavior altogether and go with Aksimet and bcSpamBlocker (you can find the latter at the WP extensions Plugins Directory) instead. I’ve had excellent results with this combination.

    Just thought you’d like to know.

  96. Anna
    December 24th, 2007 at 12:38 pm #

    Hi kirk-thanks so much for helping me. Actually the problem was my server. It was not giving the plug-in permission to complete what it was doing. However, in IE 7, the FTP information boxes still look weird. I had to use firefox but once I did with the server permission (my host had to do something) everything worked out okay.

    I will look at the other spam plug-in you suggested. Thanks again for taking the time to help me. Anna

  97. Kirk M
    December 24th, 2007 at 1:43 pm #

    You’re very welcome. Merry Christmas and Happy Holidays to you and all that. :D

  98. michael
    December 27th, 2007 at 10:12 am #

    hey,

    i have used this plug in with great success on one of my newer blogs (on a new hosting service) (from 2.2.2 to 2.3.1) ,

    Worked really easy, no problems at all, thank you ;)

    But on some of my other blogs (older hosting service, also older wp 2.2.1) f.ex. this one:
    http://blog.miguelovitch.dk/2007/12/27/act-now-get-payed-peer-play-advertising-every-time-you-site-or-blog-have-a-visitor/

    i get this message:
    Your server is running in safe mode. WPAU cannot continue in safe mode. Please ask your system administrator to change the setting to disable running in safe mode

    i am not sure, is this something i can do my self or is it my host?

    Also i have another quistion, i have made some changes in the sidebar,
    These files are located in the theme folder,, just to bee 100% sure: the theme will remain the same after update?

    thanks again,

    wish you the best

    michael pedersen

  99. BillSaysThis
    December 31st, 2007 at 6:08 pm #

    Even after upgrading to 0.8 with ALL other plugins deactivated I still get the fatal error and cannot activate WPAU. Still works perfectly on two other WP instances on the same host/account.

  100. floriana
    January 2nd, 2008 at 12:27 pm #

    excuse me, but I need an help “for dummies”
    I’m not able to find my “ftp credentials”
    the first is already written, and is admin (I think it’s right)
    the second is the password I use when I go to wordpress to admin my site
    the third is ftp base directory: in transmit I use the first folder, so I think I need to write /,
    the fourth (ftp host) ??
    is it username, password, name of the site? or what?
    excuse me, but I’m only a poor italian radiologist and what is obvious for you is not so obvious for me…
    I’ve searched it on the web but I can’t find an answer.
    Thanks, floriana

  101. floriana
    January 2nd, 2008 at 1:21 pm #

    hi, I’m a beginner
    I’ve a problem in finding ftp credentials,
    the first two, I think, are right like they appear: admin and admin’s password
    third and fourth for me are more difficult
    third; only / if I use root directory ???
    fourth is the worst : - ((((
    http://ftp.sitename? or “username”,”password”?
    I’m a radiologist, so it’s not my work…but I’d like to upgrade anyway!
    it’s difficult to find on the web these informations, so simple for you but terrible for me, thanks, floriana

  102. Sue
    January 3rd, 2008 at 11:01 am #

    Wow, wow, wow is all I can say. Tried it on my local installation, worked like a charm. Did it on my hosted sites, went just as smoothly. I always hated to upgrade…it took so long to reactivate plugins (if I could even remember which ones I had working). Now off to make a donation for your work on this project. Thanks so much.

  103. Bill
    January 4th, 2008 at 6:14 pm #

    Had some niggling performace issues after using this to upgrade from wp23 to 231.