Infinite loop when filtering Media Library images by size in a modal (using wp_prepare_attachment_for_js)

[silb3r]

In an attempt to restrict a post's Featured Image dimensions to imagers wider than 100px I implement the following code in functions.php:

function restrict_media_library_by_width($response, $attachment, $meta) {
  if(isset($response['width']) && isset($response['height']) && $response['width'] > 100) {
    return $response;
  }
  return false;
}
add_filter('wp_prepare_attachment_for_js', 'restrict_media_library_by_width', 10, 3);

I then click "Set featured image" and the Media Library modal that appears only loads one empty thumbnail and my Network panel in Chrome Dev Tools reveals it makes continued, repeated, infinite AJAX requests.

The only viable alternative I've found was to run a separate query within ajax_query_attachments_args, which is needed because the _wp_attachment_metadata key contains serialized data and that leaves no way to compare dimensions within a meta_query.

Obviously running this additional query is inefficient and more resource intensive than it should be. More details here: ​http://wordpress.stackexchange.com/questions/180500/filter-media-library-items-by-size/.

[wonderboymusic]

This could use a deeper look

[fuhton]

array_filter removes any values that are false, but doesn't reset the array indexes and will eventually cause ajax response errors.

[adamsilverstein]

Thanks @fuhton for your patch! We certainly need more help with these JavaScript related tickets. This seems like a reasonable fix. Before your fix we were getting a malformed array in the callback, right?

I tested this fix, verified the issue is fixed. I've attached screencasts before and after your patch below.

ps. In the future, please generate your patch one level up, so its easier to apply (this is how we expect them).

Before:

After:

[adamsilverstein]

refresh patch from trunk

[fuhton]

@adamsilverstein Awesome! Looks like your patch is also including a change to twenty-eleven ( the code that was causing this issue )? Was that intentional?

[fuhton]

Refresh from trunk, but with only necessary changes

[adamsilverstein]

Replying to fuhton:

@adamsilverstein Awesome! Looks like your patch is also including a change to twenty-eleven ( the code that was causing this issue )? Was that intentional?

nope! whooops, thanks for catching that :) 31570.3.diff​ looks good.