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 4 of 10)
Jun 15, 2007 4:50 pm
Strange...
one thing still doesn't seem to be right though, the page views that are now monitored are diplayed as "/?p=40" instead of "Title for post nr 40". Page edits are showed with the right title
Jun 14, 2007 8:38 pm
The file should be created by WordPress itself, and the file you posted above shouldn't cause a problem. I'm actually surprised that your site is still working afterwards!
Jun 13, 2007 1:59 am
your were right John, I deleted the htaccess-file and now Audit Trail works as aspected! I wonder what plugin created the file in the first place..
Jun 13, 2007 1:53 am
ok, I guess that has to be it... this is my .htaccess :
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
Jun 11, 2007 2:11 am
Manne, I'm at a loss. Something on your site is causing all requests to be routed through WP, resulting in Audit Trail to pick them up and also being a performance slowdown (hits to static files, like images and CSS, should not touch WP). Maybe it has something to do with your .htaccess file?
Jun 4, 2007 7:58 pm
Jake, Audit Trail requires WP 2.1 or higher
Jun 4, 2007 12:43 pm
I keep getting the following error when I activate the plugin:
Fatal error: Call to undefined function: wp_enqueue_script() in /home/grapethi/public_html/wp-content/plugins/audittrail/audit-trail.php on line 50
May 23, 2007 11:07 am
Hello John
No it's not just xinha, also pictures, javascript files etc used by the theme and by plugins are being logged, for example:
/wp-content/themes/gluedideas_subtle/styles/default/headers/header_menu.jpg
/wp-content/themes/gluedideas_subtle/favicon.ico
/wp-content/plugins/attachment_list/attachment.css
/wp-content/themes/gluedideas_subtle2/assets/js/form_comments.js
All these came from one single post view.
May 23, 2007 10:57 am
Ouch... I am working elsewhere!
I test wordpress using easyphp... I am not a real wordpress user (yet?).
May 22, 2007 9:02 pm
Hi Pret,
The search does work, it just doesn't search user names! Doing so isn't going to be a small change so I'll put that and your suggestion for filters onto the list for the next version.
Leave a comment