Download Now

We are happy to announce Vigilance 1.2 has been released! This is the most stable Vigilance release to date. A few bugs have been squashed and some new features added:

• Cleaned up the alternating comment coloring
• Search term was not included in the title of the search results page
• Added trackbacks/pingbacks functionality and separated them from the comments
• Fixed too many tags breaking the layout issue
• Fixed the custom code feature so that it actually works

Hope everyone enjoys the release and be sure to report any bugs in the comments.

Download Now
In the rush to push out a fix for the comments issue we missed a formatting error in the functions.php file. This is causes a Warning: Cannot modify header information - headers already sent by error when you try to login to your WordPress admin panel. Please immediately update to 1.16 to fix this issue. 1.15 will no longer be available for download.

Download Now

Unfortunately, a bug has been discovered in version 1.14 that causes the following error in all versions prior to 2.7 (which is currently in beta):
Fatal error: Call to undefined function: post_password_required()

This 1.15 release fixes that bug. We encourage everyone that upgraded to 1.14 to now upgrade to 1.15. We apologize for any inconvenience this may have caused.

Download Now

We pushed out Vigilance 1.14 today in anticipation of the upcoming WordPress 2.7 release. Vigilance 1.14 is ready for 2.7 and we are already running the latest beta version here! One of the most exciting new features of 2.7 is comment threading. We are excited to announce Vigilance now has built in support for comment threading. We encourage you to take a look at all of the new features that will be included in WordPress 2.7.

Note: Older versions of Vigilance will work with 2.7, but will not have the comment threading feature. As always we recommend upgrading to the latest version.

Download Now

Features and fixes in version 1.13:

• Fixed bugs relating to link color switching in the theme options menu
• Added an option to disable image hovers in the theme options menu
• Properly cleared entry div to fix floated blockquotes and other floated elements
• Added automatic author comment highlighting

We pushed out a quick release with two small updates, nothing major. Look for Vigilance 1.2 to drop over the coming weeks. It will have some nice new features including the option to change the width of the theme from within the Theme Options panel.

Version 1.11 of Vigilance was released today:

• New alert box for the home page that can be toggled on and off through the theme options panel
• Added a permalink to comments and cleaned up the comments template
• Switched the date location on single posts
• Fixed date spacing on post titles
• Removed favicon from the default theme files to prevent upgrade overwriting

A quick tutorial on using WordPress “Child Themes” to upgrade Vigilance while maintaining your custom CSS, adding custom functions, and eventually adding custom templates (WordPress 2.7) adding custom templates.

Read more

We just pushed out Vigilance 1.1 which contains a few new features and some bug fixes. We highly recommend upgrading to this release:

• Added background color and link color to the Theme Options Menu for super easy color customization. The background.css file has now been deprecated.
• The theme is now fully compatible with the subscribe to comments plugin and now contains a link to the comment RSS feed.
• Added “Edit” links to posts and pages for easy editing when you are logged in with proper privileges.
• Added proper paragraph spacing for comments
• Added a “Your comment is awaiting moderation” message when the feature is enabled.
• Fixed recent comments widget display bug.
• Fixed category widget when post count was enabled.

Vigilance 1.01 was released today! Head on over to the download page to grab it. Some minor bugs were squashed:

• Comments textarea width was too wide.
• Admin email address in comments.php was set to an incorrect email address.
• Search results styling was causing the date to display incorrectly.

Sometime in the next few weeks we will have a more substantial release with some exciting new features. You can always check out new features and development activity by browsing through the latest commits. Download and run these nightly builds by visiting the repository.