The return false part is ok but why not showing the warnings from fopen?
marcus
At 13:16 05.12.2002, John Coggeshall wrote:
Here's the patch (again, this makes all getimagesize() failures return
false instead of some of them returning NULL, and turns off error
reporting if the file fails to
The return false part is ok but why not showing the warnings
from fopen?
Well, the issue here is in the bugreport... It's not an issue of PHP
throwing a warning when a file doesn't exist and is attempted to be
opened, but it was throwing the error if the filesize was zero.. I could
see that
At 13:34 05.12.2002, John Coggeshall wrote:
The return false part is ok but why not showing the warnings
from fopen?
Well, the issue here is in the bugreport... It's not an issue of PHP
throwing a warning when a file doesn't exist and is attempted to be
opened, but it was throwing the error if
Marcus Börger wrote:
From my point of view accessing a file should result in an
error if the file cannot be opened or in case of
GetImageSize() a file operation cannot be executed. For
example i would expect GetImageSize() to show an error if the
information cannot be retrieved due to
From my point of view accessing a file should result in an
error if the file cannot be opened or in case of
GetImageSize() a file operation cannot be executed. For
example i would expect GetImageSize() to show an error if the
information cannot be retrieved due to file corruptions.
I
At 03:02 PM 12/5/02 +0100, Tit \Black\ Petric wrote:
From my point of view accessing a file should result in an
error if the file cannot be opened or in case of
GetImageSize() a file operation cannot be executed. For
example i would expect GetImageSize() to show an error if the
