Delicious Brains

Brad Touesnard

Image Processing Queue is an alternative to on-the-fly (OTF) image processing (e.g. <a href="https://github.com/syamilmj/Aqua-Resizer" rel="nofollow ugc">Aqua Resizer</a>) 
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 <a href="https://github.com/A5hleyRich/wp-queue" rel="nofollow ugc">WP Queue</a>.
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 <code>srcset</code> and delete them from the 
filesystem when the image is deleted from the Media Library.

Image Processing Queue

It works!

tbh, it took me a few minutes to fully understand how this library would benefit my workflow and my clients - but once I started to grasp the changes in development and how I wouldn't be running Regenerate Thumbnails every time I needed a new image size, it clicked!

I think with some more detailed documentation and usage examples this could be a near perfect solution to the image size problem in many themes and plugins.



This could be a game changer!

Real intresting approach and something that should be considered for WP Core - especially the Batch Processing Stuff isn#t only useful for images ...

Great Idea!

Andy Fragen

Ari Stathopoulos

Colin Stewart

Paul Biron

This is a feature plugin is for testing Rollback Auto-Update, aka Rollback part 3. This feature only protects plugins during the auto-update process.
As part of the normal Rollback process, the currently installed version of the plugin is moved to <code>wp-content/upgrade-temp-backup/plugins</code>. An active plugin is checked to ensure it doesn’t cause a PHP fatal error when visiting the site. An inactive plugin is not checked because it cannot cause your site to white screen.
Rollback parts 1 was merged into WordPress 6.2 as the <code>move_dir()</code>. Rollback part 2 was merged into WordPress 6.3 and protects the manual update process of plugins and themes.
<ul>
<li><a href="https://core.trac.wordpress.org/changeset/53578" rel="nofollow ugc">r53578</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55204" rel="nofollow ugc">r55204</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55219" rel="nofollow ugc">r55219</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55220" rel="nofollow ugc">r55220</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55223" rel="nofollow ugc">r55223</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55720" rel="nofollow ugc">r55720</a></li>
</ul>
<h3>Testing</h3>
<ul>
<li>Requires WordPress 6.3</li>
<li>This only works on auto-updates.</li>
<li>Run the following commands from the terminal. You might need to run the command several times to get it started: 
wp cron event run wp_version_check</li>
<li>When updating a plugin, you should be able to see the old plugin in the <code>wp-content/upgrade-temp-backup/plugins/PLUGINNAME</code> folder. The same should apply for themes. Since updates sometimes run fast and we may miss the folder creation during testing, you can simulate an update failure to demonstrate.</li>
<li>When a plugin auto-update fails, the previous version should be restored. To test that, change the version of a plugin to a previous number, run the update, and on fail the previous version (the one where you changed the version number) should still be installed on the site. To simulate an update failure and confirm this works, use the built-in Simulate failure link. Just activate/deactivate from the <code>plugins.php</code> page action link. This link will only be present if the plugin has an update pending.</li>
</ul>
<h3>Reporting</h3>
Please submit <a href="https://github.com/afragen/rollback-update-failure/issues" rel="nofollow ugc">issues</a> and <a href="https://github.com/afragen/rollback-update-failure/pulls" rel="nofollow ugc">PRs</a> to GitHub.
Logo from a meme generator. <a href="http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.html" rel="nofollow ugc">Original artwork</a> by Allie Brosh.

Rollback Auto Update

A feature plugin now only for testing Rollback Auto Update, aka Rollback part 3. Manual Rollback of update failures has been committed in WordPress 6.

Image Processing Queue vs Rollback Auto Update