Plugin yìí kò tíì ṣe àyẹ̀wò pẹ̀lú àwọn ìtújáde mẹ́ta pàtàkì tó kẹ́yìn ti WordPress. Ó lè jẹ́ pé a kò tọ́jú tàbí ṣe àtìlẹ́yìn fún un mọ́, ó sì lè ní àwọn ọ̀ràn ìbámu nígbà tí a bá lò ó pẹ̀lú àwọn ẹ̀yà WordPress tuntun.

Image Processing Queue

Àpèjúwe

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.

Ìgbéwọlẹ̀

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

Àwọn àgbéyẹ̀wò

Èbìbí 4, 2020
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.
Ọwẹ́wẹ̀ 29, 2017
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 ) );
Èbìbí 1, 2017
Real intresting approach and something that should be considered for WP Core – especially the Batch Processing Stuff isn#t only useful for images …
Ka gbogbo àwọn àgbéyẹ̀wò 9

Àwọn Olùkópa & Olùgbéejáde

“Image Processing Queue” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

A ti túmọ̀ “Image Processing Queue” sí àwọn èdè agbègbè 2. Ọpẹ́lọpẹ́ fún àwọn atúmọ̀ èdè fún àwọn ìkópa wọn.

Túmọ̀ “Image Processing Queue” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

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