sticky
not a support questionImportant Message for those whom WPAU is not working, this is a workaround for those users for whom the plugin does not put the site into maintenance mode.
Try changing all folder permissions to 777 and then running the plugin, once that is done go back and change the file permission to 644.
That’s it I have emailed this solution to many users and it has worked from them.
Keith
How do you change the file permissions? Can you do it by just changing the permissions to public_html and it will change it for all the folders under there or do you have to do each file individually? Right now, I don't have a site because it is halfway in the middle of the upgrade and I don't know how to put it back to the way it was before I started the upgrade. I'm kind of frustrated. Any suggestions you have would be greatly appreciated.
I was having a similar problem, but I found a different solution. I had mine setup so the the back-end of the blog was in a directory, but the index.php page was in the same location as the directory containing the blog (if that makes any sense). What I had to do was copy the index page back into the same location as the back-end files, ran the wpau again, clean out the old files and it worked.
Hi,
I could not get WPAU to work using local file access; I ended up changing my password temporarily and using the FTP method. This worked fine - so, thanks for writing this plugin, but the local file access seems to be broken somehow.
It would be really nice if you could add some way of attempting the uprade regardless of the result of the check for write access to the files - I think it might be the check itself which is buggy.
Very nice of you to write the addon though, saved me having to think too hard.
cheers,
- pgl
[edit: added request for override ]
OK, found it:
$permission = exec("ls -l $theFile |awk '{print $1}'", $output, $error);
if($error == 0) {
//get the perms
$thePerms = $this->chmodnum(substr($permission, 1));
//if its 644 or 744 we cannot run man
//tell our wpau guy out there we need to change perms
//we only can write files when they are 766 or 666 lets see
$this->userPermission = $thePerms[0];
if($thePerms[2] < 6) {
$canRun = false;
}This is unfortunately not such a great way to figure out whether the file is writeable or not (it would be writeable if 030, 070, 120, etc.), but good try. Also, uh, right at the beginning of the function you have:
$chmod = @chmod($theFile, 0644);so even if the file was writeable it would never find the "6" you check for. 
Heh.
The proper way to check would just be:
$canRun = is_writable(ABSPATH . 'wpau-backup');There was a couple of other issues in runFTPPrelimCheck(), so I rerwote it to provide the same functionality (I think) - I hope that's OK:
function runFTPPrelimChecks() {
if (!is_dir(ABSPATH . 'wpau-backup')) {
$this->canMakeBackupDir = @mkdir(ABSPATH . 'wpau-backup');
$this->createIndexes();
}
return is_writable(ABSPATH . 'index.php');
}cheers,
- pgl
PS: no preview for posts? tut, tut.
Changed file permissions to 777...
get the following error message ..........
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2008-07-21 07:18:07
Task End Date: 2008-07-21 07:18:07
Task Log:
Putting the site into maintenance mode /home1/profitn1/public_html/wp-content/plugins/wordpress-automatic-upgrade
Copying /home1/profitn1/public_html/index.php to /home1/profitn1/public_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
Hope you can advise!
Tom
Found the solution!!
hi!
I have been unsuccesfully trying to use WPAU to update my WP 2.0.7 to last version.
The plugin didn´t put the site into maintenance mode, even though I continued with the process and got some serious errors, but I arrived to a glitched panel of WP 2.6...
I have managed to restore my database and the wp folder and now I am back again in the starting point.
I was going to give a try to that tip of changing folder permissions to 777 but when I do that, the website is not working (I get the INTERNAL SERVER ERRROR message)... I am also trying to figure out which folders do you mean and if I should change the permissions recursively (I am using Cyberduck) .... I tried different combinations (changing permissions for ALL the folders on my server... for the wp-folder and only for "wp-admin", "wp-content" and "wp-includes", but this error keeps appearing... ) its strange, but it must be connected...
btw, now my permisions are 0755 for every folder and file (I guess this is correct, I am sort of a bit newbie with these issues)
any help would be much appreciated, please. I am now deciding if I should stick to use WPAU or maybe start a manual update process, but I have to do this for 4 different websites and it will be very time-consuming... I was really happy when I found this plugin this afternoon after one year of not updating my WP systems.
thanks!
Try changing all folder permissions to 777 and then running the plugin, once that is done go back and change the file permission to 644.
hi again!
just to clarify I little bit, since after re-reading my latest post I think it was a bit cryptic (being written after a couple of hours of fights with WP and my server trying to make this work).
I repeated again the process and when WPAU sets the site into maintenance mode I get the "Internal Server Error" message (when I click in the confirmation link, that opens another window) ... therefore, since I guess this is the most common problem of people posting here, I just "undo" the update process, restoring my database and wp-folders backups.
Concerning the change of folder permissions, I still have that strange problem of WP not working when I change them (using cyberduck and firetp firefox extension too). Then I would need a clarification in the exact folders and / or files that need to be changed to be able to try this solution properly.
Please, any help will be much appreciated. I am waiting for a solution to this (hopefully!) before being forced undertake the manual update of several blogs. Many thanks.
What kind of selfish bastard posts an issue, then a second post to say simply "Found the solution!!"? - murdockcan, I'm looking at you. Take, take, take... is that all you can do? How about giving back for a change? I'm sure I'm not the only one facing the same issue, who'd might benefit from your solution.
Hi everyone.
I've tried to upgrade my wordpress version to 2.6 but the plugin isn't working for me.
When it has to put the site into the maintenance mode the following message appears:
Warning: copy(/home/led/public_html/weblog/index.php.wpau.bak) [function.copy]: failed to open stream: Permission denied in /home/led/public_html/weblog/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 357
We could not complete the upgrade please try again later, click here to check the logs
I've already change the folder permissions (plugins folder, am I iright?) but it appears the same message.
Below is the log for upgradation:
Task Name: files
Task Description: Backs up all the current files from the wordpress installation
Task Status: Complete
Task Start Date: 2008-07-30 15:18:35
Task End Date: 2008-07-30 15:18:35
Task Log:
Task Name: backupdb
Task Description: Backs up the database file
Task Status: Complete
Task Start Date: 2008-07-30 15:18:38
Task End Date: 2008-07-30 15:18:38
Task Log:
Task Name: newversionoption
Task Description: Shows you the options to upload latest files
Task Status: Complete
Task Start Date: 2008-07-30 15:18:48
Task End Date: 2008-07-30 15:18:48
Task Log:
Task Name: getlatestfiles
Task Description: Downloads / Uploads the latest files for wordpress
Task Status: Complete
Task Start Date: 2008-07-30 15:18:52
Task End Date: 2008-07-30 15:19:02
Task Log: Starting to download the file from http://wordpress.org/latest.zip
Downloading the files using Snoopy
Unzipping the files to /home/led/public_html/weblog//wpau-backup/
All set all files have been extracted
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2008-07-30 15:19:05
Task End Date: 2008-07-30 15:19:05
Task Log:
Putting the site into maintenance mode /home/led/public_html/weblog/wp-content/plugins/wordpress-automatic-upgrade
Copying /home/led/public_html/weblog/index.php to /home/led/public_html/weblog/index.php.wpau.bak
Could anybody help me with this problem?
Thanks!
Hi, I don't successfull for uddated my wp to last version, the plugin hs been change perrmission 777
=================
Warning: copy(/home/folder/public_html/wp-content/plugins/wordpress-automatic-upgrade/temp-index.php) [function.copy]: failed to open stream: No such file or directory in /home/folder/public_html/wp-content/plugins/wp-upgrade/wpau_upgrade.class.php on line 359
We could not complete the upgrade please try again later, click here to check the logs.
I couldn't get mine to work, either and I have absolutely no idea what to do. Permissions? What? Where? How? I don't really speak "computer," and need VERY clear instructions for this kind of thing (grin).
The error message I'm getting? As follows:
Warning: copy(/home/punctual/public_html/wp-content/plugins/wordpress-automatic-upgrade/temp-index.php) [function.copy]: failed to open stream: No such file or directory in /home/punctual/public_html/wp-content/plugins/wordpress-automatic-upgrade.1.2.1/wpau_upgrade.class.php on line 359
We could not complete the upgrade please try again later, click here to check the logs.
(I copied the entire log, if that's something that would be useful for those of you who know more "computer" than I do. But, honestly, I don't even know where the permissions settings ARE, much less how to change them ... hence the reason I was trying an automatic update plugin in the first place!
Thanks for any help.
This is getting frustrating. Some finds the problem to this error but do not post it and it seems like this post got abandoned already?
Has anyone found the solution to why WPAU refuse to set in maintenance mode? I don't get it either. This plugin works in my other site, but I don't know what exactly the difference with the other site I'm editing. I heard it was the PHP limit or something, but I checked the site I am having problem with WPAU and found out that it has larger PHP limit than the site in which the plugin is working;
Ahhh!! Is there anyone out there still know how to get this plugin works?
If so please...
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2008-08-11 21:42:32
Task End Date: 2008-08-11 21:42:32
Task Log:
Putting the site into maintenance mode /home/ramjtmp/public_html/wp-content/plugins/wordpress-automatic-upgrade
Copying /home/ramjtmp/public_html/index.php to /home/ramjtmp/public_html/index.php.wpau.bak
Help..
OMG what is wrong with you people?! You find the solution but doesn't share it.. talk about being selfish!
I'm having this problem on 1 site out of 7 and I have done nothing differently on this specific site..
Somebody tell us what the solution is, please!
Possible solution:
Here is the error that I was getting when WPAU version 1.2.1 (the latest) tried to upgrade Wordpress 2.6 to 2.6.1:
Warning: copy(/xxxx/xxxx/xxxx/xxxx/index.php.wpau.bak) [function.copy]: failed to open stream: Permission denied in /xxxx/xxxx/xxxx/xxxx/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 357
We could not complete the upgrade please try again later, click here to check the logs.
When I looked at the logs I saw this:
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2008-08-15 15:23:12
Task End Date: 2008-08-15 15:23:12
Task Log:
Putting the site into maintenance mode /xxxx/xxxx/xxxx/xxxx/wp-content/plugins/wordpress-automatic-upgrade
Copying /xxxx/xxxx/xxxx/xxxx/index.php to /xxxx/xxxx/xxxx/xxxx/index.php.wpau.bak
** SOLUTION (worked for me) **
Delete the index.php.wpau.bak file from your Wordpress base directory. The problem is apparently that the index.php.wpau.bak file was left over from a previous upgrade and WPAU could not override it, even though it had my proper FTP credentials.
If that does not work then try this solution *** AT YOUR OWN RISK ***
*** !!DISCLAIMER!! - I did what I'm about to describe on one of my sites and it worked. Everything seems to be fine now. BUT I MAKE NO PROMISES ***
The problem that I was having on another site is the same one that I just described. I was getting this error when trying to go into maintenance mode:
Warning: copy(/xxxx/xxxx/xxxx/xxxx/index.php.wpau.bak) [function.copy]: failed to open stream: Permission denied in /xxxx/xxxx/xxxx/xxxx/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 357
We could not complete the upgrade please try again later, click here to check the logs.
The problem was that something was going wrong with the initial preliminary check (I.e., I knew that WPAU needed my FTP credentials, but the check was insisting that I did not.) I played around with the code but was not smart enough to figure out why the check was saying that it did not need my credentials (I'm not a coder). So I just changed one word in the code to make it require my credentials. It's not pretty, but it worked:
1. Open up wpau_prelimcheck.class.php
2. Scroll down to the FTPPrelimChecks function. The code is on line 98, and it will look like this:
function runFTPPrelimChecks() {
3. Scroll down to the bottom of that function where you see this:
if($chmod) {
return true;
}
4. Change the word "true" to "false" (without the quotes). This causes the preliminary check to "fail" even if it thinks the files are writable. Then you can put in your FTP credentials and continue.
**NOTE: The second solution did generate some more permissions errors, but they were all in the preliminary check, and they did not affect the update or any of my files as far as I can tell. But again, I'm not a coder, so do it at your own risk.**
I have suPHP on my server and for some reason I am still getting a permission denied error on the maintenance mode step:
Warning: copy(/home/burdenwa/domains/drewburden.com/public_html/blog/index.php.wpau.bak) [function.copy]: failed to open stream: Permission denied in /home/burdenwa/domains/drewburden.com/public_html/blog/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 357
Any ideas? I had to force the plugin to pass the preliminary check, since I knew the files were writable even when the plugin thinks otherwise. I've hit a wall here...
OK, so I see that WordPress 2.6.1 is ready for me to update via WPAU.
So I click on the link to start the process only to get to his:
Warning: copy(/home/content/o/h/i/ohiosports/html/blog/index.php): failed to open stream: No such file or directory in /home/content/o/h/i/ohiosports/html/blog/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 357
We could not complete the upgrade please try again later, click here to check the logs.
Now my blog is located in a sub-directory on my root, but it's URL is not, so here's what I had to do in order for WPAU to work.
I had to move the files ".htaccess" and "index.php" from the root into the sub-directory.
Ran WPAU without a hitch.
Move those two files back to the root.
Open "index.php" and edited it by adding "/blog" to "/blog/wp-blog-header.php"
That's it.
I'm also getting this error message at the final stage:
Warning: copy(/path/to/my/install/index.php) [function.copy]: failed to open stream: Permission denied in /path/to/my/install/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 359
We could not complete the upgrade please try again later, click here to check the logs.
I fixed that by chmod 777 index.php, but then I get a shed load of other errors and the upgrade fails to complete even though it says it has!
I think this plugin is best avoided until the bugs are properly ironed out.
OK - I had the same problem and this is all I had to do to solve it.
Find the "index.php.wpau.bak" file that is in your web root directory (probably something like 'public_html' or 'www'
Change it's permissions to 777 - you can use a command like "chmod 777 index.php.wpau.bak"
then restart the automatic upgrade process - it worked for me!
(I also had another funny problem occur farther on in the upgrade process - almost at the very end where I had to upgrade the database. A new window opens and it tries to run wp-admin/upgrade.php and it fails saying the file wp-load.php doesn't exist - it should be in your web root. It was weird, the file didn't exist, so I copied it from another wordpress blog I have and then ran upgrade.php again and it worked fine.)
I hope this helps! It is a great plugin!
I have the same issue as murdockcan, for some reason WPAU can't put the site into maintenance mode, unfortunately, I have not found the solution yet.
Anybody?
I was getting the "failed to open stream: Permission denied" using the FTP method of updating. I quickly found a real easy solution. It turns out there was already a wpau-backup folder on my server from an early install. I deleted the folder and it worked more or less without problem.
When I go to "Set permissions of '/public_html/MYFOLDER/index.php.wpau.bak' to '777'"
I see in FileZilla the following response: "Response: 550 Could not change perms on index.php.wpau.bak: Operation not permitted"
No matter what I do, I can't seem to change the attributes...perhaps that is part of the issue.
I got the same error when trying to upgrade Wordpress as many others have:
"Warning: copy(/path/to/my/install/index.php) [function.copy]: failed to open stream: Permission denied in /path/to/my/install/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 359
We could not complete the upgrade please try again later, click here to check the logs."
I found following solution:
1. I deactivated the plugin wordpress-automatic-upgrade
2. I deleted the entire wordpress-automatic-upgrade folder from site
3. Downloaded new version wordpress-automatic-upgrade 1.2.2
4. Uploaded new version manually through FTP app.
5. Activated the plugin.
Now WPAU works without errors.
Hopes this can help somebody else.
Oh no...I did something terrible and now I don't know how to edit it.
Okay, first I deleted index.php.wpau.bak file, but I get all these errors about the persmission. Then, I changed the index.php chomd to 777, but I also got this error
[strong]Fatal error: Cannot redeclare validate_file() (previously declared in /home/ramjtmp/public_html/wp-includes/functions.php:2245) in /home/ramjtmp/public_html/wp-admin/includes/file.php on line 73[/strong]
I don't know what to do next. I think I have created more trouble. I can't even open my dashboard.
Please help!
that's what is says when I log in, and when I check the site, it shows this:
/strong/Fatal error: Call to undefined function get_shortcode_regex() in /home/ramjtmp/public_html/wp-includes/formatting.php on line 100 /strong/
Keith,
"Try changing all folder permissions to 777 and then running the plugin, once that is done go back and change the file permission to 644."
This doesn't make sense. All of what folders? You say we should change folder permissions, but then tell us to go back and change file permissions. Do you mean we should change every file in the Wordpress directory to 777? 644 is the default for files, not folders. Please clarify.
Also, there is one apparently quite important file, index.php.wpau.bak, whose permissions I can't change, because they are owned not by me but by some entity named "httpd". How there can be something on my own site (and not even in the root directory) that is owned by some entity other than me is a worrying mystery.
As you can see from all the posts above, Keith, your directions have not been helpful to many of us, and advice from others seems to have done more harm than good. Since Wordpress 2.6.2 is apparently an important security upgrade, this is a matter of urgency. Please don't leave us stranded here. Remember: many of us chose your plugin because we are not experts; just looking at Wordpress' manual upgrade direction makes my head spin.
I've been blogging with Wordpress for just a month or so, and until this problem came along, I thought your plugin was the best thing since sliced bread, and was planning on donating money. If this is the kind of support I can expect, I'm frankly glad I waited before donating.
the following worked for me.
my blog is installed in a subdirectory /home. when asked for my ftp details, I naturally put /home as where wp is installed. then i kept getting:
Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
but actually as indicated in the instructions on the same page, I should have put /public_html/home. once I changed that, it worked like a charm.
maybe what I did would help someone.
You must log in to post.