wyrfel

<p>LogStore can be used to log (important) data from within your plugin.<br />
It provides a simple interface to log entries and a friendly administration interface for viewing and managing the log entries.</p>
<p>While LogStore can be used to log debug output or system events, it’s main intention is to log more extensive data, such as:</p>
<ul>
<li>system emails sent your users</li>
<li>data received from remote API calls</li>
</ul>
<h3>Usage</h3>
<p>To use LogStore in your plugin, add the following line to your plugin’s ‘plugins_loaded’ callback function:</p>
<pre><code>if (class_exists('LogStore')) $this->log = new LogStore('slug', __('Title'));
</code></pre>
<ul>
<li>The ‘slug’ should be a unique identifier for your logger.</li>
<li>The ‘Title’ will be the title used in menu entries, options and page titles.</li>
</ul>
<p>Once that’s done you can then start logging your data from anywhere within your plugin by using the following:</p>
<pre><code>if (!empty($this->log)) $this->log->log(__('My log message'), $my_log_data, 'status', 'tag');
</code></pre>
<ul>
<li>‘My log message.’ is any arbitrary message to describe your log entry.</li>
<li>$my_log_data is the extended data you want to log. This can be either an array or string.</li>
<li>‘status’ is one of ‘none’, ‘ok’, ‘warn’, ‘critical’ or ‘fatal’.</li>
<li>‘tag’ can be any kind of singular tag to  further classification to your log entries.add</li>
</ul>
<p>If you use LogStore in your plugin, you should check for it’s presence in</p>
<ul>
<li>your ‘plugins_loaded’ callback</li>
<li>your plugin activation callback</li>
</ul>
<p>You should either make LogStore use optional or notify the user that they need to install LogStore for your plugin to work properly.</p>
<h3>Plugin Hooks</h3>
<p>In the following hooks, <code>*myname*</code> stands for the name with which you instanciated the LogStore class.</p>
<h4>Action Hooks</h4>
<ul>
<li><code>logstore_init-*myname*</code> – runs during the execution of WP’s <code>init</code> action hook, passes a single boolean parameter indicating if logging is active or inactive for this logger</li>
</ul>
<h4>Filter Hooks</h4>
<ul>
<li><code>logstore_new_entry-*myname*</code> – runs during the creation of a new entry, passes a single array containing all values for that entry (‘time’, ‘message’, ‘data’, ‘status’ and ‘tag’)</li>
<li><code>logstore_entry-*myname*</code> – runs before displaying an entry on screen, passes a single array containting all values for the entry (‘time’, ‘message’, ‘data’, ‘status’ and ‘tag’)</li>
<li><code>logstore_format_entry_data-*myname*</code> – runs before displaying the formatted data on screen, passes the formatted data as string</li>
</ul>
<h3>Further Notes</h3>
<p>Please note that the ‘bulk actions’ in the log viewer are currently not<br />
working.</p>


LogStore

LogStore is a 'meta' plugin that allows other plugins to log data easily.

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.

LogStore vs Custom 404 Pro