WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Windows server infinite redirect after upgrading to 3.1 (99 posts)

  1. AardvarkGirl
    Member
    Posted 3 years ago #

    Yeah but I'd hardly call using a plug-in a fix, more like a band-aid.

    Whats going to happen when they fix this bug and you have the plug in installed(?). :-(

  2. robanna
    Member
    Posted 3 years ago #

    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.

    http://apexprd.org/
    http://indiantree.apexprd.org/
    http://foundation.apexprd.org/

  3. mikemsi
    Member
    Posted 3 years ago #

    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: http://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 http://gpdionline.com/wp-login.php... it's not going to to the "site" subdirectory.

    If it put in: http://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!

  4. hereswhatidid
    Member
    Posted 3 years ago #

    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.

  5. mikemsi
    Member
    Posted 3 years ago #

    Thanks for the reply.

    Tried it... didn't work.

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

  6. marcomc
    Member
    Posted 3 years ago #

  7. krispy_b
    Member
    Posted 3 years ago #

    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.

  8. Cristescu Bogdan
    Member
    Posted 3 years ago #

    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!

  9. AardvarkGirl
    Member
    Posted 3 years ago #

    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.

  10. hereswhatidid
    Member
    Posted 3 years ago #

    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.

  11. AardvarkGirl
    Member
    Posted 3 years ago #

    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. :)

  12. RevJar
    Member
    Posted 3 years ago #

    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?

  13. Samuel Wood (Otto)
    Tech Ninja
    Posted 3 years ago #

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

  14. RevJar
    Member
    Posted 3 years ago #

    @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.

  15. scythe944
    Member
    Posted 3 years ago #

    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 http://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.

  16. rvirtue
    Member
    Posted 3 years ago #

    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.

  17. swhitley
    Member
    Posted 3 years ago #

    Thank you for the plugin band-aid! Worked for me.

  18. zymotik
    Member
    Posted 3 years ago #

    I'm having the same issues on a fresh install and a upgraded site.

    IIS 6, Windows Server 2003, PHP5.

    I will use the band-aid (http://wordpress.org/extend/plugins/permalink-fix-disable-canonical-redirects-pack/) plugin for now ;)

    pluggable.php, line 987, constant redirect @ function wp_redirect

    Thanks guys and girls.

  19. Samuel Wood (Otto)
    Tech Ninja
    Posted 3 years ago #

    @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.

    Okay... Create a mu-plugins directory. Then put it in there. :)

  20. Samuel Wood (Otto)
    Tech Ninja
    Posted 3 years ago #

    Especially with no up-front acknowledgement and warning that it's needed.

    If we had more testers who had their sites running the betas on Windows platforms, maybe the problem wouldn't be in there.

  21. zymotik
    Member
    Posted 3 years ago #

    It's weird, because I'm sure its been working fine the past couple of days on 3.1. Only today did I get an issue?! It was a fresh site.

  22. jamesisin
    Member
    Posted 3 years ago #

  23. jivesamba
    Member
    Posted 3 years ago #

    I was also having the issue of the front end of my wp site throwing a 301 (too many re-directs error) after upgrading from 3.0 to 3.1. The backend (admin) of my site was still functioning correctly.

    I took the advice of @jarnez from earlier in this thread and installed this plugin:
    http://wordpress.org/extend/plugins/permalink-fix-disable-canonical-redirects-pack/
    and it solved the problem.

    Thanks!

  24. rvirtue
    Member
    Posted 3 years ago #

    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.

  25. RevJar
    Member
    Posted 3 years ago #

    Our site is back up, but I can't log in to the the Dashboard still. Any suggestions for that?

  26. Drawer
    Member
    Posted 3 years ago #

    Otto, are you actually BLAMING Windows people that this is happening? As if anyone said they needed Windows testers...

    I wonder if anyone will acknowledge that maybe this was released too soon. I won't touch it til Windows problem is fixed.

    Signed, Proud to be Windows WP blogger.

  27. esmi
    Forum Moderator
    Posted 3 years ago #

    There have been a number of appeals for testers. Perhaps you just weren't listening at the time. However, there's nothing to stop you helping out with beta testing from now on, is there?

  28. Drawer
    Member
    Posted 3 years ago #

    And I'm not listening now, Esmi. How rude.

  29. RevJar
    Member
    Posted 3 years ago #

    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?

  30. Daniel King
    Member
    Posted 3 years ago #

    @scythe944 "but I don't know why you wouldn't have access to the dashboard, as everyone else with this problem has been able to. "

    I'm having the same problem RevJar does, I can't access Dashboard.
    Using the mu-plugins it's a very good idea in order to use the band-aid solution.

    @revjar: Before I upgraded, I backed up files and database. It took me only 30' to restore WP to 3.0.5 and I had no problems at all. I think it would be the same to you

Topic Closed

This topic has been closed to new replies.

About this Topic