ID: 18721 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: No Feedback Bug Type: PHP options/info functions Operating System: FreeBSD 4.6 PHP Version: 4.2.2 New Comment:
No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2002-10-04 11:19:13] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-08-03 04:52:09] [EMAIL PROTECTED] As the title says, when there is a non existent path specified in include_path, activating open_basedir will generate the warning Warning: open_basedir restriction in effect. File is in wrong directory in "xxxxxx.php" on line XX This warning will not appear if the invalid path does not start with a slash. e.g. include_path = ".:asdf/asdf:/usr/local/lib/php" will not produce warning when open_basedir is enabled but will produce warning when include_path = ".:/asdf/asdf:/usr/local/lib/php" note the /asdf/asdf is the non-existent path. I understand that by removing the non-existent path, the error will be gone, however I think the warning should not have appeared especially when it complains about open_basedir and not about the include_path itself which will cause confusion. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=18721&edit=1
