Dawi

This plugin disables the WordPress update notifications, as well as update notifications of different plugins. It is ideal to deliver a complete WordPress and not bother the user with alerts. Silence!
<h4>Please note!</h4>
It’s very important that you keep your WordPress plugins up to date. If you don’t, your blog or website could be susceptible to security vulnerabilities or performance issues. If you use this plugin, you must make sure you keep yourself up to date with new releases of your active plugins and update them as new versions are released.

Silence!

Disables the plugin update checking and notification system.

Steve Taylor

This plugin has arisen from the requirements of a client who manage many of their WordPress sites via Git repositories on Beanstalk. Core WP files are not in the repo, to keep its size down, but plugins and themes are. WP upgrades are of course tested on local development and remote staging servers before being run on the production server. But since plugins and themes are in the repo, ideally they should be upgraded locally for testing, then pushed to Beanstalk. Beanstalk in turn deploys the changes to the staging server, and then the production server.
To help maintain this workflow, this plugin tests if the environment is local or not (checking for <code>WP_LOCAL_DEV</code> or searching for “localhost” in <code>$_SERVER['HTTP_HOST']</code>). If the environment isn’t local, plugin and theme installation, editing and upgrades are disabled.
The following constants can be defined in <code>wp-config.php</code> to override the defaults:
<ul>
<li><code>SLT_CLC_LOCAL_STRING</code> – The string to search for in <code>$_SERVER['HTTP_HOST']</code> that will indicate a local development environment. Default: <code>"localhost"</code></li>
<li><code>SLT_CLC_DISABLE_REMOTE_CORE_UPGRADES</code> – Default: <code>false</code></li>
<li><code>SLT_CLC_DISABLE_REMOTE_PLUGIN_THEME_UPGRADES</code> – This will also disable editing plugin and theme files via the admin interface. Default: <code>true</code></li>
<li><code>SLT_CLC_OUTPUT_NOTICES</code> – Whether to output explanatory notices on the upgrades, themes, and plugins admin pages. Default: <code>true</code></li>
<li><code>SLT_CLC_CORE_NOTICE</code> – Default: <code>"Core upgrades are currently disabled on this server by the Control Live Changes plugin."</code></li>
<li><code>SLT_CLC_PLUGIN_THEME_NOTICE</code> – Default: <code>"Plugin and theme upgrades are currently disabled on this server by the Control Live Changes plugin."</code></li>
</ul>
An alternative to the <code>SLT_CLC_LOCAL_STRING</code> check for a local environment is the <code>WP_LOCAL_DEV</code> constant. This is used by Mark Jaquith in his technique for defining local database connection details in a separate file (http://markjaquith.wordpress.com/2011/06/24/wordpress-local-dev-tips/). If <code>WP_LOCAL_DEV</code> is set to true, the <code>SLT_CLC_LOCAL_STRING</code> check is made irrelevant.
Development code hosted at <a href="https://github.com/gyrus/Control-Live-Changes" rel="nofollow ugc">GitHub</a>.

Control Live Changes

Prevents certain upgrade and installation actions on non-local environments.

Silence! vs Control Live Changes