This is a really weird one, and I'm actually not even sure what the solution is, but it feels like something that should be looked at.
We've been trying to figure out why some photos are failing to move from Arc into our print CMS (CCI CuePrint). We isolated it to being something about specific images that were causing the failure, and just today we think we found the cause. We're pretty sure that the issue is photos that have a file extension as one file type but in actuality are a different file type altogether.
For example, one story published fine in Arc and works fine on the site. However, it never made its way into our print CMS. We found that the failure point was a single photo. When looking at that photo, we discovered that even though it ends with .jpg, it's actually a .png. Our print CMS apparently doesn't like this and it's rejecting the entire story.
Even the photo API is getting faked out. When we do a GET to the photo endpoint, the type is returned as image/jpeg. If you download the image from Photo Center and run the command line utility "file," though, you can see its real file type: .jpg
Obviously the photo should never have been named a .jpg in the first place, and we don't yet know how that happened, but I'm wondering if there should be some sort of check upon file upload to try to prevent this sort of thing from happening so that one file type isn't masquerading as another.
Can you think of anything we can do to prevent this issue in the future, or at least identify problem photos like this one so we can try to filter them out for the print CMS?
Britton Peele
