• Resolved Gabe Shackle

    (@hereswhatidid)


    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.

Viewing 15 replies - 31 through 45 (of 98 total)
  • I’m having a problem with sub-domainss on an IIS server after the upgrade. The main domain work perfect but the subdomains gets an error on ever page but the main pages.

    The page isn’t redirecting properly
    Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
    * This problem can sometimes be caused by disabling or refusing to accept cookies.

    https://apexprd.org/
    https://indiantree.apexprd.org/
    https://foundation.apexprd.org/

    Redirect problem here too, but I can’t even access admin control to fix. This is a site under construction, so it was in a “site” subdirectory. If I go to: https://gpdionline.com/site/wp-login.php I get the login fields without formatting. When I put in login info, I get “page cannot be found” at https://gpdionline.com/wp-login.php… it’s not going to to the “site” subdirectory.

    If it put in: https://gpdionline.com/site/wp-admin.php it still gets “page cannot be found”.

    Is there a change that I can make at the database to point everything back to the “site” subdirectory?

    ANY ideas would be appreciated!

    Thread Starter Gabe Shackle

    (@hereswhatidid)

    Not sure if this is the best way to do it but you could try adding this line to your theme’s functions.php file and see if it temporarily fixes the issue:

    remove_filter(‘template_redirect’, ‘redirect_canonical’);

    Basically disabling the canonical redirects which I believe are the real culprit behind the redirect loop people are experiencing.

    Thanks for the reply.

    Tried it… didn’t work.

    I guess it’s time to start over. Damn.

    While the ‘fix’ works, I’m still waiting for a bug release before I dare put 3.1 on any other of my websites.

    I’m not sure what the process is, but when will there be any official recognition of this issue? Is it effecting everyone with WP on windows server?

    I’m trying to post where I see “install 3.1 it’s great” warning people that they may want to hold fire if they have a windows server/hosting. also giving the plugin name as a temp fix.

    I rename the W3 Total Cache plugin and the issue was fixed for me!

    Im able now to access dashboard and I dont receive an infinit loop ar other error!

    krisby_b – I am with you.

    People keep saying it is a plug-in or something… well I have a 100% brand new fresh, full install of 3.1 on the same server I had the 3.1 updates on (but other wise have had flawless fresh installs and auto updates of all previous versions since I started using WP pre-version 3.X) that has tanked as well.

    I can’t get a fresh install to work and I get the infinite look – no tampering with this install.

    Thread Starter Gabe Shackle

    (@hereswhatidid)

    It definitely is not related to just a plugin. I had the same experience AardvarkGirl had with a completely fresh install still generating the infinite loop on a Windows server.

    hereswhatidid – oh thank gawd, someone said they had the same problem, hehe. ?? Now I don’t feel crazy. I started a thread for a FRESH INSTALL but didn’t see that anyone else posted to it.

    It would be nice if someone would create a post that says “Yes, there is a problem, we are aware and are working on it, just hang tight”. ??

    I spent a good amount of time restoring a client’s website to version 3.0.5 yesterday. But hard lesson learned.

    1. Run any future updates on our test site FIRST ??
    2. Back up the database to my computer (it is far easier than fishing the back up off the server)
    3. Make sure I have the previous version install files with a list of all plug-ins

    It’s ok though. ??

    I got the Permalink Fix & Disable Canonical Redirects Pack uploaded via FTP. However, I still can’t gain access to the Dashboard to enable the plugin. Any advice how to do this would be greatly appreciated?

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    @revjar: Move the plugin’s php file into the mu-plugins directory. Everything in mu-plugins is automatically active.

    @otto – I don’t have a mu-plugins directory. The only directory I have is \wp-content\plugins. I tried putting it there and no luck.

    I got the Permalink Fix & Disable Canonical Redirects Pack uploaded via FTP. However, I still can’t gain access to the Dashboard to enable the plugin. Any advice how to do this would be greatly appreciated?

    You mean that you can’t access the dashboard by visiting https://www.yourdomain.com/wp-admin?

    I guess you could always try creating the mu-updates folder and putting the plugin in there, but I don’t know why you wouldn’t have access to the dashboard, as everyone else with this problem has been able to.

    AardvarkGirl said: “oh thank gawd, someone said they had the same problem”

    You’re definitely not alone. The infinite loop redirect problem arises with fresh DEFAULT installs on Windows/IIS platforms. And I have three (3) such platforms to prove it.

    AardvarkGirl also said: “Yeah but I’d hardly call using a plug-in a fix, more like a band-aid.”

    Right about that too. Especially with no up-front acknowledgement and warning that it’s needed.

Viewing 15 replies - 31 through 45 (of 98 total)
  • The topic ‘Windows server infinite redirect after upgrading to 3.1’ is closed to new replies.