23355 Posts in 17838 Topics by 2862 members
|Go to End|
7 February 2014 at 10:27pm
Don't use FlushGeneratedImageTask. It will "Remove all cached/generated images created as the result of an image manipulation" and "Actually clear out all the images".
All resized images inside HTMLEditors will be lost, because the path to the resized image is hardcoded in the image tag.
- You have "assets/Uploads/_resampled/ResizedImage200268-02.jpg" somewhere
- FlushGeneratedImageTask will remove all cached images
- "assets/Uploads/_resampled/ResizedImage200268-02.jpg" doesnt exists anymore
- edit "assets/Uploads/_resampled/ResizedImage200268-02.jpg" to "assets/Uploads/02.jpg" and save the DataObject
- a new "assets/Uploads/_resampled/ResizedImage200268-02.jpg" will be generated.
19 February 2014 at 8:36am Last edited: 19 February 2014 8:44am
Hmmm, that's a bit of an oversight....
Okay, how about this slight change of tack. When I was calling "FlushGeneratedImagesTask", I was only concerned with flushing the resampled folder of a specific directory within "assets/".
Is there a way to flush all generated images within a certain folder only?
19 February 2014 at 9:52pm
Sure. Write your own FlushGeneratedImagesTask?
Anyhow, cached images will be deleted if its original image get deleted. So there is really no good reason to use this task other than to have a clean state for development purposes.
|Go to Top|