Needs work
Project:
Image
Version:
6.x-1.x-dev
Component:
image.module
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Sep 2007 at 21:44 UTC
Updated:
22 Jan 2013 at 16:41 UTC
This patch for HEAD moves the image size settings into a table and puts the updated timestamp on each size so that when a size changes only that type of derivative image is rebuilt.
| Comment | File | Size | Author |
|---|---|---|---|
| image_sizing.patch | 13.07 KB | drewish |
Comments
Comment #1
Shai commentedOn this page: http://drupal.org/node/3256/release "head" is showing up as "Sept. 7". But I assume some cron job needs to run that hasn't yet. I'm hoping that I'll be able to test this on Sunday or Monday. Thanks for the work.
Shai
Comment #2
drewish commentedactually this isn't ready.
Comment #3
drewish commentedmarked #244315: Any Time You Change The Derivative Image Sizes, All Nodes Get That Derivative Rebuilt All At Once as a duplciate
Comment #4
Leeteq commentedAlso see http://drupal.org/node/257168
"Prevent unnecesary rebuilding of derivative images"
Comment #5
ice5nake commentedWith convert being a resource intensive program I'd say this should be given a higher priority. Not to mention this is crashing my server at the moment.
I have 8 different sizes running on my site and whenever I change one of these settings slightly the server is crashing. I have a dedicated VM with 2GB of Ram reserved and 2ghz reserved.
Comment #6
jcamfield commentedBump for this or the broader #244315 ; things that would make my server less angry at me:
- batch rebuilding by cron, so that the site doesn't churn through every image
- enable deleting a derivative set without triggering a rebuild
- Make sure you only rebuild derivatives that have changed
- Rebuild at next view of the image
- integrate with imagecache's management a bit more?
Comment #7
ice5nake commentedDespite what I imagine is a huge number of installations it seems like this module has been abandoned.
See: http://drupal.org/node/257168#comment-4772192
I'd say there needs to be a warning on the home page of this project saying that it doesn't scale well and that it is no longer being supported.