Image Gallery
factasy - January 6, 2008 - 16:47
Hi
I have problem with my Image Gallery at http://www.factasy.com/civil_war/image
When someboby submit a photo to my site with jpg will not the Image Gallery not do a tumbnails of it but if the user submit a photo with gif the Image Gallery work fine and do a tumbnail of the photo.
What is the problem
Regrads Ann

...
But I do see thumbnails of JPEGs there...
You get no error messages(s) at all?
Check your server's error log too.
Go to 'admin/settings/image-toolkit'
Are you using the 'gd' toolkit?
Go to 'admin/logs/status/php'
Search for 'JPG Support'. is it enabled?
Open an issue in the Image module's issue queue. (It's not the 'Image Gallery' module itself which handles the images; it's the 'Image' module.) I've found a report about JPEG there, but the user got error messages, which isn't the case with you.
The Error
The log i get when i put up a jpg file is
Unable to create scaled Thumbnail image
Unable to create scaled Thumbnail image
Your Image has been created.
q's thumbnail derivative image was missing. The derivatives will be rebuilt to regenerate it.
The derivative images for q have been regenerated.
Ann
Same error
I get the same error mesages.
Everything works. The thumbnails are created and the galery behaves like it should. Only those error messages bother and i have no idea why they appear, since stuff is obviously working.
# DSC00712's thumbnail derivative image was missing. The derivatives will be rebuilt to regenerate it.# DSC00712's preview derivative image was missing. The derivatives will be rebuilt to regenerate it.
# The derivative images for DSC00712 have been regenerated.
Same error with 6.2
Is there a solution for this? I see these error messages too despite that fact that things appear to be working correctly.
I am working with Drupal 6.2 and the Image module (version 6.x-1.0-alpha2).
Posted in the wrong forum. Sorry.
I just realized this is a 5.x forum. My apologies for posting 6.x issues here!
For what it is worth, in 6.x it appears that these errors were caused by the web browsers' local cache.
Maybe it's the same with 5.x?