[New Smug] Re-uploaded images not getting EXIF
amycham
Registered Users Posts: 7 Beginner grinner
When I upload a new file for an existing image, the data is not updating. Not sure if this is some sort of caching lag, but some have been in for over an hour and are not showing camera/Exif data. This is significant because they don't sort by date without their data, and weddings are weird to flip through if they are out of order. :cry
0
Comments
Please check out my gallery of customisations for the New SmugMug, more to come!
DayBreak, my Folk Music Group (some free mp3s!) http://daybreakfolk.com
Now change your Lightroom SmugMug publishing settings to include All Metadata. Right click on the first of the two photos you published, and click "mark to republish", then hit the "publish" button to reupload just that photo. Over on SmugMug, notice that the photo still has no metadata showing, though the image filesize has increased slightly:
Conclusion: Lightroom republish using the SmugMug plugin fails to update image EXIF data.
Now, export the second photo you published from Lightroom as a JPEG to your computer, this time including All Metadata. Browse over to your SmugMug page, click the Tools button for that second photo, and select Organize > Replace. Choose the JPEG that you exported from Lightroom with full EXIF data.
When I returned to my gallery, I noted that the file size and dimensions of the image had been updated to the new version I exported from Lightroom, but the EXIF data remained stubbornly empty:
Conclusion: "Replace Photo" feature inside SmugMug fails to update EXIF of replaced photo.
Now in Lightroom, remove both of those photos from the gallery and publish. Then add them back again, and publish. Once the upload is complete, you'll note that this time the photos correctly show full EXIF data!
Conclusion: SmugMug is capable of showing EXIF data for these photos, but the two methods of Replacing a photo are incapable of refreshing the EXIF data.
Please check out my gallery of customisations for the New SmugMug, more to come!
In my case, I'm just uploading the images again with the native (web-based) uploader and indicating that duplicates should be overwritten rather than skipped.
My guess is that when an existing file is overwritten, either the database is not getting hit with the metadata--and it just overwrites the image files--or we're getting old data from the CDN or some kind of cache. I'm guessing it's the former, as I would imagine a CDN or cache would have updated by now.