This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Image Processing Queue

ཞིབ་བརྗོད།

Image Processing Queue is an alternative to on-the-fly (OTF) image processing (e.g. Aqua Resizer)
for WordPress themes.

Like OTF image processing, it allows theme developers to define image sizes for specific theme
contexts rather than defining a size for all uploaded images. This greatly reduces the number of
resized images and hence reduces disk space usage and the wait time when uploading an image.

Image Processing Queue differs from OTF image processing in how it behaves when an image doesn’t
exist yet. OTF generates the image right away and the end-user has to wait for the image to be
generated. With Image Processing Queue there’s no waiting. It immediately returns an image that
already exists (that is the closest fit to the image size requested) and adds the image size to
a queue. Image sizes are quietly generated in the background using WP Queue.

Image Processing Queue also accommodates responsive themes much better than OTF. It allows theme
developers to define a list of image sizes that will work best for their theme’s responsive
breakpoints. Images generated by Image Processing Queue are added to the post meta so that WordPress
core’s responsive functions will automatically add them to the srcset and delete them from the
filesystem when the image is deleted from the Media Library.

སྒྲིག་འཇུག

To install as a plugin search for “Image Processing Queue” in your WordPress dashboard and install it from there.

གདེང་འཇོག

2020 ལོའི་ཟླ 5 ཚེས 4 ཉིན།
It’s crazy this exact functionality is not in core! These days many themes and custom built sites/themes have 10 to 15, or often many more crop sizes, especially if you are trying to support responsive images properly. But usually you only need 3 or 4 crop sizes for any given images. The functionality of this plugin would solve that, but it should be WP core to save everyone wasted storage space and to ensure future compatibility. To me it makes no sense for a cropped copy of the image to be created when that image is never loaded — ever.
2017 ལོའི་ཟླ 10 ཚེས 11 ཉིན།
Have been using this now for a couple of months and it’s improved my workflow significantly!
2017 ལོའི་ཟླ 9 ཚེས 29 ཉིན།
I have been using aquaResize for a long time, this is a game changer. If you want only the url of the resized image use echo ipq_get_theme_image_url( $id_here, array( 600, 400, false ) );
2017 ལོའི་ཟླ 5 ཚེས 1 ཉིན།
Real intresting approach and something that should be considered for WP Core – especially the Batch Processing Stuff isn#t only useful for images …
གདེང་འཇོག 9 ཡོངས་སུ་ཀློག

བྱས་རྗེས་འཇོག་མཁན། & གསར་འབྱེད་པ།

“Image Processing Queue” is open source software. The following people have contributed to this plugin.

བྱས་རྗེས་འཇོག་མཁན།

“Image Processing Queue” has been translated into 2 locales. Thank you to the translators for their contributions.

ཁྱེད་ཀྱི་སྐད་ཡིག་ནང་ལ་ “Image Processing Queue” ཡིག་སྒྱུར་བྱོས།

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

དག་བཅོས་ཉིན་ཐོ།

1.1.1

  • Bug fix: PHP Fatal error: Class ‘Image_Processing_Queue\Exception’ not found.

1.1.0

  • Improvement: Added ipq_job_attempts and ipq_cron_interval filters.

1.0.0

  • New: Uses WP Queue internally to process image jobs.
  • Bug fix: Multiple jobs for the same attachment created.

0.2

  • New: ipq_get_theme_image_url function added for returning a single image URL

0.1

  • First release