IMPORTANT INSTRUCTIONS IF WPAU IS NOT WORKING

Techie Buzz Forum » WordPress Automatic Upgrade Form

IMPORTANT INSTRUCTIONS IF WPAU IS NOT WORKING

(63 posts)

Tags:

« Previous 123 Next »

matt-thorn
Member

I tried elimam's suggestion. It didn't help (there is apparently no problem with the path), but it did motivate me to look more closely at the logs. Here's what I got:

Task Name: maintmode
Task Description: Puts the site into maintenance mode
Task Status: Failed
Task Start Date: 2008-09-17 04:28:07
Task End Date: 2008-09-17 04:28:07
Task Log:
Putting the site into maintenance mode /hsphere/local/home/**********/**********/wordpress/wp-content/plugins/wordpress-automatic-upgrade
Copying /hsphere/local/home/**********/**********/wordpress/index.php to /hsphere/local/home/**********/**********/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

Using WebShell, I went through and changed the permissions of the "wordpress" folder, all the folders inside "wp-content", all the folders inside "plugins", and everything inside "wordpress-automatic-upgrade" to 777. (And I made sure "index.php.wpau.bak" was also set to 777.)

Finally, no error messages! Success! Congratulations! WPAU is confident that it successfully upgraded to WP 2.6.2.

Unfortunately, it didn't.

I flushed my browsers cache, restarted the browser, and there on my WP Dashboard is the "WordPress 2.6.2 is available! Please update now" message and WPAU's "Click Here to Automatically Upgrade WordPress to latest Version". I ran the upgrade again, once more got a cheerful declaration of success, and nothing has changed.

