Jason Cosper

<p>PLU Redux displays the “Last Updated” date and “Tested up to” version for all of your installed plugins. If a plugin hasn’t been updated in over two years – or hasn’t been tested with a recent WordPress version – you’ll get a warning emoji next to the relevant field.</p>
<p>Version 3.0 adds full support for plugins managed by <a href="https://git-updater.com/" rel="nofollow ugc">Git Updater</a>. GitHub, GitLab, Bitbucket, Gitea, and Gist are all supported.</p>
<h3>Usage</h3>
<p>Once activated, head over to your Plugins screen. You’ll see “Last Updated” and “Tested up to” info in the metadata row for each plugin. Warning emojis appear when a plugin hasn’t been updated in over two years or its “Tested up to” version is significantly behind your current WordPress version.</p>
<p>For the Site Health checks, navigate to Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Site Health in your WordPress dashboard.</p>
<h3>Git Updater Support</h3>
<p>PLU Redux automatically detects plugins using <a href="https://git-updater.com/" rel="nofollow ugc">Git Updater</a> headers and queries the appropriate hosting API for last updated info.</p>
<p>Supported platforms:</p>
<ul>
<li>GitHub (<code>GitHub Plugin URI</code>) – checks releases first, falls back to last commit</li>
<li>GitLab (<code>GitLab Plugin URI</code>) – uses <code>last_activity_at</code></li>
<li>Bitbucket (<code>Bitbucket Plugin URI</code>) – uses <code>updated_on</code></li>
<li>Gitea (<code>Gitea Plugin URI</code>) – self-hosted; requires a full URL in the header</li>
<li>Gist (<code>Gist Plugin URI</code>) – uses gist <code>updated_at</code></li>
</ul>
<p>PLU Redux also respects the <code>Primary Branch</code> header. When there’s no release, it falls back to the last commit on the specified branch.</p>
<p>Note: “Tested up to” is only available for WordPress.org plugins. Git-hosted plugins will only show “Last updated.”</p>
<h3>Site Health Check</h3>
<p>PLU Redux adds two checks to Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Site Health:</p>
<ul>
<li><strong>Outdated plugins</strong> – Lists any plugins not updated in 2+ years (critical status).</li>
<li><strong>Untested plugins</strong> – Lists plugins not tested with a recent WordPress version (recommended status).</li>
</ul>
<h3>WP-CLI Command</h3>
<p>PLU Redux includes a WP-CLI command: <code>wp plu list</code></p>
<p>This outputs a table of your installed plugins with their last updated dates and tested versions. Plugins needing attention are flagged with an arrow (<code><-</code>). A <code>-</code> in the “Tested Up To” column means the plugin isn’t in the WordPress.org directory.</p>


PLU Redux

Displays the "Last Updated" date and "Tested up to" version for your plugins. Supports WordPress.org and Git Updater plugins.

Marius L. J.

<p>Troubleshooting Mode was initially a feature introduced via the Health Check plugin, and is now available as a standalone plugin.</p>
<p>The most common, and reliable, means of troubleshooting a website using WordPress, is by first disabling all plugins, and using one of the default themes that come with the software.<br />
The best way to do this, is by the use of a staging website, but not all website hosting providers have this feature, or it may not be part of the plan you are currently on.</p>
<p>Troubleshooting Mode will do its best to allow a site maintainer to disable plugins, and switch themes, without affecting regular visitors to your website.</p>


Troubleshooting

Provides a Troubleshooting Mode to help with support and debugging.

PLU Redux vs Troubleshooting