Incorrect APP1 Exif Identifier Code in Exif->readExifTags()

could you attach the image you were using when getting the error. it could help to know if it it Drupal module, drupal or php module (.so)

same here on 7dev....not always though

this happens when some software used some specific identifier(s) not present in the specification of iptc or exif. To correct it, I need the file which raise the error and the 'semantic' of the field you want to use.

here is the image...the samantic fields im using are :
iptc_object_name
iptc_caption
iptc_credit

the image is here:

http://ablevision.tv/PentagonPapers_Kins.jpg

thanks. I should take a look as all of them are in the spec (and in the supported list of this module !).

I am sorry bit I can not do anything for you as this is a warning raised by the apache exif module and is not linked to the code of this module. This is working at the maximum capacity of the chosen platform (apache/php) :).

ok thanks but is there a suggestion as to the platform config of exif?

No, there is no special configuration. The only thing to do is to update to last php version (with last exif extension) and hope it manage more field. Note that the field you are using ARE correclty managed. The warning message is due to another field.

The warning message is due to another field.

you mean another definition is firing anyway? could it be xmp? i do get the message that:

XMP library is not available SXMP library is not available
Functions SXMP are not available on the system. XMP metadata will not be extracted.

thanks!

I have added a try-catch block around the exif_read_data() function so it now is handled without breaking and just leaves an entry in the watchdog instead.

As most users don't care about things that the exif library can't figure out, it makes sense to suppress warnings.

Patch to do this attached.

This is a problem created by bad data. However, the module should handle these errors and not allow them to be displayed. I recommend either silently hiding the errors (#11) or at record a message that there was a problem (#10, once cleaned up).

I suggest setting the error handler to catch E_WARNING messages, that'll record a watchdog message; see #2266413: "Incorrect APP1 Exif Identifier Code" for suitable code.

integrated in last 7.x branch.