I had uploaded a whole bunch of images with a few presets. I have since added a new preset. The new preset works for images uploaded after I created it, but not for images uploaded before.

I've cleared the cache, no luck. What's happening here and how do i fix it?

Comments

philly1’s picture

philly1 CreditAttribution: philly1 commented

I also have the same problem. Is there no solution for this? or is it a bug?

galed’s picture

galed CreditAttribution: galed commented

I haven't been able to figure it out in the time between now and when I first posted this

irgnet’s picture

irgnet CreditAttribution: irgnet commented

So i have this problem to. Pls someone to write how to create preset images from already uploadet pics

ferrangil’s picture

ferrangil CreditAttribution: ferrangil commented

Similar problem here... I checked the files directory permissions and they are owned by apache...
Subscribing...

glarsch’s picture

glarsch CreditAttribution: glarsch commented

I'm using the 5.x-2.4 version but am also having the same issues

robino’s picture

robino CreditAttribution: robino commented

did you set the permissions?

galed’s picture

galed CreditAttribution: galed commented

Did i set the permissions on what? The images? the file folder?

drewish’s picture

drewish CreditAttribution: drewish commented
Status: Active » Postponed (maintainer needs more info)

did you try flushing the preset cache?

wpanssi’s picture

wpanssi CreditAttribution: wpanssi commented

I'm having the same behaviour. I have tried to flush the preset but it doesn't help.

casafont’s picture

casafont CreditAttribution: casafont commented

Same issue, and not finding the reason...

Rosamunda’s picture

Rosamunda CreditAttribution: Rosamunda commented

+1!

picardo’s picture

picardo CreditAttribution: picardo commented

Same issue. As a bit of context, I have a custom file path configuration on my content field where I see this issue. So instead of saving the files in sites\default\files\ it saves them sites\default\files\[site-name]\portfolio\[content-type]. Might be irrelevant, but I don't know what could be significant to fix this issue.

FreeFox’s picture

FreeFox CreditAttribution: FreeFox commented

+1 same issue

eff_shaped’s picture

eff_shaped CreditAttribution: eff_shaped commented

me too.

tried all that flushing (what does flushing a preset do anyway?)

and uploading another version of the image doesn't add the preset into the image browser for node that pre-exists the new preset

wuihung’s picture

wuihung CreditAttribution: wuihung commented

+1

wuihung’s picture

wuihung CreditAttribution: wuihung commented

+1

modctek’s picture

modctek CreditAttribution: modctek commented

subscribing

wrd’s picture

wrd CreditAttribution: wrd commented

I'm having the same problem. My older presets are all working correctly, and the new preset tests out fine (the sample image is displayed at the correct size, and the resized image appears in the preset directory), but attempts to load existing images using the new path just result in a 404 and no new image is created in the preset directory.

jemond’s picture

jemond CreditAttribution: jemond commented

+1

stuchl4n3k’s picture

stuchl4n3k CreditAttribution: stuchl4n3k commented
Component: Miscellaneous » imagecache_image module
Category: support » bug
Priority: Normal » Major

+1

Poieo’s picture

Poieo CreditAttribution: Poieo commented

subscribing

frognation’s picture

frognation CreditAttribution: frognation commented

+1

unc0nnected’s picture

unc0nnected CreditAttribution: unc0nnected commented
Priority: Major » Critical
Status: Postponed (maintainer needs more info) » Active

i just decided to change the default display size for images on my CMS by created a new preset editing views and then I flushed the previous one to clean up all the old images and now you're telling me I'm completely stuck with an imageless site because no one ever conceived of the day when this would happen? Is there any way at all to fix this? reinstall imagecache because it sounds like I'm going to have to dump it all together now.

unc0nnected’s picture

unc0nnected CreditAttribution: unc0nnected commented
Priority: Critical » Major

http://drupal.org/project/imagecache_batch

Check out the following module.. I've set it up and am running cron for the first time now and it's going nuts re-creating all of my images that were lost. Thank god for this module, can't believe this was overlooked in such a critical module like imagecache

sandrewj’s picture

sandrewj CreditAttribution: sandrewj commented
Status: Active » Postponed (maintainer needs more info)

If the imagecache_batch module is solving this problem it seems that imagecache IS able to generate images according to a new preset.

For those still having this problem, can you check several things:
1. drupal permissions for "view

" 2. filesystem permissions for the folder 3. The drupal error log for any error messages from imagecache You can also try loading a single image from a new preset over the course of ten minutes and see how long/if it ever is generated. If the image doesn't show up, what response do you get (404,403,500, file not found, forbidden, internal server error)
fizk’s picture

fizk CreditAttribution: fizk commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Please reopen if this is still an issue with ImageCache 6.x-2.0-rc1.

sumoanand’s picture

sumoanand CreditAttribution: sumoanand commented
Version: 6.x-2.0-beta9 » 6.x-2.0-rc1
Status: Closed (fixed) » Active

I am still getting this issue. It is working for old presets. But for new, neither preset folder nor images getting created.