Support » Installing WordPress » 2.5 Problem Fixed, Now I’m Scared

  • Hey All,

    Through a process of elimination I was able to track down a problem with my upgrade to 2.5 (running on a Windows XP Pro box and IIS out of my home). I am not a coder or skilled with scripting languages in any way shape or form, so my grasp of just what I have done is meager at best and I’m worried about potential consequences.

    After running the upgrade script I was unable to reach the admin page. I would get errors regarding “Undefined index: PATH_INFO” in wp-settings.php. I scoped out that file and noticed that there were a couple of “else” statements set up as a fix for IIS that included the PATH_INFO statement. I remarked them out and everything has since been running like a top. The block of code I remarked out was as follows:

    //	else
    //	{
    		// Some IIS + PHP configurations puts the script-name in the path-info (No need to append it twice)
    //		if ( $_SERVER['PATH_INFO'] == $_SERVER['SCRIPT_NAME'] )
    //			$_SERVER['REQUEST_URI'] = $_SERVER['PATH_INFO'];
    //		else
    //			$_SERVER['REQUEST_URI'] = $_SERVER['SCRIPT_NAME'] . $_SERVER['PATH_INFO'];
    //
    		// Append the query string if it exists and isn't null
    //		if (isset($_SERVER['QUERY_STRING']) && !empty($_SERVER['QUERY_STRING'])) {
    //			$_SERVER['REQUEST_URI'] .= '?' . $_SERVER['QUERY_STRING'];
    //		}
    //	}

    Have I found a bug in this version of WordPress, managed to fix a problem anomalous to my system, or stuck my foot in a big ol’ bucket of something that may come back to bite me later? Any input from those folks who actually know what they’re doing (or at least know what I’m doing) would be greatly appreciated.

    Uncle Andrew

Viewing 15 replies - 1 through 15 (of 37 total)
  • Thanks for posting this. I was going to ask about this myself, but since it’s working for you I thought I’d give it a shot and what do you know.. it works like a charm! Hopefully this will be one of the areas covered in the 2.5.1 release…

    Ah 2.5.1 :p…

    sacredpath

    (@sacredpath)

    Automattic Happiness Engineer

    I’m waiting for 2.5.87 myself.

    You know, I really can’t imagine what convinced me to be an “early adopter” in this particular case….I don’t habitually gravitate towards the very first release of something. Perhaps it was the siren song of self-installing updates. Whatever it was, other than this one hitch it seems to be working just fine. The new Dashboard is going to take some getting used to, though….kinda fugly, IMHO.

    Uncle Andrew

    Thanks I was having the same problem–and I know next to nothing about php. blocking out that code worked for me too…

    Yep, worked here too! Thanks for that!

    THANK YOU.

    This was driving me nuts, because the error causes the page to trigger a “this page cannot be displayed” message in IE7. At least, I think this was the culprit…

    Okay, now my main page comes up but all links return this error:

    “bad server response” (NSURLErrorDomain:-1011)

    That can’t be good. 🙁

    I commented out lines 58 through 83 of wp-settings.php and everything seems to be working for me now.

    Thanks

    I had the same problem and actually could solve it with the fix above, but after that my NextGEN Gallery didn’t work anymore so it would be nice to actually get some pointers in what should the line “PHP Notice: Undefined index: PATH_INFO in C:\Inetpub\wwwroot\wp02\wp-settings.php on line 72” contain. I’m also using IIS so obviously something is missing. Thought about “going back” to the old WordPress but the whole database update scares me to start that whole battle!!!

    Thankfull for any tips or tricks on this error.

    Cheers
    Peter

    Peter,

    I also have NextGEN Gallery and am using IIS. Blocking out the code above doesn’t seem to have affected the Gallery for me. Have you upgraded the NextGEN Gallery with the latest? It was updated just after 2.5 was released.

    I think I have my install of 2.5 working correctly now.

    What I did was compare the wp-settings.php files from the 2.3 install and the 2.5 install. I noticed there is a line of code in the section regarding the PATH_INFO stuff we’ve been discussing that is present in 2.3 but absent in 2.5. When I added it back in, my pages now load in IE7.

    This may be a better solution than commenting out the offending code.

    Okay, scratch that.

    The fix above does solve the issue with IE7, but it breaks the admin dashboard (messes up the linking to edit posts, etc.)

    There is a bug ticket on how this was playing out in WP 2.3 (see below) but I haven’t found anything more recent about how this is working (not working) in WP 2.5. The trac systems won’t let me log in to create a new bug ticket. (Yes, I’m registered.)

    here’s that bug ticket, in case any one is curious:

    http://trac.wordpress.org/ticket/5160

    Perhaps someone with success posting a bug to the trac system could just let them know that the “undefined index” error is not theoretical

    Could one of you with IIS create a test.php file and run this for us?
    <?php var_dump($_SERVER); ?>

    Post that along with your IIS version number in the various problem threads you have. You can leave out the bits that seem to be giving away too much info to you.

    See, very few people run IIS, so nobody really gets to test it on that server. It’s hard to know what to code because, well, IIS kinda sucks. Different versions behave differently, and nobody knows what the stupid server variables are on different versions.

    Of course, the simple fix is obvious: Switch to Apache.

    “See, very few people run IIS, so nobody really gets to test it on that server. It’s hard to know what to code because, well, IIS kinda sucks. Different versions behave differently, and nobody knows what the stupid server variables are on different versions.

    Of course, the simple fix is obvious: Switch to Apache.”

    I don’t think glib excuses to defects in your code due to your own lack of testing are appropriate. Either you support IIS or you don’t. If you do, then a bit less condescension in light of your admitted less-than-rigorous testing and the resulting coding errors might be better received.

    Just sayin’

Viewing 15 replies - 1 through 15 (of 37 total)
  • The topic ‘2.5 Problem Fixed, Now I’m Scared’ is closed to new replies.