I'm starting to get pretty annoyed. First of all, this is supposed to be "automatic" (That's the whole idea, right?), and it was automatic until this latest WP upgrade, so why should I have to fiddle around with folder permissions, hoping that something will work (and making my site vulnerable in the meantime)? WPAU is also supposed to "upgrade" (That's the whole idea, right?), yet even when it behaves as if it has successfully upgraded, it hasn't.

Now I have to go back, make sure all my folders are reset to 755, hope that I haven't left some crucial file vulnerable, and wait for Keith to do something about this. Assuming, of course, that he is even reading this thread and intends to do something.

Posted 1 year ago #
matt-thorn
Member

Yoohoo? Anyone there?

Posted 1 year ago #
ablears
Member

I had the same problem - the plugin would fail at the maintenance mode step.

I solved it by going back to the initial step and changing my FTP connection details. My site is in the root, so I used "/" as the FTP path, whereas before it was blank and caused the error.

Anthony

Posted 1 year ago #
matt-thorn
Member

ablears suggestion did not work for me. Nothing has worked for me. Does Keith feel any sense of responsibility for his product at all? How can he expect people to make donations when there is zero support?

Posted 1 year ago #
archey
Member

Thank you ascension2020 deleting the index.php.wpau.bak file was just what I needed.

Posted 1 year ago #
P4rD0nM3
Member

If your webserver is using Apache, you have to let 'apache' the user to write instead of your 'username'. chown'ng the files worked for me, then I jsut did a chown -R back on the, to my username:group.

Posted 1 year ago #
matt-thorn
Member

If your webserver is using Apache, you have to let 'apache' the user to write instead of your 'username'. chown'ng the files worked for me, then I jsut did a chown -R back on the, to my username:group.

Umm... Would you mind translating that into English? How do I let "'apache' the user" write? And what is "chown'ng"? Does it require protective headgear or a license of some kind?

Posted 1 year ago #
susan
Member

This is what I'm getting:

Warning: copy(/home/xxxxx/public_html/index.php.wpau.bak) [function.copy]: failed to open stream: Permission denied in /home/xxxxxxx/public_html/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 have no idea what to do. I tried EVERYthing posted here. Nothing works. Please help me. I just want to upgrade to 2.6.3.

Thanks!

Posted 1 year ago #
dermod
Member

This is the most frustrating example of the reputation of a great plugin being destroyed by sloppy follow-up and a miserable lack of attention to the detail necessary to make people happy when using it. Upgrading is a panicky procedure - and if it goes wrong it's awful.

Because there appear to be so many people on this thread offering different suggestions and no one seeming to provide any different answers, I'll just offer what I did that worked.

Like most people here, I had "permission denied" errors when trying to enter maintenance mode. I fixed it by ensuring that the FTP path had a trailing slash. That's it.

instead of /pub-html I put /pub-html/

Duh.

Posted 1 year ago #
matt-thorn
Member

dermod, I couldn't agree more with your first paragraph. But I'm not sure what the final "Duh" meant. I don't think you are impugning the intelligence of those of us who have still not succeeded, since at least two of us have pointed out that the solution you offered (and which had been suggested earlier) did not work for us. Like Susan, I've tried every suggestion offered in this thread, and have even tried them in various combinations, to no avail. Since the creator of the plugin obviously has nothing more to say on the subject, I have decided to give up on it and perform the upgrade manually. Too bad, because, as you point out, this is (or should be) a great plugin. As I said before, I'm just glad I encountered this problem before donating any money to the creator. If he can't muster the enthusiasm to help his users, then I doubt the plugin has much of a future.

Posted 1 year ago #
susan
Member

Matt,
Did you do it? Upgrade manually? How did it go? I'm too scared to do it!!!

Posted 1 year ago #
stoptheinsanity
Member

I fixed this WPAU situation fairly easily.

First I had to deal with the FTP Permissions and how to format them:

FTP Username format I used was:
myusername@myblog.com

FTP Host:
myblog.com

FTP Folder
My blog is my website therefore the index.php file is modified a little and is in the root directory. Specifically in my case the index.php is located is /var/www/html/ but the WordPress files and directory structure are in /var/www/html/wordpress/.

The index.php modification is the last line of code telling the index where the files are located. If your site was running fine, then this shouldn't be a worry.

Here's the code for the index.php if it's one level up:

/** Loads the WordPress Environment and Template */
require('./wordpress/wp-blog-header.php');
?>

The reason WPAU couldn't set my site into maintenance mode was that I had moved the file index.php out of the /wordpress/ directory and up one level. I did not leave a copy of index.php in the wordpress directory.

The workaround should be a permanent fix. I simply COPIED the index.php out of the root directory (/var/www/html/) and into the /var/www/html/wordpress/ directory. Then WPAU worked flawlessly (one note - I didn't actually open a new browser tab to verify that the public saw the maintenance mode message.)

After running the upgrade I checked that BOTH index.php files were in their respective locations. They are. I compared the content. The WPAU must modify the index.php in the /wordpress/ directory and tell it that the path is now the normal path for all files, etc. But it left the one in the root directory alone. And I left them both alone. I didn't do my normal housekeeping and clean up the extra index.php file.

Bottom line - Web browsers see the first level index.php, but WPAU looks for one in the /wordpress/ directory. So unless something hinky happens I am leaving this alone.

Flawless upgrade...

Posted 12 months ago #
TKen
Member

stoptheinsanity: YES! That was it for me too. My blog is my website, and I did not have the index.php file in the WP directory, just in the public root. Copying the index.php to the WP directory did the trick! (It's always been this way, why the WPAU didn't work this time I don't know.)

Posted 11 months ago #
stoptheinsanity
Member

That is interesting because WPAU has worked before without any issues on my site as well. All of a sudden it didn't. I thought I must have imagined that it worked seamlessly.

Wonder what happened?

BTW, did you get a reminder to clean up old files?

Posted 11 months ago #
matt-thorn
Member

I'm glad to see that stoptheinsan and TKen were able to fix their problems, but unfortunately their situation does not apply to me.
susan, no, I haven't tried the manual upgrade yet. Like you, I'm afraid of what might go wrong, and the directions are not exactly simple.
I just continue to be disgusted that the author of this plugin, after starting this thread, has not written a single response despite the fact that may of us have yet to resolve this problem.

Posted 11 months ago #
stoptheinsanity
Member

Matt;

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.

I found this file in my Wordpress folder, but it is listed as owned by vuser, i.e. me. If you view it with your site manager it is simply the backup copy that WPAU makes of your index file. It should be attributed to you, the owner. I would see nothing wrong with deleting the file.

As to your situation not being the same as mine and TKen's, what is different? Is it that your site is not in the root folder? If not, is it possible that you installed wordspress to a sub folder and moved the index.php file up one level above that? If that is the case, it would seem that it is essentially the same as my case.

Posted 11 months ago #
matt-thorn
Member

Thanks, stoptheinsan. I fixed the problem with file permission a while back. (For some reason, file permissions occasionally get screwed up, but I was able to fix them by using my domain host's online file manager.

My blog is not my site, but rather a directory on my site. (http://matt-thorn.com/wordpress/). The index.php file is also in that directory, and there is no other copy anywhere else.

Posted 11 months ago #
stoptheinsanity
Member

Matt;

Next time you might try, before using WPAU, putting a copy of your index.php like this... http://matt-thorn.com/index.php.

BTW, I like your site, clean, relevant, researched...

Posted 11 months ago #
gynciuz
Inactive

My solution for "Maintainance mode error" was adding "/" to input '/public_html/' in the beggining of upgradeing process.

I hope it will help for someone! Cheers!

Posted 11 months ago #
gynciuz
Inactive

My solution for "Maintainance mode error" was adding "/" to input '/public_html/' in the beggining of upgradeing process.

I hope it will help for someone! Cheers!

Posted 11 months ago #
gynciuz
Inactive

My solution for "Maintainance mode error" was adding "/" to input '/public_html/' in the beggining of upgradeing process.

I hope it will help for someone! Cheers!

Posted 11 months ago #
Sanwal
Member

i m getting the below error:

Warning: copy(/home/j4jumpy/public_html/index.php.wpau.bak) [function.copy]: failed to open stream: Permission denied in /home/j4jumpy/public_html/wp-content/plugins/wordpress-automatic-upgrade/wpau_upgrade.class.php on line 362
We could not complete the upgrade please try again later, click here to check the logs.

Posted 4 months ago #
Sanwal
Member

any replies....

Posted 4 months ago #
gaiageek
Member

I ran into this problem of the upgrade not being able to put the site in maintenance mode when upgrading from 2.7.1 to 2.8.1. I had Wordpress Automatic Upgrade version 1.2.5 already installed. I tried changing the folder permissions with no luck. Ultimately what worked, following a tip from another user above, was deleting the Wordpress Automatic Upgrade plugin (in Wordpress), uploading it new (even though it was the same version), activating it and running it again. If you're previously upgraded Wordpress using WPAU, I recommend trying this. It seems maybe something was damaged from the previous upgrades.

Hope this helps someone. Good luck.

[ earth | technology | life ] - http://www.gaiageek.com

Posted 4 months ago #
ravichauhan02
Member

http://sizlopedia.in/

Posted 4 months ago #
jorchav
Member

Hello,
Ran into this problem I neither understand nor know how to fix:

Task Name: files
Task Description: Backs up all the current files from the wordpress installation
Task Status: Failed
Task Start Date: 2009-08-02 12:12:02
Task End Date: 2009-08-02 12:12:02
Task Log:
...
(final log reading)
Adding File /home/*******/public_html/blogsite/wp-includes/feed-rss.php to /home/*******/public_html/blogsite/wp-includes/feed-rss.php
Could not archive the files PCLZIP_ERR_READ_OPEN_FAIL (-2) : Unable to open file '/home/*******/public_html/blogsite/wp-cron.php' in binary read mode

How can I fix that and get on with the update?
Thanks!

Posted 3 months ago #
dsgncr8or
Member

Task Name: maintmode Task Description: Puts the site into maintenance mode Task Status: Failed Task Start Date: 2009-08-03 18:46:32 Task End Date: 2009-08-03 18:46:32 Task Log: Putting the site into maintenance mode /******/wp-content/plugins/wordpress-automatic-upgrade Copying /******/index.php to /******/index.php.wpau.bak The file was successfully copied Moving the maintenance file to root ERROR -> Could not put the site into maintenance mode

Suggestions - this is during an upgrade attempt from 2.8.2->2.8.3

Posted 3 months ago #
Kristofer
Member

Nothing new here - I get the same problem as most people here:

Task Name: maintmode Task Description: Puts the site into maintenance mode Task Status: Failed Task Start Date: 2009-08-04 23:24:35 Task End Date: 2009-08-04 23:24:35 Task Log: Putting the site into maintenance mode /home/web25259/domains/domainname.com/public_html/wp-content/plugins/wordpress-automatic-upgrade Copying /home/web25259/domains/domainname.com/public_html/index.php to /home/web25259/domains/domainname.com/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

I have really tried to keep file and folder permissions to 777, but haven't succeeded with the upgrade yet. Anyone got tips on where I can add the forward slash at the end of the path to my root folder? Like so:

/home/web12345/domains/domainname.com/public_html/

After I have given the path once (when I first gave this plugin acces) I can't find where to change it?!

Posted 3 months ago #
jorchav
Member

Hello,

This appears to be a systematic error. WPAU has failed to upgrade three of my blogsites in succession. The final log entry is the same:

Adding File /home/xxxxxx/public_html/blogsite/wp-includes/feed-rss.php to /home/xxxxxx/public_html/blogsite/wp-includes/feed-rss.php
Could not archive the files PCLZIP_ERR_READ_OPEN_FAIL (-2) : Unable to open file '/home/xxxxxx/public_html/blogsite/wp-cron.php' in binary read mode

Any suggestions? Anyone?

Posted 3 months ago #
jorchav
Member

Hello,

Now I have four (4) blogsites in need of updating. The problem is the same:

If that does not solve your problem please post on the forum and I will definitely take a look at the issue.Below is the log for the upgradation
Task Name: files
Task Description: Backs up all the current files from the wordpress installation
Task Status: Failed
Task Start Date: 2009-08-09 14:52:47
Task End Date: 2009-08-09 14:52:48
Task Log:

Creating files backup archive at wpau-files-bak-ExFatxkD.zip

...
Adding File /home/*******/public_html/blogsite/wp-includes/feed-rss.php to /home/*******/public_html/blogsite/wp-includes/feed-rss.php
Could not archive the files PCLZIP_ERR_READ_OPEN_FAIL (-2) : Unable to open file '/home/*******/public_html/blogsite/wp-cron.php' in binary read mode "

Is this forum being monitored? I see questions but no recent answers...

Should I be looking elsewhere for a reliable upgrade plugin??

jorchav

Posted 3 months ago #

RSS feed for this topic

« Previous 123 Next »

Reply »

You must log in to post.