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.

flashpixx

<p>The plugin creates zip download links within articles and pages of a subversion or git repository. On each call the subversion revision number / git tag, link text, css name and download<br />
name can be set, so that each link points to different repositority parts.</p>
<h4>Features</h4>
<ul>
<li>remote access to Git or Subversion repository</li>
<li>local caching for the repository data</li>
<li>automatic update to the head revision</li>
<li>extension access only need on access</li>
<li>free configuration of tags, branches, trunk and revision / commit access</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WordPress 3.2 or newer</li>
<li>PHP 5.3.0 or newer </li>
<li><a href="http://de3.php.net/manual/en/book.zip.php" rel="nofollow ugc">PHP Zip extension</a></li>
</ul>
<p>for SVN access<br />
* <a href="http://de3.php.net/manual/en/book.svn.php" rel="nofollow ugc">PHP SVN extension</a></p>
<p>for Git access<br />
* Git client<br />
* PHP must execute shell commands (no safe mode)</p>
<h3>Shortcode</h3>
<p>Shotcut for SVN access</p>
<pre>[svnzip url="url-to-your-svn"]</pre>
<p>The SVN tag uses three optional flags (the default values are set within the plugin settings):</p>
<ul>
<li>“trunkdir” the name of the trunk directory</li>
<li>“branchdir” the name of the branch directory</li>
<li>“tagdir” the name of the tag directory</li>
</ul>
<p>Shotcut for Git access</p>
<pre>[gitzip url="url-to-your-svn"]</pre>
<p>Parameters for both commands are (all parameters are optional):</p>
<ul>
<li>“version” defines a special revision (SVN) / commit (Git), which is used. If the parameter is not set, the latest revision (head) is used</li>
<li>“downloadtext” filename for the downloaded file (if not is set, the linktext is used)</li>
<li>“linktext” text of the link (default is set within the plugin settings)</li>
<li>“cssclass” sets the CSS class of the link (default is set within the plugin settings)</li>
<li>“type” enum value trunk | branch | tag for setting the repository part (default is trunk, for Git trunk is also used and it is applied to the master)</li>
<li>“name” the value for tag- or branchname (on trunk it is ignored / empty)</li>
</ul>


Repository Zip

With this plugin a zip download link of a subversion or git repository can be created within blog articles and pages

Staunch vs Repository Zip