Posted by galed on July 2, 2009 at 4:52am
Jump to:
| Project: | ImageCache |
| Version: | 6.x-2.0-beta9 |
| Component: | imagecache_image module |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
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
#1
I also have the same problem. Is there no solution for this? or is it a bug?
#2
I haven't been able to figure it out in the time between now and when I first posted this
#3
So i have this problem to. Pls someone to write how to create preset images from already uploadet pics
#4
Similar problem here... I checked the files directory permissions and they are owned by apache...
Subscribing...
#5
I'm using the 5.x-2.4 version but am also having the same issues
#6
did you set the permissions?
#7
Did i set the permissions on what? The images? the file folder?
#8
did you try flushing the preset cache?
#9
I'm having the same behaviour. I have tried to flush the preset but it doesn't help.
#10
Same issue, and not finding the reason...
#11
+1!
#12
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.
#13
+1 same issue
#14
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
#15
+1
#16
+1
#17
subscribing
#18
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.
#19
+1
#20
+1
#21
subscribing
#22
+1
#23
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.
#24
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
#25
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)