Edit report at https://bugs.php.net/bug.php?id=80478&edit=1
ID: 80478
Updated by: cmb@php.net
Reported by: rg at mejoramos dot com
Summary: exif_read_data(php80D2.tmp): Process
tag(xE6FA=UndefinedTag): Illegal format
Status: Open
Type: Bug
Package: EXIF related
Operating System: Windows
PHP Version: 7.4.13
Block user comment: N
Private report: N
New Comment:
May make sense to introduce exif.ignore_warnings, similar to
<https://www.php.net/manual/en/image.configuration.php#ini.gd.jpeg-ignore-warning>.
Previous Comments:
------------------------------------------------------------------------
[2020-12-04 17:25:42] cmb@php.net
Doc update: <http://svn.php.net/viewvc?view=revision&revision=351876>.
------------------------------------------------------------------------
[2020-12-04 16:38:33] rtrtrtrtrt at dfdfdfdf dot dfd
> Right. exif_read_data() is normally used together with error suppression
sane code *never* should need error supression
------------------------------------------------------------------------
[2020-12-04 16:31:33] rg at mejoramos dot com
>>> Right.
Then my participation finish here.
Many thanks by your time team PHP.
Regards, and happy 2021
:-)
------------------------------------------------------------------------
[2020-12-04 16:21:40] nikic@php.net
Right. exif_read_data() is normally used together with error suppression (@), unless you
specifically want to debug why some EXIF results are missing or similar. Warnings from this
functions are generally harmless, as long as you still get back a result.
Maybe this should be documented though?
------------------------------------------------------------------------
[2020-12-04 16:12:51] rg at mejoramos dot com
>>> disable your error handler
The police in company is
"NO HIDDEN ERRORS / PREVENT ERRORS"
>>> Silence the exif_read_data() call using the @ operator
ah!,
then becouse exist this option, my report:
[NO'T is a BUG]
true?
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=80478
--
Edit this bug report at https://bugs.php.net/bug.php?id=80478&edit=1