Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
Topic closed
exif being destroyed or mutilated?
It appears that after an image is uploaded through Textpattern’s interface, many EXIF fields become empty or are changed into odd values…
For example, the camera Model field is empty, and so is FNumber. MaxApertureValue and ApertureValue are changed to f1, and UserCommentOld (where my copyright should be) is empty.
An example of such output can be seen here. Healthy output can be seen here.
Note that in the ‘unhealthy’ output, it shows
[Errors] => 10I am absolutely sure that this loss of data is not because of how I save my images— I’ve tested various methods, and have seen when all EXIF data is lost; however, this type of loss only seems to happen after I upload via TXP.
Is there a bug in the code? Is it a side-effect of how TXP uploads/saves an image?
I want my FNumber back!
Edit: OK, this is getting weirder and weirder. This morning I uploaded an image through TXP, and TXP assigned it the name 127.jpg. In the ‘unhealthy output’ page, I reference the file with it’s proper URL: http://lumilux.org/images/127.jpg. For the ‘healthy output’ page, I downloaded the image from the TXP /images/ directory, uploaded it via SFTP to the same directory as the EXIf-reader file, and referenced the file as 127.jpg. The one in the TXP images directory looks like it’s broken, but when I download it and reupload it, it seems fine.
Last edited by Hans (2006-01-22 15:34:07)
Lumilux – A Photoblog
Offline
Re: exif being destroyed or mutilated?
Well, uh, I guess this post should be moved. There’s a bug in exifer that causes it to read the EXIF data weirdly if the image isn’t in the same directory as the exif-reading script. Case closed!
Lumilux – A Photoblog
Offline
Pages: 1
Topic closed