google.com/trislawdlatior…

The file was successfully copied
Moving 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

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?

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.

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.

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!

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.

Can anyone help me with this?

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