ID: 16047 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: *Configuration Issues Operating System: Windows 2000 PHP Version: 4.1.2 New Comment:
I think someone else got the core of this issue and described it in more technical terms in Bug #15865 Sorry about the duplication, I did search before submitting, however I didn't find Bug #15865 until I browsed all the bugs for version 4.1.2 Thanks (so I guess you could close this, if the other one will get fixed) ! Erik Previous Comments: ------------------------------------------------------------------------ [2002-03-13 16:28:05] [EMAIL PROTECTED] Hi, Just drove my self crazy upgrading to the latest build for win32 4.1.2, as an apache module Granted I'm not very confident as to how this *should* work, I think I found a minor bug/inconsistency. If you do not set include_path it defaults to C:\php4\pear (or was it c:\php4\includes\pear ) I believe based upon reading this, " include_path string Specifies a list of directories where the require(), include() and fopen_with_path() functions look for files. The format is like the system's PATH environment variable: a list of directories separated with a colon in UNIX or semicolon in Windows. Example 3-3. UNIX include_path include_path=.:/home/httpd/php-lib Example 3-4. Windows include_path include_path=".;c:\www\phplib" <b>The default value for this directive is . (only the current directory)</b>. " So... I'm guessing it should default to "." instead of C:\php4\pear (or whatever) ... All of the includes on my site went bunk right after I upgraded... setting include_path = "." rectified this for me. If this is obvious, and the intended effect, I apoligize in advance for my erroroneous bug report. Erik ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16047&edit=1