#27891 [Com]: Bad behavior of require() function and relative paths with IIS

ID: 27891 Comment by: david_amer at yahoo dot co dot uk Reported By: faraco dot phpbugs at mailnull dot com Status: No Feedback Bug Type: IIS related Operating System: win32 PHP Version: 5CVS, 4CVS (2005-06-19) New Comment: I was having the same problem so i tryed the latest build as sugested in the previous post, it still isnt working unfortunatly. Previous Comments: ------------------------------------------------------------------------ [2005-08-07 01:00:03] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2005-07-30 15:29:05] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-05-17 22:54:53] faraco dot phpbugs at mailnull dot com The problem persists. ------------------------------------------------------------------------ [2005-05-17 16:46:44] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-05-16 22:34:47] faraco dot phpbugs at mailnull dot com Another way to explain the problem... Following de example above: 1. when I require 'lib/functions.php', the file is first looked in my domain document root ['docroot/lib/'] and then in my actual path ['subroot/lib'] because if I delete the first directory, the same script finds the second directory; 2. Yes, my 'include_path' is set to '.'; 3. Again, ISAPI Caching is disabled. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/27891 -- Edit this bug report at http://bugs.php.net/?id=27891&edit=1