ID: 21674
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Bogus
Bug Type: *URL Functions
Operating System: Cobalt RAQ4 Apache/Linux
PHP Version: 4.3.0
New Comment:
That depends on one's definition of a bug. In this case, the erroneous
message given by php would defintely be considered a bug, in my
opinion.
Its the analougous to one calling the fire department and saying "come
now, my house is on fire" when, in fact, one's nextdoor neighbor has
burned his bar-b-que ribs.
If the affliction is related to a permissions or authority issue, then
the message should state so. The error message should not be one that
makes mention of of a "file or directory not found" when, in fact, the
file or directory does exists.
Cheers.
Previous Comments:
------------------------------------------------------------------------
[2003-01-16 18:28:44] [EMAIL PROTECTED]
So it turns out that this is not a bug in PHP :)
------------------------------------------------------------------------
[2003-01-16 18:17:58] [EMAIL PROTECTED]
I may have debugged the problem. Actually, the problem is more of a
very bad Error Message than a functionality issue.
Specifically, my script's end result is to create a dynamic page
(index.html) the web root path/directory from which the script is
executed and in which the index.html file is to be written to was did
not have "w" write permissions.
So instead of PHP stating that it could not write to
/home/sites/site3/web/ due to an authorization issue it sent:
Warning: main(lang.php) [function.main]: failed to create stream: No
such file or directory in /home/sites/site2/web/IV/config.php on line
97
Warning: main() [function.main]: Failed opening 'lang.php' for
inclusion (include_path='') in /home/sites/site2/web/IV/config.php on
line 97
Warning: main(extras.php) [function.main]: failed to create stream: No
such file or directory in /home/sites/site2/web/IV/config.php on line
98
Warning: main() [function.main]: Failed opening 'extras.php' for
inclusion (include_path='')
Which is grossly misleading and only sends one off on a "wild goose"
chase.
Thanks.
------------------------------------------------------------------------
[2003-01-15 23:29:05] [EMAIL PROTECTED]
The script worked like a charm prior to upgrade to php 4.3.0
------------------------------------------------------------------------
[2003-01-15 23:27:01] [EMAIL PROTECTED]
What do you mean when you say that my include_path is empty?
------------------------------------------------------------------------
[2003-01-15 23:25:35] [EMAIL PROTECTED]
Your error is from include not require, are you sure this is the
correct code? Require is fatal; something is fishy here.
------------------------------------------------------------------------
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/21674
--
Edit this bug report at http://bugs.php.net/?id=21674&edit=1
