WordPress.org

Felix Arntz

Andrew Ozz

<p>Lazy Loading Feature Plugin is an official plugin maintained by the WordPress team. It is intended for testing of automatically adding the <code>loading</code> HTML attribute to images and other elements that support it.</p>
<p>More information about the <code>loading</code> attribute:<br />
Description: <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-loading" rel="nofollow ugc">https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-loading</a>.<br />
HTML Specification: <a href="https://html.spec.whatwg.org/multipage/embedded-content.html#attr-img-loading" rel="nofollow ugc">https://html.spec.whatwg.org/multipage/embedded-content.html#attr-img-loading</a>.</p>
<p>Currently the <code>loading</code> attribute is supported in the following browsers: <a href="https://caniuse.com/#feat=loading-lazy-attr" rel="nofollow ugc">https://caniuse.com/#feat=loading-lazy-attr</a>.</p>
<p>To test, install and enable the plugin. It will automatically add <code>loading="lazy"</code> attributes to all images in all new and existing posts, pages, and text widgets on the front-end.</p>
<p>Then use one of the browsers that support it (Chrome, Opera, Firefox, Edge, Android, etc.) and visit the site. Best would be to test over a slower connection, with a phone, etc. and test web pages that have a lot of images, like gallery posts.</p>
<h4>Things to look for</h4>
<ul>
<li>Obvious bugs, for example images are missing.</li>
<li>Try to scroll down as soon as the page loads. All images should be at their places, and the page shouldn’t “jump” when images are loaded.</li>
</ul>
<h4>Note to developers</h4>
<p>This plugin is intended for testing. If the tests are successful, this functionality will be added to WordPress, but the exact code may change, perhaps significantly.</p>
<p>When testing, please also test the filters added by this plugin, and provide feedback at <a href="https://github.com/WordPress/wp-lazy-loading" rel="nofollow ugc">https://github.com/WordPress/wp-lazy-loading</a> or at <a href="https://core.trac.wordpress.org/ticket/44427" rel="nofollow ugc">https://core.trac.wordpress.org/ticket/44427</a>.</p>


Lazy Loading Feature Plugin

WordPress feature plugin for testing and experimenting with automatically adding the "loading" HTML attribute. Not for production use.

Andy Fragen

Ari Stathopoulos

Colin Stewart

Paul Biron

<p>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.</p>
<p>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.</p>
<p>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.</p>
<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 <strong>only</strong> 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:<br />
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 <strong>Simulate failure</strong> 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>
<p>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.</p>
<p>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.</p>


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.

Lazy Loading Feature Plugin vs Rollback Auto Update