3.0.3 automated upgrade fails

So we know this

1) Running an automated update somehow ‘changed’ the permissions on files, forcing Tony to have to enter his IIS credentials.
2) Copying the files up manually DID NOT engender this problem.

I think Frumph’s on to something. It could be that the copy from the temp folder where WordPress stashes its files for an update/upgrade (which is wp-content/upgrade on linux, and I thought the same on Windows…) is copying the files up with bad ACLs.

That’s a PHP copy, right? Perhaps there was a minor update to the version of PHP you’re running? I’d scan the server log and see if anything’s updated PHP in the last 30 days (or if you can pinpoint the LAST time you ran an automated install/update, since then).

This would also explain why Akismet went away. The new files can’t be accessed by iis. I would look at the acls on those files in comparison to those on another plugin.

Maybe as with nix there’s setting for the default rights used on newly created files…

On nix, when the upgrader starts having a huffy princess day, I generally delete the update folder and recreate it as 777. I don’t know what the equivalent of that is for IIS, but it’s worth a shot.

lol

s/he/she/

Apologies, Ipstenu! I knew that I really did, but I think the half-elf rogue threw me. I started thinking of Tanis Half-elvin and all was lost from there.

Love the hat either way!

So… here’s the latest.

Got the message that there was a security flas in 3.0.3 yesterday. Figured since I still had the backup I made prior to the manual install of 3.0.3 I would try the automated update…what the heck?

The autmated update to 3.0.4 worked perfectly just as all other updates have in the past (except for 3.0.3).

And to my surprise, Akismet was now present as well. And there is no longer any prompt for IIS Admin Credentials when accessing the Plugins link on the WP Dashboard.

However, Akismet also now says that there is an update available for it. I am a little hesitant in trying that but again… what the heck? I am now taking a snapshot of the server and as soon as it is done I will try the Akismet automated update.

Things may just be looking up

When trying to WordPress Autoupdate, make sure that you FIRST:

0. Delete the Upgrade folder completely from your server
1. Go into your Plugins page
2. Click the checkbox above all of them to select ALL plugins
3. From the pulldown, select DEACTIVATE, then OK it
4. Try the update again – that usually takes care of the errors for me.
5. Don’t forget to re-enable your plugins as in Steps 1-3

Thanks Jpneok. However, as I stated I was successful updating from 3.0.3 to 3.0.4 with the automated update and in the process it fixed the issue with Akismet.

I just attempted the automated update of Akisment from 2.4.0 to 2.5.1 but it failed again. However, this time when I downloaded 2.5.1 and manually copied the files to the Plugins\Akismet folder it updated successfully and is working properly.

Cheers!! ??

Yeah – it’s weird tony.. I’ve no idea..

I officially declare IIS ‘hinky’ and sentence it to being an annoyance in my life. *grumble*

Um, I think my message may have to be moved to a different thread. But no being sure, I need to rely on the forum hosts (sorry!) to take care of it.

I got to this page trying to find out why my old blog from Windows Spaces was no longer accessible.

Most of what I’m reading here sounds like stuff that technicians do, or even programmers. I am neither. I just want to know where 3 years of blogging made off to and how to get it back.

Thanks.

@nobodyzsukey

There may be some information in these articles.

windows live spaces shutting down

https://en.blog.wordpress.com/2010/09/27/welcome-windows-live-spaces-bloggers/

WordPress.com and Windows Live partnering together

https://ma.tt/2010/09/msn-spaces-closing-becomes-wp-com/

from now i’ve to check with server before upgrade, it might be safety way
great topic ^^

sooooooooooooooooooooooooooooo frustrating to FINALLY get a site migrated to a new server…. then try YET ANOTHER upgrade…. and have it fail…

now i’ve got “page not found” errors all over the place and will spend the next couple hours trying to get this running!!!

starting to wonder why i keep trying w/ WP….. they seem to work so hard at making it difficult!

GRRRRRRRRRRRRRRRRRRRRRRR

yeah… I just tried the latest auto update to 3.1.3 and once again it failed with the following:

Downloading update from https://www.ads-software.com/wordpress-3.1.3.zip
Unpacking the update
could not copy files
Installation Failed

Where and what permissions should I be looking for?

I found that error_log was commented out in the php.ini. I edited it to write create error_log.txt. I attempted an outmatic update to 3.1.3 again and the following was written to the newly created error log.

[24-Jun-2011 07:06:02] PHP Warning: copy(C:/wordpress/wp-admin/includes/update-core.php) [function.copy]: failed to open stream: Permission denied in C:\wordpress\wp-admin\includes\class-wp-filesystem-direct.php on line 200

Any help with this would be greatly appreciated.