Scott Cariss

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.
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.
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.

Staunch

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

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

Staunch vs Post Version Control