Konstantin Obenland

Erick Hitter

Brandon Kraft

Adam Silverstein

Pascal Birchler

Ipstenu (Mika Epstein)

Michael Arestad

Mark Uraine

Johan Falk

Shiny Updates is a WordPress Core Feature Plugin.
It replaces The Bleak Screen of Sadness™ (example) with a simpler and more straight forward experience when installing, updating, and deleting plugins and themes. 
Progress updates for these actions don’t add a benefit, they are disruptive and confusing. Shiny Updates deals with these details behind the scenes, leaving users with clear actions and results.
Development for this plugin takes place at GitHub. 
To report bugs or feature requests, please use <a href="https://github.com/obenland/shiny-updates/issues" rel="nofollow ugc">Github issues</a>.
<h3>Testing</h3>
We need help testing the user flows! Please <a href="https://wordpress.org/plugins/shiny-updates/" rel="ugc">install the Shiny Updates plugin</a>, run the tests below, and share your feedback in the <a href="https://wordpress.slack.com/archives/feature-shinyupdates" rel="nofollow ugc">#feature-shinyupdates</a> channel in Slack or <a href="https://github.com/obenland/shiny-updates/issues" rel="nofollow ugc">create an issue on GitHub</a>.
Update core
<ol>
<li>If you have any themes or plugins that need updating, update them. If you don’t have any that need updating, you can edit the them and change the version number to something older. Once saved, they will show as needing an update.</li>
<li>Update one specific item, a theme or a plugin.</li>
<li>Try updating all items in the table.</li>
<li>Share your feedback. Or if you found a bug, <a href="https://github.com/obenland/shiny-updates/issues" rel="nofollow ugc">create an issue on GitHub</a>.</li>
</ol>
Questions
<ol>
<li>What were the noticeable differences in the new install/update/activate/delete process compared to the old one without Shiny Updates?</li>
<li>How did installing and activating a plugin or theme go? Was it difficult or easy? Was it faster or slower than expected?</li>
<li>Do you have any further comments or suggestions?</li>
</ol>

Shiny Updates

Why isnt this in core, who wants to see the ugly installation screen ? the only thing i would be worried about and hopefully is considered if there is a problem with installation does it give a valuable error ? other than that we must get rid of the ugly install screen's



Needs to be in core

A smoother experience for managing plugins and themes.

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.

Shiny Updates vs Rollback Auto Update