Req #36160 [Opn->Bgs]: include/require ../ relative to current script

Edit report at http://bugs.php.net/bug.php?id=36160&edit=1 ID: 36160 Updated by: johannes@php.net Reported by: ovdspek at liacs dot nl Summary: include/require ../ relative to current script -Status: Open +Status: Bogus Type: Feature/Change Request -Package: Feature/Change Request +Package: *General Issues Operating System: * PHP Version: 5.1.2 Block user comment: N Private report: N New Comment: This works as designed and documented. Previous Comments: ------------------------------------------------------------------------ [2006-01-25 23:31:55] ovdspek at liacs dot nl Last sentence of your quote: If filename begins with ./ or ../, it is looked only in include_path relative to the current working directory. ------------------------------------------------------------------------ [2006-01-25 23:30:12] tony2001@php.net Maybe we're looking to different docs? ----- Files for including are first looked in include_path relative to the current working directory and then in include_path relative to the directory of current script. E.g. if your include_path is ., current working directory is /www/, you included include/a.php and there is include "b.php" in that file, b.php is first looked in /www/ and then in /www/include/. If filename begins with ./ or ../, it is looked only in include_path relative to the current working directory. ----- (c) http://php.net/include ------------------------------------------------------------------------ [2006-01-25 23:09:04] ovdspek at liacs dot nl The fact that the documentation says it's not (it says it's only relative to the current working directory). ------------------------------------------------------------------------ [2006-01-25 23:06:38] tony2001@php.net What makes you think it's not relative to the current script? ------------------------------------------------------------------------ [2006-01-25 22:59:22] ovdspek at liacs dot nl It's not. And if you're sure it is, could you update the documentation? ------------------------------------------------------------------------ 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/bug.php?id=36160 -- Edit this bug report at http://bugs.php.net/bug.php?id=36160&edit=1