Manually regenerating derivatives?

I was also wondering something simillar.. if it's possible to stop them from automatically regenerating each time something is changed with the image crop and size settings..? Or atleast, to hide the message which shows up on everyone's profile page which says which images had been regenerated.

you can easily recreate your derivatives all at once:
- admin -> content management -> content - > Show only items where: type: image -> Update options: rebuild image thumbnails.

It helps if you 1) set your lists to something insane like 200 or so nodes, and 2) start from the last page of images. You're done when you start to hit images marked "new".

Now the opposite (sort of.) Is there anyway to hide that message that shows all the regenerated images that appears on any page with image nodes?

Sorry, unfortunately this request is way too specific. Feel free to re-open this issue if you want to supply a patch.

When I do this

- admin -> content management -> content - > Show only items where: type: image -> Update options: rebuild image thumbnails.

with all of the image nodes selected, the derivatives do not get built and I get "Page Not Found" error.

If I do it with a single image node it works fine in rebuilding the images. But as I start to do more than 1 at time, around 3 or 4 I start to get errors that not all of the derivatives are being created.

I really need to find a way for my client to upload their images in bulk, and get the derivatives made since doing it on demand causes too many other problems.

I'm using the Imagemagick Tool Kit, as the GD bombs with memory problems. PHP Memory Limit is set to 90M (the limit by the host).

I'm sure this failure is also a memory problem, so I think need to find or make a script that will give the client a link to run this function sequentially on each image.

Any help you can give me will be greatly appreciated!
Thanks in advance!
Steve

How does the site react to looking at galleries, one by one by one by one by one? That'll regenerate derivatives, too, if the thumbnails (and/or other derivatives) have been deleted off the hard drive (or server) first.

Thanks for your reply, Hetta.

I find that if there are more than 1 image that needs derivatives created I will often get a message that a few of the derivatives were not created. If there is a very large number to create, I have also found that it appears to work with a few error messages, but none those derivatives are not indeed saved in the files/images directory.

Because of the jQuery scripts I'm using on this site to replace images in certain instances, I really need to have the derivatives created first, not on the fly.

Ideally, I would like to have the derivatives created immediately after import so that the client (and their employees) doesn't have to remember to do any extra steps.

I'm reviewing the modules code now to see how I might call for the derivatives to be created after importing without causing the other memory problems I have read about in other posts when trying to do this.

I'm also trying to do more controlled testing to see when and where it actually fails.

Thanks for you help,
Steve

Sorry, unfortunately this request is way too specific. Feel free to re-open this issue if you want to supply a patch.

I was able to effect a cron-triggered regeneration of image derivatives in D7 as follows:

1. Create a view with a page display which displays all desired image derivatives as fields in a list of nodes. I.e. so that loading this view's URL in a browser triggers image derivative generation. You don't have to use a pager; we'll be making wget wait a delay before each request.

2. For sake of simplicity, disable all blocks for this view's URL. I.e. try to only have the view display the image derivatives and as few links as possible.

3. Launch wget in a cron job on some period, e.g. every 2hrs, like so:

5 */2 * * * wget -P /tmp/wget-drupal -nH -w 5 -m -r -q -I sites/default/files/styles http://mysite.com/view-url > /dev/null 2>&1

The important bits are the "-w 5", the "-P /tmp/wget-drupal", and the "-I sites/default/files/styles" options. The first tells wget to wait 5sec before each request, i.e. so that it's not trying to download all image derivatives one immediately after another. The 2nd tells wget to store the files it downloads locally, so it can maintain a local cache to compare against. The 3rd option tells wget only to download image derivative files.

You would need to alter this wget command to match your setup.