Hi all,
I have a problem with updating my imagecache files. Some cached images are unable to remove or update. Deleting images in the files/ folder works fine, but the cached images of that file are not deleted as well. I can understand that this is how it goes, and that the cached images are suppost to be overwritten next time. But if i upload a new image with the same name, the old cached images will not be replaced by caches of the newly uploaded images.
I also cannot change the write permissions with Filezilla. My maps and files are all in xxx modus. I guess that's because apache is the 'owner'?
Using a hard refresh or running cron does not help, but flushing the caches manually per type in the imageCache menu does. But i can't expect future users to flush it manually through an admin page.
I am thinking that i can use another token to make every uploaded image unique. Now i use the following for naming my images:
[title].[filefield-extension-original]
I'll try to make it more unique by adding date or something. I guess the problem still remains that old cached images will not be removed and just build up onto the server forever...
I'll try adding the file-ID:
[title]-[field_image_cache-filefield-fid].[filefield-extension-original]
I hope someone can help me out. This issue is driving me crazy.
Cheers,
Danny
Comments
Comment #1
danny_joris commentedits what i expected: it works, but the old files just stack up. I guess its a fine temporary sollution...
Comment #2
bsenftner commentedI am experiencing this same issue - deleted nodes from custom (module implemented) Content Types are leaving their imagecache versions in the imagecache directories.
However, this is majorly important for me, because the WebApp that is this project has high turnover for node creation, use, and deletion. The WebApp is used by image analysis labs, and the researchers (end users) create lots of data and delete it routinely. The imagecache directories grow 20-60 MB each day, and I'm periodically flushing all of them via the admin interface, but that process is not practical. And I only have one lab using it at this point - the final user pool will be hundreds of different labs using it.
Looking at the imagecache.module file, I noticed a routine called imagcache_file_delete()... would this be the correct routine to call to delete an image's imagecache versions when it's owning node is deleted?
Comment #3
fizk commentedPlease reopen if this is still an issue with ImageCache 6.x-2.0-rc1.