Scott Cariss

<p>Automatic upgrades on live sites are, we think most people would agree, a Bad Idea. You can’t test them before they go live; they’ll play havoc with your version control system, if you’re using one; and if they fail or screw up, your live site is broken. Bad. Idea.</p>
<p>Enter Staunch. Staunch makes you stick to best practice for upgrades, by preventing even admins and superadmins from running WordPress’s automatic upgrade processes on your live site.</p>
<p>When you want to upgrade WordPress, you can do so on a local or development install of your site; after you’ve tested it and made sure everything’s okay, you can then deploy the site as you usually would — through version control, FTP, or something else.</p>


Staunch

A WordPress plugin to prevent automatic updates on your live sites.

Sed Lex

<p>Every thing you need to efficiently develop a fresh plugin.</p>
<p>The different features is:</p>
<ul>
<li>Creation tool for creating a new fresh plugin without difficulties, </li>
<li>SVN client for uploading your plugin into WordPress repository, </li>
<li>An interface to push plugins and data from your dev site to your production site (and vice versa). </li>
<li>Show all messages/errors/warning/notices raised by your plugins in the admin panel. </li>
<li>Automatic import of sent translations. </li>
</ul>
<p>This plugin is under GPL licence.</p>
<h4>Multisite – WordPress MU</h4>
<h4>Localization</h4>
<ul>
<li>English (United States), default language</li>
<li>French (France) translation provided by SedLex</li>
</ul>
<h4>Features of the framework</h4>
<p>This plugin uses the SL framework. This framework eases the creation of new plugins by providing tools and frames (see dev-toolbox plugin for more info).</p>
<p>You may easily translate the text of the plugin and submit it to the developer, send a feedback, or choose the location of the plugin in the admin panel.</p>
<p>Have fun !</p>


Dev Toolbox

Every thing you need to efficiently develop a fresh plugin.

Staunch vs Dev Toolbox