asked on

Problem with require('./wp-blog-header.php'); The ./ is throwing a 500 error message.

Problem with require('./wp-blog-header.php'); The ./ is throwing a 500 error message.

I am running on a Windows 2008 server, 64 bit, with IIS7.

You can see my php info at http://www.greatersba.org/php-info.php

I have a Wordpress installation, that I discovered this issue in. But the problem doesn't seem to be a Wordpress issue, it seems to be more of a PHP on Windows issue.

For some reason, in the information I found (when looking around) the use of ./ is supposed to tell PHP to look in the "currrent folder" for the file that is being called, as in require('./wp-blog-header.php');

But, with the ./ in front, I always get a 500 error. Even if I put just a / I get a 500 error.

I would like to fix this if possible so it would work normally, but since I am on a Windows 2008 server with IIS7 .. I am not sure how to get this to work properly. Most of what I see on the net refers to Linux servers.

Can someone explain why it's not working properly on my Windows server .. and what I might be able to do or change (somewhere) so this will work (without my having to remove the ./ in front of the file name??

Thanks,
Gary

ASKER CERTIFIED SOLUTION

Gary Dewrell

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

njcuwebsupport

ASKER

I guess, what I'm trying to also figure out is .. can I do anything on my windows server, change something, etc., so if code is written this way, that it would just work (even though the Windows server "may not need it". It took me forever to debug that this was the problem and I'd simply like to have my Windows server set up in a way that this type of coding in PHP wouldn't throw a 500 internal server error.

Let me know.
Gary

jrm213jrm213

There are a couple of possibilities in this thread that you should look into. People with the same issue of relative paths work in subdirectory but not in root, and they are all using iis7 with php applications.

http://www.webmasterworld.com/php/3685216.htm

1. I'm not sure if this only applies to ASP/SSI, but IIS6 (not sure about 7) does have a "parent paths" option. If you select your websites and go to the Scripts Configuration menu, under the options tab "Enable Parent paths" is an option.
2. I ran into this problem, too; giving the anonymous IIS user permissions to the parent directory fixed it.

njcuwebsupport

ASKER

Thanks again!

njcuwebsupport

ASKER

jrm213jrm213

Please see the new posting I just put up.

Sorry, I clicked to fast and applied the points to the wrong person.

Just resubmit your answer again.

:(
Gary