WPAU Bugfixes and Updates
Phew couple of more major bugs and other minor bugs have been fixed for the WordPress Automatic Upgrade Plugin and this release version 0.5 is pretty much stable and should work on 95% of the blogs.Previously it wasn’t working for 30% of users due to a server issue. Thanks to Robert Morse for first of all reporting the bugs like many of you did, but also a super thanks to him for providing me with a identical system where I could run the tests and fix the bugs. Thanks to Robert I have been able to fix the most major bug and release the new version.
Couple of other bug fixes and once again thanks to again the feedbacks from all of you.
Sometimes all plugins were not re-activating after running the final step (specially the DoFollow plugin) which has now been fixed. The issue with some plugins is that they try to run their function when WPAU activates them even though they are deactivated. You can check more about that issue on the post from Just Thinkin which has my reply about the issue.
Thank you Kirk and Ronald for helping me fix this issue.
With the new version it will take a wee bit longer to re-activate your plugins as it checks if a plugin throws up any errors while re-activating with WPAU.
Note: If a plugin does not reactivate with WPAU it does not mean that there is some problem with it, it is only because of some programmatically error which breaks the re-activation only with WPAU. You can always re-activate the failed plugins using the regular plugin page.
Another change is that the automatic option will not re-activate the plugins, you will have to click the link PLEASE REACTIVATE YOUR PLUGINS after running automatic version to re-activate your plugins. The link will be shown below the automatic progress bar once upgrade has complete, please click on the upgrade db link before you can run plugin re-activation in case WordPress has some database upgrades.
Finally The plugins that could not be activated will be shown in the logs, you will have to re-activate those plugins manually.
Other than that fixed a issue where WPAU was allowing to continue even when some errors were there. Now WPAU will not be able to continue when there are errors.
That’s it head below to read release notes and updates.
Also a special thanks to Rishi and Shankar for donating towards development expenses. Donations are always welcome and if anyone of you wants to donate you can use the Chipin widget in the sidebar.
On other serious note hold back till this weekend I am releasing another plugin which hopefully many of you will like so keep checking back on the blog for the latest plugin.
Installation
To do a new installation of the plugin, please follow these steps
- Download the wordpress-automatic-upgrade.zip file to your local machine.
- Unzip the file
- Upload
wordpress-automatic-upgradefolder to the/wp-content/plugins/directory - Activate the plugin through the ‘Plugins’ menu in WordPress
If you have already installed the plugin
- De-activate the plugin
- Download the latest files
- Follow the new installation steps
ChangeLog
- Version 0.1 released Tuesday, July 17th 2007
- Version 0.4 released Thursday, July 26th 2007
1. Added a prelim check before starting the process to check whether or not we can write files to the server
2. Checks if previous version files were not cleared
3. If we cannot write the files to server asking user for ftp credentials so that we can make the permission changes
4. Fixed bug where task status was not reported on error thus showing a db error to the user
5. Fixed a bug where open_basedir restriction is on for a website hosted as virtual folder
- Version 0.5 released Wednesday, August 8th 2007.
1. Fixed bugs where user had a www folder with full write permissions but the public_html folder was not writable.
2. Fixed issue where while writing there were ftp errors while creating backup directory but still plugin said all ready to go
3. Fixed issue where plugins were not activating even if one plugin threw an error.
4. Fixed other issues with html and reporting
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 Latest Version downloaded times
Yipeee!!! This plugin will get out beta and turn into a stable plugin soon. I have covered almost 95% of systems than can be upgraded to the latest versions with this plugin it may still have some bugs but I can release it as a stable version in next release. 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
Blips
August 8th, 2007 at 8:24 pm #
This is a big time saver for sure, I love this plugin!
I used versio 3 to update a copuple of blogs and got some errors. Version 5 gives me the same errors on my development site.
Warning: copy(/public_html/wp-admin/setup-config.php) [function.copy]: failed to open stream: Permission denied in /home/blipsdev/public_html/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 173
Warning: copy(/public_html/wp-includes/js/tinymce/plugins/spellchecker/config.php) [function.copy]: failed to open stream: Permission denied in /public_html/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 173
Warning: copy(/public_html/wp-includes/js/tinymce/tiny_mce_config.php) [function.copy]: failed to open stream: Permission denied in /public_html/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 173
(I removed /home// )
These files all have the word config in them maybe that is a clue. I checked the files, they have chmod 444, after chmod to 644 it was ok. I checked 4 other sites on the same hosting-server and they have exactly the same copy errors because of the chmod setting.
Richard
August 9th, 2007 at 12:38 am #
Thanks for your fixing, Keith! I like this plugin very much. I have shared it with my friends by my website.
BTW, I have an idea that maybe you can create a PO file to make it can be translated into any languages. If so, I can translate it into Chinese and Japanese if you don’t mind. The plugin will be more popular at that time.
Anyway, thanks again for this nice pugin!
mo
August 9th, 2007 at 3:14 am #
Hello,
Thank you for this excellent work,
I was wondering when WPAU finishes it’s work, does the ftp user (the one we would usually use to access the folders) have access to the wp-admin, wp-include folders again?
and also is there somehow anyway to keep self included files in the wp-admin folder, untouched. Like in the case that some plugins require us to upload files to that folder.
Thank you again for your time and fabulous work.
keith
August 9th, 2007 at 8:18 am #
Hi Mo,
Yes the ftp user has all access to the files after the upgrade is complete. Yes those files are left untouched WPAU does not delete any files.
Also thanks for your appreciation it makes me work more
keith
August 9th, 2007 at 8:20 am #
Hi Richard,
Once this plugin reaches a stable level of supporting 98% of servers I will release the version which supports multiple lanuages. Of course I would then require help to translate the plugin to different versions.
Keith
keith
August 9th, 2007 at 8:20 am #
Hi Blips,
This plugin cannot function when the permission is set to 444 it requires the permission to be 644 for running.
Thanks for the appreciation.
Keith
blips
August 9th, 2007 at 9:13 am #
Keith;
I’m fully aware of the fact that the files have to be on 644 but there was nothing I did when installing it in the first place. I’m puzzled how these files got on 444 but encountered this with 5 weblogs I updated with your valuable plugin.
mo
August 9th, 2007 at 10:08 am #
thank you for that information
looking forward to using this plugin!
sa
August 9th, 2007 at 4:02 pm #
I have activated this plugin. What woul I do next? How can I start update?
Blips
August 10th, 2007 at 4:58 pm #
Tonight I upgraded another blog with your plugin with great success. Some enhancements I would suggest;
1.Color error lines in red so they stand out more.
2.Check if the files are writable before the copy and if not chmod them.
3.Incorporate this plugin; http://blog.ftwr.co.uk/wordpress/wp-version-check/
Then a question;
What happens with files that are obsolete?
Prairie Progressive
August 11th, 2007 at 6:00 am #
Despite verifying and reverifying several times that the data I am using in the very first step/screen of WPAU asking for my FTP credentials is accurate, I continually get the message: “Oops!!!!! We are unable to connect to the ftp site with the data your provided, could you cross check and give us the data again”
All the information provided is identical to what I use with my FTP client. I have had no problem logging in to my FTP site using it several times amidst and since trying to use WPAU. There is no question my site is up and running.
Suggestions??
cooper
August 12th, 2007 at 6:17 pm #
I should kiss you, but a beer it will have to be.
Mikael
August 13th, 2007 at 6:02 pm #
This one is the bomb!
Carl
August 20th, 2007 at 8:28 pm #
Tried with this version. Still unsuccessful. I was able to actually hit the activate button, but it sent the admin area 404 because of a bad interaction with Google Sitemaps Generator and WP-Geotrack. After disabling those two plugins, I was able to activate WPAU. Incidentally, a syntax error pops up after I activate WPAU. It’s not there when I deactivate it. Apparently that one is caused by an interaction with the PodPress plugin. It disappears if I deactivate either PodPress or WPAU.
Ran through the normal mode (did you disable automatic mode - the link sent me nowhere), but got hung up at maintenance mode. Have some logfile output:
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2007-08-21 00:26:13
Task End Date: 2007-08-21 00:26:13
Task Log:
Putting the site into maintenance mode /var/www/html/wp-content/plugins/wordpress-automatic-upgrade
Copying /var/www/html/index.php to /var/www/html/index.php.wpau.bak
The file was successfully copied
Moving the maintenance file to root
ERROR -> Could not put the site into maintenance mode
I ran WPAU with all other plugins disabled, just to be sure. I also made sure the file permissions were set properly on index.php.
blips
August 26th, 2007 at 11:47 am #
Keith;
I do not know if I asked these questions before or it was just in my mind to ask for enhancements and clarificatins;
-What happens with files that are obsolete so not used by WordPress anymore? (copy to the obsolete dir?)
-Can you build a version control into the plugin so people can see if they are on he right version?
-Build a donate buton on the plugin last page.
-Change the color of error linesto standoutfrom the standard reporting tekst.
-Check if a file is writable otherwise CHMOD it.
Great plugin thats for sure.
Thanks
Blips.
Tomas Jablonskis
August 27th, 2007 at 11:03 am #
Hello,
In upgrade process I got error with database. But then finished, all is OK.
In log I found this:
Task Name: getlatestfiles
Task Status: Failed
But seems WordPress is upgraded.
Thank you, very useful plugin!
keith
August 27th, 2007 at 3:27 pm #
Glad it helped you update
Pat
September 5th, 2007 at 5:51 pm #
I ran this plugin and upgraded my site. Everything went well, no errors, however the site is stuck in maitenance mode. I followed the directions from the previous FAQs
-Login to your site using http://FTP.
-Delete the index.php file.
-Rename the index.php.wpau.bak file to index.php
It got rid of the message saying that it is in maintenance mode, but it displays only a blank white page. Has anyone else encountered this issue? If so are there any fixes for it? or do I have to re-install a backup copy of the site?
Any help would be greatly appreciated!
Luca Moretto
September 5th, 2007 at 6:42 pm #
i have a problem in http://www.quadreria.com after upload the plugin and activate it! I have in all my blog a blank pages and i can’t admin the blog. I have erase the plugin but the pages is all blank!! you can help me?
Rasmus Johnsen
September 16th, 2007 at 1:51 am #
This is really a grate plugin. I’ve used it and so far it have worked fine. Thank you very much for this.
Apparently now I have the same problem - I get this when trying to upgrate a 1.5 version of worldpress:
WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' task_log = 'Putting the site into maintenance mode /home/.sites/69/site21' at line 1]
UPDATE wpau_upgrade_log set task_status = , task_log = ‘
Putting the site into maintenance mode /home/.sites/69/site214/web//wp-content/plugins/wordpress-automatic-upgrade
Copying /home/.sites/69/site214/web/index.php to /home/.sites/69/site214/web/index.php.wpau.bak
The file was successfully copied
Moving the maintenance file to root
ERROR -> Could not put the site into maintenance mode
‘, end_date = ‘2007-09-16 10:58:46′ where task_name = ‘maintmode’
Any suggestions?
Thank you!
Chuck Simmins
September 26th, 2007 at 12:12 pm #
I’m getting hung up at the very beginning. It cleans up, then I have a screen where I can choose automatic or “click here”. Choosing the “click here” results in a 404 error. Nothing appears to happen when I click automatic.
keith
September 26th, 2007 at 8:14 pm #
Hey Chuck,
You seem to have a problem that many others have where the directory you host the WordPress in is not same as your actual blog URL. I am working on the changes, and also working on testing a mock release upgrade from WordPress 2.3 to 2.3.1 to check compatibility with WordPress 2.3.
Unfortunately my plugin is not part of WordPress Extend so I will be also adding a API to check for upgrades for my plugin in the usage screens.
Keith
Will
November 13th, 2007 at 5:38 pm #
I now find that there is another thread/post here for this plugin and find the answer to my question that I TRIED to post on the other tread. Oh Well….
What is the schedule to fix this for those of us, (lots) that have WordPress in its own directory?
Anand
January 1st, 2008 at 9:13 am #
Hey Carl
I have exactly the same issue as you had put in here. Were you able to debug and resolve the issue. It would be great if I could be assisted on this.
Thanks
Steve Higginbotham
February 19th, 2008 at 6:36 pm #
I am trying to use wpau, but mine sticks in the middle of the upgrade saying, “Unable to open maintenance mode.” Not sure if those are the exact words, but it cannot open/access/go into…something like that…maintenance mode.
Can anyone help me with this?
willard97
February 26th, 2008 at 5:50 pm #
The install of this plugin went very well until the very end when I was prompted to activate (or reactivate) the existing plug-ins in place prior to the install. Then the screen on the install page went blank. I tried to refresh the page, still blank. I went and checked the root domain of the blog, several inner pages, the admin/login page — all were blank, white screens.
Thinking that the install may have been in “maintenance mode” as described in the install, I attempted to “delete the index.php file and rename the index.php.wpau.bak file to index.php” and still nothing.
After spending several hours on the forums attempting to find a resolution to this problem, I went to the backup files in an attempt to reinstall the backups and start over. That didn’t work either.
Long story short, pretty much a total nightmare trying to install this plugin. I have installed dozens of plugins and not all of them have worked properly, but none of them from my experience has crashed the entire site. They might now work, but you can simply login and deactivate it and your fine. This plugin brought down our entire blog for almost a full day (and still counting) and was forced to have my host do a hard restore of the blog directory from our nightly backups, which is still in process.
It seems like a plugin that was too good to be true. And it was in fact, too good to be true.
Be very, very careful about using this plugin. For new blogs or blogs with light traffic that will not be impacted greatly by the potential of going dark for a day or more, go ahead and try it.
But if you’re an established blog with a significant income stream or any income for that matter, I wouldn’t use it.
Danger Will Robinson.
Terence Chang
March 27th, 2008 at 2:27 pm #
I seem to have huge problem with the permission.
When it asks to download the latest file from wordpress. It generate over few hundred errors like this.
Warning: is_dir() [function.is-dir]: Stat failed for /home/xyz1234/public_html/blog//wpau-backup/wordpress/wp-includes (errno=13 - Permission denied) in /home/xyz1234/public_html/blog/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php on line 4952
I looked into the FTP, the program creates a blank wordpress folder under wpau_backup folder. WordPress folder is dynamic created with CHMOD 757. The status of the process is still saying download and upload successfully.
When I click next …. that’s where something went wrong. It deactivate all my plugin and tell me the upgrade is completed, which is NOT.
There are more problems after that, which I can’t explain all of that here. I just want to know how to solve that permission issue before troubleshooting the next issues.
Thanks!
WirelessGuru
March 31st, 2008 at 7:07 pm #
I just tried to update one of my blogs from 2.3.2 to 2.5 using WPAU plugin.
In one of the steps I got the same error messages as the above post relating to pclzip.lib.php on line 4952. After it says everything was upgraded - it was not. I was still at WP 2.3.2.
Next I tried the automatic mode and it kept failing at downloading the latest WP zip file. After that I couldn’t get back to the Admin panel I got an error “Fatal error: Cannot redeclare documentation_link()” in /wp-admin/includes/template line 70 as I recall.
I then went to the backup files that I had downloaded as part of the manual update process - both the database and file zip folders were empty. I found a wpau-backup folder in my root directory that did have the backups. However I didn’t trust them to be complete.
To resolve my issue I manually deleted the wp-admin and wp-includes folders, and re-uploaded 2.3.2 from when I had downloaded and saved it on my computer a few months ago. Everything is now working, whew.
I’ve de-activated the WPAU plugin and will manually upgrade to WP 2.5. A nice concept - but it didn’t work for me.
Guro
April 27th, 2008 at 3:44 am #
I’m experiencing the same problem as Terence Chang. When I get to step “Get or upload the latest version of Wordpress” and press “Let’s go” I received the following error:
Warning: is_dir() [function.is-dir]: Stat failed for /home/****/public_html/spanak//wpau-backup/wordpress/wp-includes/js/jquery (errno=13 - Permission denied) in /home/****/public_html/spanak/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php on line 4952
Terence Chang is very comprehensive. I only want to add when I created the missing folders in Wordpress it continued to give me the same error with other different folders.
Vesse
May 4th, 2008 at 6:09 pm #
I got the same problem:
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2008-05-05 01:57:19
Task End Date: 2008-05-05 01:57:19
Task Log:
Putting the site into maintenance mode /home/public_html/wordpress/wp-content/plugins/wordpress-automatic-upgrade
Copying /home/public_html/wordpress/index.php to /home/public_html/wordpress/index.php.wpau.bak
The file was successfully copied
Moving the maintenance file to root
ERROR -> Could not put the site into maintenance mode
What can I do to get the WP to the maintenance mode manually?
Jeff
July 15th, 2008 at 12:25 pm #
I see a number of comments about people being stuck at the error “Could not put the site into maintenance mode”…is there any solution?
myname
November 5th, 2008 at 11:31 pm #
Like many, many above, I’m getting stuck at the error
The file was successfully copiedMoving the maintenance file to root
ERROR -> Could not put the site into maintenance mode
If anyone finds a solution, please post it here and/or on this thread.
Thanks