ccprog

<p>This plugin is derived from the no longer supported<br />
<a href="https://wordpress.org/plugins/wordpress-logging-service" rel="ugc">WordPress Logging Service</a>.<br />
Despite that it is not compatiple with it, and there is no upgrade path from one<br />
to the other.</p>
<h4>Features</h4>
<ul>
<li>No log entries generated by the plugin itself, all come from external API calls</li>
<li>Organisation of log entries in freetext categories</li>
<li>Severity levels</li>
<li>Freetext log messages</li>
<li>Entries can be marked as seen and then filtered from being displayed again</li>
<li>Filtering by minimum severity level</li>
<li>Sort by date, category, user name, severity or blog name (in Multisite installations)</li>
<li>Access to the log page can be granted by user role</li>
</ul>
<h3>API</h3>
<h4>Constants</h4>
<p>Check to test if the plugin is active:</p>
<pre><code>CLGS = true
</code></pre>
<p>Defined severity levels:</p>
<pre><code>CLGS_NOSEVERITY = 0
CLGS_INFO = 1
CLGS_NOTICE = 2
CLGS_WARNING = 3
CLGS_ERROR = 4
CLGS_FATALERROR = 5
</code></pre>
<h4>Functions</h4>
<pre><code>clgs_is_registered ( $category )
</code></pre>
<ul>
<li><code>string $category</code></li>
</ul>
<p><em>returns</em> <code>true</code> if <code>$category</code> is registered.</p>
<pre><code>clgs_register ( $category, $description )
</code></pre>
<p>registers <code>$category</code> as a log category. <code>$description</code> will be shown in the<br />
management page.<br />
It is good practice to use unique categories for each plugin that publishes<br />
log messages.</p>
<ul>
<li><code>string $category</code> At most 190 (unicode) characters</li>
<li><code>string $description</code> can contain HTML same as comments (filtered by<br />
  wp_kses_data)</li>
</ul>
<p><em>returns</em> <code>false</code> if the category is already registered or it is too long.</p>
<pre><code>clgs_clear ( $category )
</code></pre>
<p>deletes all log entries of <code>$category</code>.</p>
<ul>
<li><code>string $description</code> existing category</li>
</ul>
<p><em>returns</em> number of deleted entries or <code>false</code> if action failed.</p>
<pre><code>clgs_unregister( $category );
</code></pre>
<p>deletes all log entries and then removes <code>$category</code>.</p>
<ul>
<li><code>string $description</code> existing category</li>
</ul>
<p><em>returns</em> <code>false</code> if false if action failed.</p>
<pre><code>clgs_log( $category, $text, $severity = null, $user = null, $blog_id = null, $date = null );
</code></pre>
<p>writes a new log entry in the specified category</p>
<ul>
<li><code>string $description</code> a registered category name</li>
<li><code>string $text</code> the logged message, can contain HTML same as comments (filtered<br />
by <code>wp_kses_data</code>)</li>
<li><code>int $severity</code> one of defined severity levels (see above); if missing defaults to<br />
  CLGS_NOCATEGORY</li>
<li><code>int | string | WP_User $user</code> user id, slug or WP user object are aceptable; if missing<br />
defaults to current user (or a placeholder if none is logged in)</li>
<li><code>int $blog_id</code> blog id; if missing defaults to current blog</li>
<li><code>int | double | string $date</code> a UNIX timestamp or a string recognized by <code>strtotime()</code>;<br />
if missing defaults to current time</li>
</ul>
<p><em>returns</em> <code>false</code> if entering the log failed.</p>


Custom Logging Service

Provides a simple API for storing miscellaneous log entries and displays them in a Dashboard subpage.

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.

Custom Logging Service vs Custom 404 Pro