#9673 [Bgs]: Relative paths in require(), require_once(), include(), include_once()

ID: 9673 User updated by: vvo at geocities dot com Reported By: vvo at geocities dot com Status: Bogus Bug Type: Scripting Engine problem Operating System: RedHat Linux PHP Version: 4.3.2 New Comment: That's ok, I gave up on PHP a long time ago. RTFPHPM yourself. Previous Comments: ------------------------------------------------------------------------ [2004-04-20 06:21:34] cameron at prolifique dot com No, not necessarily a bug...just a very illogical and painful behavior for the include & require functions when using relative paths. It's like having a compass that points north in relation to wherever you started your trip, not where you're standing now. Not much use. If you knew where you started, why would you need a compass? If a relative include path isn't relative to the script calling it, what's the use of a relative include path? I never expected that the hardest part of moving from ASP to PHP would be include file references, but considering this behavior (still happening in 4.3.4), it appears to be. Luckily, there appears to be a workaround: [2 Sep 2003 8:48am CEST] mathieu dot messe at urssaf dot fr A workaround found at http://fr.php.net/manual/fr/function.include.php is to use require(dirname(__FILE__) . "\..\second.php"); ------------------------------------------------------------------------ [2004-04-05 08:50:44] sniper@php.net RTFM. There is no bug here. ------------------------------------------------------------------------ [2004-04-02 16:03:57] chapwest at hotmail dot com I have no idea what this means in regard to my sight. Michael ------------------------------------------------------------------------ [2004-04-01 18:36:07] iliaa@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2004-04-01 18:32:42] vvo at geocities dot com setting version to 4.3.2 ------------------------------------------------------------------------ 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/9673 -- Edit this bug report at http://bugs.php.net/?id=9673&edit=1