From:             [EMAIL PROTECTED]
Operating system: Win2k
PHP version:      4.1.2
PHP Bug Type:     *General Issues
Bug description:  include path in the module version, using sub dir as php causing 
error 

after I upgrade to 4.1.2 from 4.1.1 the php module version of Apache
stop working
all my working php script would throw an error

Warning: Failed opening 'path_of_the_script' for inclusion
(include_path='c:\php4\pear') in Unknown on line 0

even the one that doesn't require the use of include or require
function. In fact one of the script only have phpinfo() in it.

I've try to play around with the include_path however this make no
different.
I add my comment to a bogus post and also a Analyzed post so I thought I
would post it again

Anyway I move to the cgi version and get it to work fine, however I found
another bug, when I use a sub directly with the name php immediate after
the webroot any php page in that directly then Apache will throw a not
found error

Not Found
The requested URL /php/test.php was not found on this server.

I check in the log and this is what I found
[Wed Mar 20 10:37:18 2002] [error] [client 192.168.1.101] (2)No such file
or directory: script not found or unable to stat: c:/php/test.php

It seem to me that because I name the directory php, somehow it confuse
php and it start to pick up the page from c:\php which is where I install
php and not from the webroot.
-- 
Edit bug report at http://bugs.php.net/?id=16186&edit=1
-- 
Fixed in CVS:        http://bugs.php.net/fix.php?id=16186&r=fixedcvs
Fixed in release:    http://bugs.php.net/fix.php?id=16186&r=alreadyfixed
Need backtrace:      http://bugs.php.net/fix.php?id=16186&r=needtrace
Try newer version:   http://bugs.php.net/fix.php?id=16186&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=16186&r=support
Expected behavior:   http://bugs.php.net/fix.php?id=16186&r=notwrong
Not enough info:     http://bugs.php.net/fix.php?id=16186&r=notenoughinfo
Submitted twice:     http://bugs.php.net/fix.php?id=16186&r=submittedtwice

Reply via email to