flashpixx

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 
name can be set, so that each link points to different repositority parts.
<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>
for SVN access 
* <a href="http://de3.php.net/manual/en/book.svn.php" rel="nofollow ugc">PHP SVN extension</a>
for Git access 
* Git client 
* PHP must execute shell commands (no safe mode)
<h3>Shortcode</h3>
Shotcut for SVN access
<pre>[svnzip url="url-to-your-svn"]</pre>
The SVN tag uses three optional flags (the default values are set within the plugin settings):
<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>
Shotcut for Git access
<pre>[gitzip url="url-to-your-svn"]</pre>
Parameters for both commands are (all parameters are optional):
<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

kdiweb

Posts can be grouped in many ways in WordPress but there is no direct version control system. This plugin offers a lightweight solution if you want version control for a group of posts.
To make this work you define a keyword for each version control group you want to create. Then use that keyword as a prefix in the post name of each post in that group. The plugin will sort out the latest post automatically and label the rest as outdated.
It also let’s you have a URL that will always point to the latest post of that version control group. That way you can give out the URL to others and be sure that your visitors will always be viewing the most recent post.
This plugin will automatically:
<ul>
<li>Define if a post is part of a version control group. </li>
<li>Search and locate the latest post by publish date.</li>
<li>Label the older posts of the group as outdated.</li>
</ul>
This is especially practical for bloggers that often revisit older subjects and have to do the linking with the updated posts manually. Or if you are like me and publish material that has versioning applied to it (ex. software) through a blogging platform.
<h3>Usage</h3>
First thing you should do is visit the plugin’s options page (“Settings” -> “Post Version Control”).
There you will find two fields:
<ol>
<li>
The keyword list field, where you enter all the keywords you want to track seperated from each other by a comma and a space “, “. Each of them defines a different version control group.
</li>
<li>
The path for the latest posts URL. By default the path is “/current”. So if we have a keyword named “ajax” the URL: http://www.myblogaddress.com/current/ajax will point to the latest post of the “ajax” group.
</li>
</ol>
To link a post to a version control group of posts all you need to do is enter the keyword of that group as a prefix to the post_name of that post. So in the group “ajax” mentioned earlier all posts in that group should start with the “ajax-” prefix. An example list of that group of posts might be:
<ol>
<li>ajax-first-post</li>
<li>ajax-updated-version</li>
<li>ajax-latest-news</li>
</ol>
..and so on.
The plugin will automatically look through your posts of the same group and label the older ones by inserting an <!– outdated –> tag. This is replaced by the content of “outdated.html” in runtime. This is an example of how you can style your outdated tag. Just insert it along with your other styles:
<style>
p.outdated{ 
 border: dashed 1px #f00; 
 background: #eee; 
 color: #f00; 
 text-align: center; 
}
p.outdated a { 
 color: #f00; 
}
</style>
Uninstalling should be pretty easy too. The only left overs are the <!– outdated: … –> comments in the old posts content which of course are ignored when viewing the webpage. If you don’t mind that you don’t have to do anything else apart from de-activating the plugin through your WordPress administration.
<h3>License</h3>
This work is released under the terms of the GNU General Public License: 
http://www.gnu.org/licenses/gpl-2.0.txt

Post Version Control

Automatic version control for posts with the same prefix in the post_name

Repository Zip vs Post Version Control