ID: 14797 Comment by: [EMAIL PROTECTED] Old Reported By: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Scripting Engine problem Operating System: Windows 98 SE PHP Version: 4.1.0 New Comment:
Martin, Did my suggestion work for you? Where you missing the drive letter? -Garth Previous Comments: ------------------------------------------------------------------------ [2002-01-07 14:07:01] [EMAIL PROTECTED] From: Garth Dahlstrom <[EMAIL PROTECTED]> Subject: Re: PHP Bug #14797 == #14563 Date: Mon, 07 Jan 2002 2:36:45 EDT I did some work trying to figure this out using FoxServ off of sf.net... I can recreate the bug when I don't prefix my DocumentRoot with the drive letter... DocumentRoot "C:\apache/htdocs" # no error DocumentRoot "/apache/htdocs" # error I find it odd that they both work on my machine provided I don't provide an include_path and the syntax of the include_path can lack the drive letter and work just fine. (i.e. include_path=".;/apache/includes" is ok as long as the Docroot in httpd.conf has a C:\ in it) Wondering if you can verify this result... It may be just a matter of PHP not using C:\ as a default drive after 4.04 or something... -Garth Northern.CA ===-- http://www.northern.ca Canada's Search Engine ------------------------------------------------------------------------ [2002-01-06 06:30:33] [EMAIL PROTECTED] From: Garth Dahlstrom <[EMAIL PROTECTED]> Subject: PHP Bug #14797 == #14563 Date: Sat, 05 Jan 2002 13:15:45 EDT Martin, Indeed you have the same bug I have, I don't have a Win98 system so I could not comment on whether or not it was for all of Win32 when I opened 14563. I downgraded my set-up to a copy of PHP 4.04, and found your statement regarding versions before 4.05RC1 to be true also... setting my include_path = ".;/apache/includes" fails with the same error, however setting include_path to ";.;/apache/includes" works properly. Wondering if this workaround would work after 4.04 on Win2K, I upgraded my PHP version back up maintaining the same PHP.ini from 4.04... The workaround doesn't work on 4.06, 4.08, 4.1.0, or 4.1.1. They have closed my bugs as being bogus and I can't post into your bug to describe these findings, so if you could post this message into Bug #14797, maybe it would be helpful in keeping you bug alive. I am thinking of building a mini-distribution of Apache+PHP (4.04 + 4.06 + 4.1.1) to see if I can help more folks reproduce it. Regards, -GED Northern.CA ===-- http://www.northern.ca Canada's Search Engine ------------------------------------------------------------------------ [2002-01-02 08:58:27] [EMAIL PROTECTED] With PHP Version 4.0.5RC1 an inlude-path set to ";.;./;" it works with SAPI, but with 4.0.6 and newer it's the same like 4.1.0 Martin ------------------------------------------------------------------------ [2002-01-02 08:30:47] [EMAIL PROTECTED] Hello, I can't run PHP Version 4.1.0 under Windows 95/98 4.10, there are massive problems when I try to include a file: Server API CGI -------------- - It's possible to set the include-path in php.ini. - Scripts without any include statement work well. - include statements with a relative path work. - include statements with an absolute path do not work, there is the following error: Failed opening '/foo/test.php' for inclusion Server API Apache ----------------- - It is not possible to set the include-path in php.ini to an other value than "". If I do, there will be everytime the same error: Failed opening 'foo/index.php' for inclusion (include_path='.;/foo') in Unknown on line 0 - If I set the include-path in php.ini to "" and in a script with ini_set("include_path", $new_inc_path) to the desired path, then php shows the same behaviour like "Server API CGI" - only relative paths work. I think this could be the bug #11612 or #14563, bit I don't use Win2k, I'm using Win 98 SE. Martin ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=14797&edit=1 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
