I’m getting an infinite redirect loop after upgrading from 3 to 3.1. I’m running this on a Windows machine using the ISAPIRewrite module from Helicon. The permalinks were working fine prior to the upgrade and I’ve already tried resaving them via the admin and restarting IIS on the machine in case anything was being cached.
If we had more testers who had their sites running the betas on Windows platforms, maybe the problem wouldn’t be in there.
Possibly not and I can certainly understand that we all screw up now and then, certainly including yours truly. On the other hand, when a version update modifies a wp_redirect() function that involves a specific “if($is_IIS)” exception, wouldn’t you expect testing the results on the platform involved to be a normal part of the developer’s own revision process? Sure seems like there’s been a significant oversight this time around.
Anyhow, all I’m really saying, now that the issue has been clearly identified, is that some up-front acknowledgement and workaround posting might be a good idea to avoid more problems until a proper fix can be worked out.
What do you think of the odds of going back to 3.0.5 would break the site again? That was the last version of WordPress that worked fine for us. I’m still not able to log into the Dashboard. Can I make things any worse?