ccprog

This plugin is derived from the no longer supported 
<a href="https://wordpress.org/plugins/wordpress-logging-service" rel="ugc">WordPress Logging Service</a>. 
Despite that it is not compatiple with it, and there is no upgrade path from one 
to the other.
<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>
Check to test if the plugin is active:
<pre><code>CLGS = true
</code></pre>
Defined severity levels:
<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>
returns <code>true</code> if <code>$category</code> is registered.
<pre><code>clgs_register ( $category, $description )
</code></pre>
registers <code>$category</code> as a log category. <code>$description</code> will be shown in the 
management page. 
It is good practice to use unique categories for each plugin that publishes 
log messages.
<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 
 wp_kses_data)</li>
</ul>
returns <code>false</code> if the category is already registered or it is too long.
<pre><code>clgs_clear ( $category )
</code></pre>
deletes all log entries of <code>$category</code>.
<ul>
<li><code>string $description</code> existing category</li>
</ul>
returns number of deleted entries or <code>false</code> if action failed.
<pre><code>clgs_unregister( $category );
</code></pre>
deletes all log entries and then removes <code>$category</code>.
<ul>
<li><code>string $description</code> existing category</li>
</ul>
returns <code>false</code> if false if action failed.
<pre><code>clgs_log( $category, $text, $severity = null, $user = null, $blog_id = null, $date = null );
</code></pre>
writes a new log entry in the specified category
<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 
by <code>wp_kses_data</code>)</li>
<li><code>int $severity</code> one of defined severity levels (see above); if missing defaults to 
 CLGS_NOCATEGORY</li>
<li><code>int | string | WP_User $user</code> user id, slug or WP user object are aceptable; if missing 
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>; 
if missing defaults to current time</li>
</ul>
returns <code>false</code> if entering the log failed.

Custom Logging Service

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

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.

Custom Logging Service vs Developer Loggers for Simple History