Windows server infinite redirect after upgrading to 3.1

Great! Glad to hear your problem is solved.

Actually, based on the above-mentioned bug ticket, it looks like WP 3.1.1 will be turning off canonical redirects for IIS entirely. But that interim solution should handle the issue okay until then.

With Permalink Fix & Disable Canonical Redirects Pack
the login with form on home doesn’t work…

Looking at the discussions under Trac, this isn’t going to be fixed by 3.1.1

I too am having this issue after upgrading to the latest version. We are running ISS. I am able to access the admin area however when trying to access the site there is an infinite loop. I do not want to use a plugin to fix this issue so I downgraded to the previous version. I won’t be upgrading to this version again.

I am struggling with this. I am trying to set up a new wordpress site. no upgrades. i have set up the wordpress locally on my computer using MAMP and the 3.1 download worked fine. Now I have installed wordpress on the hosting server I use. This is the schpeel they give about the platform that I chose

“The Linux Web hosting packages offer a feature full development platform based on CentOS Enterprise Linux, Apache Web server and supporting PHP and Perl.

The Linux Hosting plans are served from fully clustered and load balanced state-of-the-art HP DL 380 Dual Xeon servers. Running CentOS Enterprise Linux, the platform offers stability, performance and reliability”

I don’t really know what this all means but after I installed wordpress, then logged in I get redirected to the front end home page. I cannot navigate from this page so cannot install any plugins / fixs. I tried the code hint from @rvirtue: to edit the canonical.php file and that has not done anything. I don’t know what else to do?

Should I just install a previous release of wordpress and if so which version. I want to use the menu feature in the admin and the fullscreen theme by graphpaperpres and the simpleviewer plugin. Any tips would be greatly appreciated.

Troubleshooting WordPress 3.1 – Master List

with such a critical flaw, im kinda surprised they havent pulled this version from the dl page or at least surrounded it with the dire warning it so badly needs. talk about sabotage. ??

I’m shocked myself, antioch. I don’t think there’s ever been a version with this many problems ever – esmi, feel free to correct me on this – and I think a warning is essential and the minimum, to save so many people valuable time and hours of worry.

Yet, nothing.

I noticed that when activating the plugin fix that it broke the links in my archives. They read “/page/2” instead of “/2011/page/2”, for example. After updating the canonical.php file as @rvirtue mentions, all was fine.

The patch worked except now my RSS feeds are broken. So I suppose I have to decide if I want RSS or broken archive links.

Upgrading to a nightly build of WordPress solved my headaches. Thank you awesome WordPress devs.

was having similar issues with the banditgear.co.uk
site upgrade to wordpress, now fixed thanks to all suggests

Thank god for this forum! Disaster averted!

I wonder if this post about running wordpress on windows server and issues of permalink structure explains what was happening in 3.1 for us sites hosted on Windows Server.
https://www.3plains.com/support/wordpress-on-a-windows-server/

the plugin fix worked on my site but I look forward to the 3.1.1 when this is fixed more permanently.

I wonder if offering to beta test would be wise in my case where I am pretty amateur in my knowledge of these things and our site is the only WordPress site of its kind being hosted on our Windows server almost for free (a nonprofit network administrator for public libraries in Massachusetts).

I do hope testing on Windows Servers is more carefully considered in future versions.

well if there arent any windows beta testers, one can hardly fault the developers for releasing something that completely kills sites on windows boxes.

however, continuing to dish out this sabotage on the download page without so much of a warning, and after so many weeks, is utterly mind boggling. given all the hours it continues to waste, one might even say that it borders on contempt. ??