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 7 replies - 31 through 37 (of 37 total)

  • I just upgraded to 2.5.1 and my site appears and displays okay, but when I try to access the wp-admin, it shows a blank page. Has anyone else experienced this or have any ideas on how to fix this?

    Thanks,

    Gaboinked!

    inkyneil, Have you upgraded to 2.5.1? Does that work without a fix or is the fix still needed and does it still work? I also have Brinkster but am hesitant to upgrade wordpress unless I know I can get my site working again.

    Thanks,
    Rebecca

    redredrose:

    I just upgraded to 2.5.1 and I do use Brinkster as well. inkyneil’s solution worked.

    However, the problem I encountered was that I could only use the default permalinks. Any other setting does not work.

    Anybody have any ideas on how to get permalinks using date and time to work with Brinkster?

    jmorale9:
    you can’t use pretty permalinks with Brinkster Windows IIS. You’d have to their Linux server.When I talked to support, they said they could transfer my account to Linux. Even then, there are tweaks to be done. Here’s a link I found that explains how to tweak it. Not so easy to tweak. Instead, I’m switching hosts at the end of the month. (YEAY!) I don’t find Brinkster very WordPress friendly.

    I just did a fresh 2.5.1 install on my Windows server, and the warning-problem is fixed. There is however still a problem with finding the right path, as wordpress apparently cannot find my themes.
    When I click on the login link I’m being sent to
    https://halinagold.net/?step=2/wp-login.php
    which doesn’t exist.

    You can view the testblog at
    https://www.halinagold.net/test251

    I’m getting exactly the same as helinagold with a clean 2.5.1 install today. I started a post on it before I found this one
    https://www.ads-software.com/support/topic/175652?replies=4

    I just did a fresh install of 2.6 and exactly the same problem is still there: No error messages, but WordPress can’t find the right paths, so the theme and the links don’t work correctly.

    As I’m apparently not being supported in continuing with a Windows server the obvious solution seems to move my blogs to another domain that’s on a Linux server.
    I could do that but it would presumably cost me lots and lots of traffic since these blogs have been around for a few years and I’ve been referring to them many places.

    Unless… is there a way to make a general redirect (on a Windows server!) so that every time someone clicks https://www.domain1.com/oldblog/post-url they will be re-directed to https://www.domain2.com/newblog

    Another solution would be leave the old blog as is (and block for comments there) and simply continue with a new blog on a Linux server…

    What do you think?

    Your help is much appreciated –

    Halina

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