Andy Whalen

<p>Creates a log file for network/multisite super admin actions.</p>
<p>The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:</p>
<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>
<p>The following actions are logged for ANY user:</p>
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
<p>Some actions that change data will show what the value was before and after.</p>
<p>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”:</p>
<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>
<p>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.</p>
<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.

Kunal

<p><strong>Custom 404 Pro</strong> replaces WordPress’s default 404 behaviour with a proper redirect. Instead of leaving visitors on a dead-end error page, you can send them to any page on your site or an external URL — with the HTTP status code of your choice.</p>
<h4>Redirect Modes</h4>
<ul>
<li><strong>WordPress Page</strong> — pick any published page from a dropdown; the plugin redirects to it automatically.</li>
<li><strong>Custom URL</strong> — enter any absolute URL to redirect 404s off-site or to a specific path.</li>
<li><strong>HTTP Status Code</strong> — choose 301, 302, 307, or 308 to match your SEO or caching requirements.</li>
</ul>
<h4>404 Logging</h4>
<p>When logging is enabled, the plugin records every 404 hit to a database table so you can see exactly what is broken:</p>
<ul>
<li>Request path</li>
<li>Visitor IP address (can be disabled for privacy/GDPR compliance)</li>
<li>Referrer URL</li>
<li>User agent</li>
<li>Timestamp</li>
</ul>
<p>Logs are searchable and can be deleted individually, in bulk, or all at once. They can also be exported as a CSV file. A configurable retention policy lets you automatically cap the table by row count, by age, or both — with a daily background cleanup and an on-demand Prune Now button.</p>
<h4>Email Notifications</h4>
<p>Optionally receive an admin email each time a 404 is logged. Designed for low-traffic monitoring — if you expect high 404 volume, keep this off to avoid inbox flooding.</p>
<h4>Multisite Support</h4>
<p>Works correctly on WordPress Multisite installations — activation creates the logs table for each site in the network.</p>
<h4>Multilingual Support</h4>
<p>Compatible with <strong>Polylang</strong> and <strong>WPML</strong>. The redirect page is resolved to the correct language variant for the current visitor automatically.</p>


Custom 404 Pro

Take control of every 404 on your site — redirect visitors to a custom page or URL, log what broke, and get notified when it matters.

Observer vs Custom 404 Pro