ID: 24053
Comment by: unknown at yabbse dot org
Reported By: jphey at netdoor dot com
Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Linux 2.4.20
PHP Version: 4.3.2
New Comment:
This is not bogus, I've seen it causing a lot of problems.
Here's a better example. Let's say someone tries to use an avatar on a
forum, and the forum decides to check if that avatar is immensely
huge.
Before, getimagesize would work fine.
Now, it generates a warning - effectively requiring a @ before the
getimagesize, and making previous versions of the forum simply not
work. (the error handler will catch the warning and die.)
-[Unknown]
Previous Comments:
------------------------------------------------------------------------
[2003-06-09 19:10:54] kriek at jonkriek dot com
I had to form absolute paths out of my relative ones.
------------------------------------------------------------------------
[2003-06-06 15:43:01] admin at 1000rpm dot net
I don't think this should have a bogus status. Have a search for the
error message on google, tons of sites are getting this error. It's
pretty urgent, I'm already getting customers complaining.
------------------------------------------------------------------------
[2003-06-06 15:37:51] admin at 1000rpm dot net
What about non-local files? The error still comes up for those...
------------------------------------------------------------------------
[2003-06-06 01:48:56] [EMAIL PROTECTED]
Don't include local files via http://..., use the correct path.
------------------------------------------------------------------------
[2003-06-06 01:41:34] jphey at netdoor dot com
My web hosting provider says the problem is merely that "error logging
was set to all" and by changing that, the warning messages disappear.
So perhaps this is not a bug, but an intended behavior.
Still, I don't know why such a warning would be issued when no call to
fseek had been made.
------------------------------------------------------------------------
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/24053
--
Edit this bug report at http://bugs.php.net/?id=24053&edit=1
