Audit Trail Plugin
Audit Trail is a plugin to keep track of what is going on inside your blog. It does this by recording certain actions (such as who logged in and when) and storing this information in the form of a log. Not only that but it records the full contents of posts (and pages) and allows you to restore a post to a previous version at any time.
To summarize:
- Log of user actions inside your blog - useful for finding out who did what in a multi-user system
- Post/page revisions and restorations - every change to a post or page is recorded and can be instantly restored to a previous version
- Differences are shown graphically
- Extensible, allowing other plugins the ability to add and display items in the Audit Trail
- Ability to track registered user page visits
- Fully localized
Version History
- 1.0.10 - Only include prototype on AT pages
- 1.0.9 - WP 2.5 compatability
- 1.0.8 - Show log items according to blog timezone offset
- 1.0.7 - Fix favicon.ico logs, ignore certain users, track failed login attempts
- 1.0.6 - Fix warning, allow searching by username
Installation
The plugin is simple to install:
- Download audit-trail.zip
- Unzip
- Upload
audit-traildirectory to your/wp-content/pluginsdirectory - Go to the plugin management page and enable the plugin
You can find full details of installing a plugin on the plugin installation page.
NOTE: If you are upgrading from a pre 1.0 version please de-activate and then re-activate the plugin. This will upgrade your database tables (unfortunately any existing Audit Trail data will be lost).
Usage
Once the plugin is installed then your actions are already being recorded. You can view the Audit Trail log from the Manage/Audit Trail page.
Note that some entries in the log can be clicked and will expand to show more details.
Post & Page history
The Audit Trail plugin records the entire post everytime it is changed. This can then be used to provide a version history along with the capability of restoring a post to a previous version through this interface which appears on appropriate posts:
Usage is simple. Select the version you wish to view, click the 'view' button and examine the contents of the post. From here you choose to restore this version, delete it, or close the contents.
Restoring a post to a previous version will be recorded in the Audit Trail logs just like any other change. If you decide you don't like the restored version you can always restore back to another version.
NOTE: Installing the Audit Trail plugin in a blog with existing posts will mean that you have no revision history until a post has been changed at least twice (there is no log before the plugin, and there is little point allowing a restoration to the same version as is currently live)
Options
From the options page you can configure exactly what actions are audited. Any plugins that support Audit Trail will also display themself here.
Permissions
Users with the 'edit_plugins' or 'audit_trail' capability can view and administer the Audit Trail plugin. The 'audit_trail' capability can be added with the Role Manager plugin.
Support
Please direct all support questions to the Audit Trail support forum. Any support questions left on this page may not be answered.
Bugs & New Features
A full list of all bugs can be found in the Audit Trail issue tracker.
A full list of all requested features can be found in the Audit Trail feature tracker.
Comments (page 6 of 10)
Oct 19, 2007 9:56 am
When I click on the "View" button to the right of the various version listings when editing a post, nothing happens.
Oct 15, 2007 7:45 am
It started working on its own! This looks great.
What was happening is:
If I do Manage --> Audit Trail, and click one of the "Save post" links, the area where the edit box would appear opens up, but then it is filled with my site's custom 500 server error message, including CSS, which screws up the style for the entire page I am viewing.
If I do Manage --> Posts, and click the "View" button for a revision, it shows the 500 error where it would have shown the diff between revisions.
Oct 15, 2007 3:48 am
Designer, favicon.ico shouldn't appear in the logs. Only pages that are served through WordPress will appear in the log. If favicon.ico is appearing then it means it is being served by WordPress, which is not supposed to happen. A possible cause of this would be a .htaccess file - see comment 38.
Endolith, what part of the page?
Manne, times are recorded in the timezone of your server. Does that still make it 2 hours off?
Oct 14, 2007 1:35 pm
This looks like what I've been looking for, but when I try to view the difference between two revisions, part of the page I am looking at is replaced with my site's 500 server error message.
Oct 11, 2007 3:19 pm
I have "Registered user page visits" enabled on Audit trail, but I keep on getting flooded with "View Page - /favicon.ico" views. This is in WordPress 2.3 install. Any way to exclude specific files or just /favicon.ico?
Sep 21, 2007 11:33 am
John: Great!
I just noticed that the date/time recorded by Audit Trail are two hours off, I guess it has to do with GMT since I'm at GMT+2. How could I fix it?
Aug 27, 2007 3:09 am
This is a wonderfull tool for our multi-user blog.
Thanks for sharing it.
I would be happy happy happy if Audit Trail also would
- log failed login attempts
- log password resets
- alert me by email or run a script when there are too many login failures or pwd resets
(I'm thinking of time limited dynamic IP blocking here...)
Aug 24, 2007 12:17 am
Manne, I'll put that on the list for the next version
Aug 23, 2007 10:42 pm
I figured out my problem. The ssl capability check that was recently added does not work in my environment. Apache was installed to be used with Plesk (server administration) only, which uses ssl. The blog is installed on the main web server which is using IIS (http only). In this scenerio, the .js was trying to load from the https site (which was wrong one). I commented out the check, which fixed the issue.
Aug 23, 2007 7:16 am
Would it be possible to include custom fields (metadata) in the version history?
Leave a comment