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.

Pär Thernström

Bring more loggers to <a href="https://simple-history.com" rel="nofollow ugc">WordPress user history plugin Simple History</a>. 
That are useful for developers during development of a site or to maintain a live site.
<h3>Important</h3>
Please note that this plugin is no longer actively maintained and only receives security fixes.
<h3>Modern and up to date alternatives</h3>
For an up to date alternative please see the <a href="https://simple-history.com/add-ons/debug-and-monitor/" rel="nofollow ugc">Debug & Monitor add-on</a> which logs WP REST API requests, sent emails, HTTP API requests, and WP cron jobs.
<h3>Get more features with Simple History Premium</h3>
Need advanced WordPress audit logging capabilities? Simple History Premium extends your site monitoring with powerful features:
Enhanced WordPress Activity Logging:
<ul>
<li>Advanced Analytics Dashboard – Comprehensive stats and visual activity tracking</li>
<li>Custom Event Logging – Add manual entries and notifications to your audit trail</li>
<li>Stealth Mode – Control user access with granular permissions</li>
<li>Flexible Log Retention – Configure automatic cleanup or keep logs indefinitely</li>
<li>Data Export Tools – Export logs in CSV/JSON format for analysis</li>
<li>Security Features – IP anonymization and login attempt location tracking</li>
</ul>
<a href="https://simple-history.com/premium/" rel="nofollow ugc">» Get Simple History Premium</a>
<h3>Included loggers and plugins</h3>
Post to Slack
All your events is posted to a <a href="https://slack.com/" rel="nofollow ugc">Slack</a> channel of your choice, using an <a href="https://api.slack.com/incoming-webhooks" rel="nofollow ugc">incoming webhook</a>. Yes, with this plugin enabled 
there is no need what so ever to ever leave Slack to see what’s happening on your site or the site of your 
clients or… well, on any site where you have Simple Histor and this plugin enabled.
WP_Mail-logger
See all mails sent with wp_mail(), no matter what the recipient address is. 
changelog
404 logger
View page visits that load the 404 template.
JavaScript error logger
See what JavaScript errors users that visit your site is getting.
SystemLog logger
Log all messages from Simple History to the syslog on the server. With this logger enabled there is no need to use the beautiful GUI of Simple History ;).
HTTP API logger
Log all usage of HTTP calls from functions like wp_remote_post() and wp_remote_get().
You can the URL requested, the arguments posted and the full returned result, including server headers.
The time for the request to complete is also logged. Great for debugging!

Developer Loggers for Simple History

Useful loggers for SimpleHistory for developers during development of a site or to maintain a live site.

Observer vs Developer Loggers for Simple History