EXIF Issue

[dhdesign]

I had posted about this issue with version 1.5 in this thread (http://forum.pixelpost.org/showthread.php?p=43810#post43810) a few days ago (my post is the last one). I patched exif.php with the fix listed in this thread (http://forum.pixelpost.org/showthread.php?t=5221&highlight=EXIF+data), and it fixed the ISO problem. I even installed the EXIF to database addon to see if it would clear the flash info problem, but that didn't help.

I've done a clean install of v1.6 with no problems whatsoever (so far, at least), but am still having this same issue with the ISO and flash info not displaying correctly for images where I've added the author info and copyright info into the comments field in image properties.

Here is the link (http://www.kpdesign.net/blog16/index.php?showimage=1) to an image with the correct ISO and flash info (I haven't added anything into the image properties on this one).

Here is the link (http://www.kpdesign.net/blog16/index.php?showimage=2) to an image with the ISO and flash info not displaying properly (I've added author info/comments into the image properties for this image). You can see that the ISO is showing as "4456608", and the flash as "fired", even though no flash was used.

My install is still using exifer1.5. I have not patched exif.php on it, as I'm still testing. I also have not activated the option to put the EXIF info into the database.

Would it at least be possible for the devs to patch the exif.php file within exifer1.5 in the PP v1.6 download package to fix the ISO problem permanently?

Also, any ideas on what can be done to resolve the issue with the incorrect flash info being displayed when author info and comments are added to the image properties?

Thanks in advance! :)

[Dennis]

Ok first things first: you're right about patching the exif.php file. We should look in to that. But exifer is a third-party script and not maintained by us.

The Exif to database addon is NOT suitable for 1.6. Pixelpost 1.6 has his own routines for saving the exif info to the database. So do NOT use this addon for 1.6.

Could you send me some files for testing purposes? One with author info and one without?

Basically we're having more and more problems with exifer. Perhaps we should think about finding (or writing) a new routine.

[dhdesign]

I wasn't going to install the EXIF to database addon to my v1.6 install, because I thought there was already a way to activate this function within the admin area. I haven't activated that option yet, as I wanted to see how the EXIF data would behave first.

You can save both images that I've linked to in my first post, and use those for testing. The horses image has the extra info added (author info/copyright info in comments), but the farmer's market image does not have anything added, just the regular EXIF data from the camera.

If that doesn't work, send me a PM with your email addy, and I'll send both images to you via email.

Thanks! :)

[Dennis]

Ironically most problems with this beta is with a third party script :(

[LightDarkKevin]

I have not had a chance to try the 1.6 beta yet, but I was wodering if someone could post the EXIF values that are available in 1.6.

I also use EXIF to store longitude and latitude data, and I am hoping that 1.6 will support this. I'd rather not do any database hacking if I don't need to.

[Dennis]

The new GoogleMap will support those tags. Normally Pixelpost won't use those tags. They are however saved in the database.

[dhdesign]

Ironically most problems with this beta is with a third party script :(
Yes, I know. :(

Let me know if you were able to save those images down from my blog, or whether I need to email them to you.

Thanks for everything! :)

[Dennis]

With the images you provided me, and with the updated exif.php (see this thread: http://forum.pixelpost.org/showthread.php?t=6317) this issue has been fixed.