Just a thought: Couldn't you have included a warning for 3.1?

For many, many people, myself included (2 sites) the auto-upgrade went as other upgrades in the past had – very quickly with no problems what-so-ever.

16 sites upgraded so far – one had a modest problem
after extensive beta testing – how would we know what to warn about?

Ok, maybe this amount of trouble is to be expected and in the big picture is not relevant.

Just a thought for all the people who filled the first page of this forum with 3.1 issues.

Extensive beta testing?! Are you serious? The infinite loop redirect issue occurs even with a brand new fresh default installation on a Windows/IIS server. And I have THREE (3) Windows server set-ups to prove it!

In any case, pending a proper fix, now that the problem has been made abudantly clear, A PRIOR WARNING IS DEFINITELY IN ORDER — preferably right on the download page.

Upgraded about 10 sites this morning. Had a minor display issue on one due to the Admin bar but the theme is positively ancient. I pretty much expected this and fixed in in about 20mins.

No update process is ever 100% successful across all users on all platforms. If you can get 90% or above, you’re doing pretty well. All told, I’d guestimate that the failure rate for 3.1 is still well below 10% – which ain’t bad.

well I must admit most testers stay away from windows servers because of problems with many things other than wordpress – but still, yes extensive testing was done
again – with all the testing – what would we warn about?

In that case, if your product is untested on any Windows/IIS platforms and/or not intended for use thereon, that should be made clear up front.

In that case, if your product is untested on any Windows/IIS platforms

I didn’t say that – untested – it’s just not anywhere near as faithful a platform as apache/’nix – so that’s what most people use – so please don’t put words in my mouth

personally, I don’t even get why you would run a windows server unless you had a dedicated .asp site or ran Crystal, etc. – such a pain

@rvirtue: Why not help out then by testing future beta versions?

@esmi – I think rvirtue would say he is. ??

@esmi – I think rvirtue would say he is. ??

sort of late – after the fact, eh?

Actually, I do my own dev work and cross-platform compatibility testing on several platforms, Windows/IIS being only one of them. In any case, denegrating and blaming any user’s platform choices is NOT an answer, neither for myself nor for many others as quite evident here.

The question is simply whether WP supports the Windows/IIS platform (including its own appropriate pre-release cross-platform testing) or not and, either way, the answer should be clearly stated up front.

It is if people are complaining that “3.1 broke stuff on <foo> platform” but never once tried testing any of the pre-release versions on a non-production site themselves. The time for bug-fixing and/or complaining was during the preceding months… and months… of beta testing. It’s completely unreasonable to expect a small group of core developers to try and test everything on every conceivable platform. That’s what beta and RC versions are released for and it’s where the active involvement of the wider WordPress community is vital if the % failure rate is to kept as low as possible.

The problems extend well past Windows/IIS platforms. My Ubuntu/Apache site had been through numerous automatic upgrades dating back to well before 3.0. Even the 2.x to 3.0 auto update went smoothly.

The 3.1 upgrade splattered it and it’s still down. Attempts at manual upgrades have also failed, and I’ve found nothing in these forums that has been helpful. It was running the latest version of the Atahualpa theme, so it can’t be blamed on an “old” theme.

I’m about to try a fresh 3.1 install and I guess I’ll rebuild the site by picking all the old articles out of the database backups by hand.

This is truly ugly, and has severely lowered my confidence in WordPress as a platform. I have another half dozen sites to deal with, but they’re going to stay on 3.0.5 until I’m absolutely sure I understand what’s going so terribly wrong.

Fixing this appears not to be much less work than moving to a whole new platform. The WordPress folks really should have a tutorial page somewhere with a step-by-step how-to on doing a forensic manual restoration.

I’ll report back if I learn anything useful doing the rebuild.

Samuel B

well I must admit most testers stay away from windows servers because of problems with many things other than wordpress

The small company I work for has 4 servers all running Windows – the bulk of programming done here is custom ColdFusion. I’m the only ‘non programmer’ here and have been the one to bring WordPress into our shop and promote it to clients who can’t afford custom programming. I’m not a server tech person either. I don’t have much say in the server set ups.

I will say I am really growing to love WordPress so much so that I changed my personal website from ColdFusion to WordPress just so I could get to know the product on a more intimate level.

I applaud every who puts their all into this product, all the plug-in developers etc.

But I suspect my boss would give me the hairy eyeball if I suggested maybe we get a non-windows based server just for our WordPress sites. :-O My bosses hubby is an IBM veteran… so I doubt there is much hope for me to petition, but I suppose I could try. :-\

If someone wants to point me in the direction of an article that gives WordPress’ best platform, I’ll put it under my bosses nose for consideration, but I can’t sell that argument myself.