Resizing more the 250 at a time

You can go into imsanity/ajax.php and around like 76 it looks like this:

if ($count >= 250) break;

You can increase that number 250 to whatever you like. But, at a certain point you may get server timeouts or your browser may get a little cranky. The bulk resize are processed 1 at a time so even if it hangs in the middle you can always start from whatever point it left off so there’s no harm in experimenting with a large number there.

Hi Wockawocka,
I’m working on a site that has around that many posts with images as well. When I go to search for images to bulk resize, I get the twirlly thing while it’s working/searching and it’s taking forever. Is that what happened to you as well?

Jason, I guess what I’m asking is… Does Imsanity find the first 250 images and then stop searching or does it need to work its way through the entire database before it returns the 250 images?

Thanks!

Since WordPress stores the image metadata as JSON inside one single mysql column – unfortunately but there really isn’t any way to query by size efficiently.

Imsanity will do the first “page” of 250 images and then stop. Then if you run it again it will try to locate then next “page” of 250 and so on. So eventually you would resize your entire library. But – if your library had thousands of images then my guess is the bulk resize will be fast for page 1, a little slower for page 2, and so on because it has to read all of the previous images. I’m guessing that after a couple of thousand it may get slow.

It’s not great, but due to the way WordPress stores the image size data I’m not sure there’s a more efficient way to query it.

here’s a jquery blam for ya.

setInterval(function(){ if (jQuery('div:contains("RESIZE COMPLETE")').size() < 1) return; imsanity_load_images('imsanity_image_list'); setTimeout(imsanity_resize_images, 10 * 1000); }, 5 * 1000);

gang bang all your images in batches of 250. just paste that in the Chrome console.