Andy Whalen

Creates a log file for network/multisite super admin actions.
The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:
<ul>
<li>change network settings (update_site_option)</li>
<li>grant super admin privileges (granted_super_admin)</li>
<li>revoke super admin privileges (revoked_super_admin)</li>
<li>upgrade blog (wpmu_upgrade_site)</li>
<li>add blog (wpmu_new_blog)</li>
<li>set blog archived (archive_blog/unarchive_blog)</li>
<li>set blog deleted (make_delete_blog/make_undelete_blog)</li>
<li>set blog mature (mature_blog/unmature_blog)</li>
<li>set blog spam (make_spam_blog/make_ham_blog)</li>
<li>delete blog (delete_blog)</li>
<li>delete user (wpmu_delete_user)</li>
<li>delete user (deleted_user)</li>
<li>change other user’s settings (edit_user_profile_update) [NOTE: doesn’t show diff]</li>
<li>change blog setting (updated_option) [NOTE: may occasionally log annoyingly large diffs]</li>
</ul>
The following actions are logged for ANY user:
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
Some actions that change data will show what the value was before and after.
Below is an example of a log entry when the user ‘smith’ has changed the Network site name from “WP Local Network” to “WP Local Networks”:
<pre><code>[Tue, 03 Sep 2013 13:45:49 +0000] [smith:1] [update_site_option] [1] [site_name] [(WP Local Network)->(WP Local Networks)] [127.0.0.1] </code></pre>
Each line in the log file will roughly follow the below example. Individual actions may log slightly different information, but the DATETIME, USERNAME, USER_ID, ACTION, and IP_ADDRESS sections should always be populated.
<pre><code>[DATETIME] [USERNAME:USER_ID] [ACTION] [AFFECTED_OBJECT_ID] [DATA_TITLE_OR_KEY] [(VALUE_BEFORE)->(VALUE_AFTER)] [IP_ADDRESS] </code></pre>

Observer

Creates a log file for network/multisite super admin actions.

John Godley

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 summarise:
<ul>
<li>Log of user actions inside your blog – useful for finding out who did what in a multi-user system</li>
<li>Extensible, allowing other plugins the ability to add and display items in the Audit Trail</li>
<li>Ability to track registered user page visits</li>
<li>Fully localized</li>
</ul>
Audit Trail is available in:
<ul>
<li>English</li>
<li>Estonian by Lembit Kivisik</li>
<li>Belorussian by Marcis G</li>
<li>Simplified Chinese by maoanyuan</li>
<li>German by Andreas Beraz</li>
<li>Japanese by Chestnut</li>
<li>Romanian by Mikalay Lisica</li>
<li>Lithuanian by Nata Strazda</li>
</ul>
<h3>Documentation</h3>
Full documentation can be found on the <a href="http://urbangiraffe.com/plugins/audit-trail/" rel="nofollow ugc">Audit Trail Page</a> page.

Audit Trail

Notice: Trying to get property of non-object in /home/www/example.com/wp-content/plugins/audit-trail/models/auditor.php on line 337
Notice: Trying to get property of non-object in /home/www/example.com/wp-content/plugins/audit-trail/models/auditor.php on line 240
NUFF SAID!



Turn on DEBUG!!! ERRORS on TOOLS > AUDIT TRAIL admin page

Audit Trail is a plugin to keep track of what is going on inside your blog by monitoring administration functions.

Observer vs Audit Trail