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

You seem to regard Windows usage as some kind of an exotic departure from “normal” expectations. For many potential WP users it’s anything but that.

If the end product’s usage on Windows/IIS platforms is intended and supported, a default installation test on one or two such platforms would hardly seem to be an “unreasonable” expectation of its developers, or anything like testing on “every conceivable platform.” I do it myself and I’m just a “core team” of one single person.

On the other hand, if such usage is not intended and supported, you should say so clearly up front. That’s all. Pretty simple really.

On the other hand, if such usage is not intended and supported, you should say so clearly up front.

you are the king of ad-homs – I never said that

let’s be honest here – every single software that runs php/mysql has and still does have problems with windows – not just wordpress – and windows has to to be tweaked/configured to do the job apache/’nix does out of the box and you seldom ever get the same functionality

i’ve been using wordpress since 1.5.something and windows users have always had problems

i’ve been installing php/mysql software of all varieties for over 6 years now. i install on all sorts of platforms and hosts. i always end up having to charge more for windows installations because of the extra time spent configuring things to work correctly.

this is all i have to say on this – i encourage you to take esmi’s suggestion and help us test – and get as many other windows users as possible, also – this will definitely help reduce these types of problems in the future

I never said that you did say that. It was an “either/or” comment conditional on whether Windows/IIS platform support is intended or not. If it is, it really needs some minimal pre-release testing. If not, it should be so stated up front.

Anyhow, if my input is now being taken as some kind of “ad-hom” attack, I suppose it’s best for me to bow out at this point. Thanks for your attention. I’m sure it’ll get straightened out at some point. In the meatime this Disable Canonical Redirects plugin provides one possible workaround that solved the problem for me pending a proper fix.

Clearly one issue here is there’s among users a lot of different levels of knowledge and understanding of how WP works. My request was not intended as a mean-spirited gripe against developers, to whom I’m really thankful. But there should be an understanding that a lot of us have no idea how to fix some of the issues caused by upgrades. Hence, my request for some type of warning about what’s gonna change/be affected.

In my case, my homepage was quite screwed up after the upgrade and I’m at a stage I can’t spend time figuring out what was wrong. So I decided to lay off the updates for a while. I guess I’ll go back to performing them later this year, when I find the time.