Do you have "Grum Plugins Classes.3" installed & active?

-- Geoff

to understand the problem, I need an example of the photo producing the error message: I think there's something not recognized in the metadata and to understand why, having the photo will help me.

I get following:

Notice: Undefined offset: 1 in /home/romancos/public_html/plugins/AMetaData/JpegMetaData/Readers/XmpReader.class.php on line 668

Notice: Undefined offset: 1 in /home/romancos/public_html/plugins/AMetaData/JpegMetaData/Readers/XmpReader.class.php on line 668

Warning: Cannot modify header information - headers already sent by (output started at /home/romancos/public_html/plugins/AMetaData/JpegMetaData/Readers/XmpReader.class.php:668) in /home/romancos/public_html/include/page_header.php on line 105

not only error message appears but also css is corrupt and full image not loading in the lightbox.

Last edited by romancos (2012-08-07 10:47:04)

Hi,

I just tested to upload some images with the ApertureToPiwigo plugin and was looking into the results and found these photos throwing an error:

http://www.yogie.de/picture.php?/78/category/13
http://www.yogie.de/picture.php?/83/category/13
http://www.yogie.de/picture.php?/84/category/13
http://www.yogie.de/picture.php?/86/category/13
http://www.yogie.de/picture.php?/88/category/13
http://www.yogie.de/picture.php?/91/category/13
http://www.yogie.de/picture.php?/93/category/13
http://www.yogie.de/picture.php?/94/category/13

I guess that it has something to do with the "Copyright" information as the tab to show the EXIF shows just:    seq, Array

But it would be nice to eliminate the PHP error messages on top and to leave the meta data empty if it is not possible to just display it!? I've checked the difference between the other images that do not throw the error. The copyright field is just empty and the ones with the error are containing my first and last name but without any special character just a blank to divide the names.

Cheers
Yogie

Last edited by Yogie (2012-08-09 06:13:57)

Here we have a different problem.

In XMP format you have 2 things:
- the content (the value)
- the container (the identifier of the the content)

The first example you gave me was a problem about the content: it was not correct, the format was not good according to XMP specification.


Here it's another problem: the container is not correctly defined, according to XMP specification.

The corrupted information is the markup dc:right container, set as SEQ (sequential array) instead of ALT (alternative array).

I think it's possible to do something for this kind of problem.
I've updated the feature [Bugtracker] ticket 2720 to take it in account.

I'll have some time in september, so I'll try to fix this kind of problem in september.

mmh..

in fact, I've found some time this afternoon, a new version will be released very soon ;-)
I've tried to manage kind of case you gave me and try to improve code about other malformatted values (unknown case... ^_^), but I can't tell if it will work each times something wrong will happen with uncorrect metadata.

grum wrote:

mmh..

in fact, I've found some time this afternoon, a new version will be released very soon ;-)
I've tried to manage kind of case you gave me and try to improve code about other malformatted values (unknown case... ^_^), but I can't tell if it will work each times something wrong will happen with uncorrect metadata.

You are a hero! :-) Your modifications are successful I have updated to your last release and the error has been gone, the EXIF data is showing correctly as it should. Many, many thanks! You rock!

Last edited by Yogie (2012-08-13 06:17:01)