WordPress plugin intelligence profile

Post Version Control

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

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 2.5
Current version1.0
WordPress coverageTested up to WordPress 2.5
Minimum stackWP 2.5 · PHP —
Directory statusactive
Last directory update29 May 200818y ago
Active installations10Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Post Version Control version 1.0 as active, updated 18y ago and tested up to WordPress 2.5.

Overview

About this plugin

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:

  • Define if a post is part of a version control group.
  • Search and locate the latest post by publish date.
  • Label the older posts of the group as outdated.

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.

Usage

First thing you should do is visit the plugin’s options page (“Settings” -> “Post Version Control”).

There you will find two fields:

-

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.

-

The path for the latest posts URL. By default the path is “/current”. com/current/ajax will point to the latest post of the “ajax” group.

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:

  • ajax-first-post
  • ajax-updated-version
  • ajax-latest-news

and so on.

– outdated –> tag. html” in runtime. This is an example of how you can style your outdated tag.

Just insert it along with your other styles:

<style>

outdated{

border: dashed 1px #f00;

background: #eee;

color: #f00;

text-align: center;

}

outdated a {

color: #f00;

}

</style>

Uninstalling should be pretty easy too. – 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.

License

This work is released under the terms of the GNU General Public License:

txt

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • version control
  • automatic
  • revision
  • subversion
  • svn
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 2.5

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 2.5.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to2.5
Minimum requirementsWordPress 2.5 · PHP not listed
Update activity29 May 200818y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.