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 8 of 10)
Jan 10, 2008 12:58 am
The log is now shown according to whatever time offset your blog is configured for.
Jan 9, 2008 4:51 am
John - looks like time for changes when looking at the audit trail are taken from server time. At least it doesn't heed my wordpress settings. I've seen that with another plugin I'm using (cforms), developer found that the time was pulled from database settings. This something easy to change? So AuditTrail picks update time from blog settings?
Dec 31, 2007 12:22 am
Hi Manne, no changes are needed to plugin.php (doing so will prevent any localisation!). Have you modified wp-config.php to your locale?
Dec 22, 2007 5:08 pm
Hi, I'm trying to localize AT and have made a sv_SE.mo file that I've put in /locale. I've also changed $locale to sv_SE in plugin.php. What else do I have to do to make the translation kick in?
Nov 26, 2007 10:44 pm
I've released a new version with a few updates and hopefully an end to the favicon.ico issue
Nov 26, 2007 3:35 am
JP, I should reword that section, but what it means is that data will be lost if you are upgrading from a pre 1.0 version. After that your data is retained.
Nov 18, 2007 4:05 pm
Great work!
I have the same problem describing in posts #28 and #56. I don't know if .htaccess really cause that problem (not tested), nethertheless I have to use that file. Its content is
I've took a look at my database and the entry of the field operation is template_redirect.
Ok, nice information, but what can I do to avoid logging of favicon.ico?
THX again for your plugin
Nov 14, 2007 2:56 pm
John, the page says: NOTE: If you are upgrading from a previous 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)
...so it should be ok to upgrade, contrary to the page's statement?
Nov 13, 2007 3:50 pm
Great plugin. I am however only able to view the first page of the audit. Any other pages gives a "Cannot load audit-trail.php." error message even when I use the Next link or click on the page # under Manage>Audit Trail. Does anyone know why this is the case?
Nov 12, 2007 6:57 pm
Updates should occur without data loss
Leave a comment