Darren Jacoby

<p>Easily configure the WordPress admin interface and application state using a single config file.</p>
<ul>
<li>Simplify the WordPress admin interface.</li>
<li>Place WordPress application state in a config file.</li>
</ul>
<p><a href="https://github.com/darrenjacoby/intervention" rel="nofollow ugc">Intervention on GitHub</a></p>


Intervention

Vishal Paswan

<p>Version Locker lets you lock specific plugins and themes to their current version. Once locked, they won’t update automatically or manually until you unlock them.</p>
<p>Useful for keeping your site stable when you have customized plugins, client sites, or production environments where you need control over when things update.</p>
<h3>What It Does</h3>
<ul>
<li>Lock individual plugins to prevent updates</li>
<li>Lock individual themes to prevent updates</li>
<li>Block all plugin updates at once (global killswitch)</li>
<li>Block all theme updates at once (global killswitch)</li>
<li>Block WordPress core updates (global killswitch)</li>
<li>Quick toggle locks on/off without page reload</li>
<li>Bulk lock or unlock multiple items</li>
<li>Email alerts when locked items try to update</li>
<li>Search and filter your plugins and themes</li>
<li>Activity log showing who locked what and when</li>
<li>Works on Multisite (each site has its own locks)</li>
</ul>
<h3>How It Works</h3>
<p>The plugin uses WordPress filters to hide update notifications and block update attempts. It doesn’t modify any plugin or theme files.</p>
<h3>Credits</h3>
<p>Thanks to <a href="https://profiles.wordpress.org/nemai/" rel="nofollow ugc">Nemai Naskar</a> for testing and feedback on 1.2.2.</p>


Version Locker

Lock plugin and theme updates to prevent accidental or automatic updates. Simple, secure update control for WordPress.

Intervention vs Version Locker