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.

webaware

Log emails to the WordPress database for later analysis. Access is restricted to administrators, and emails with WordPress passwords are obfuscated for security / privacy. Useful for diagnosing lost email problems.
Use this plugin with <a href="https://shop.webaware.com.au/downloads/disable-emails/" rel="nofollow ugc">Disable Emails</a> to divert all WordPress emails into logs, especially handy for developers.
Logs are automatically purged after a defined period, set through a settings page in the WordPress admin. Setting the period to 0 prevents logs from being purged. Uninstalling the plugin purges all logs.
<h3>Translations</h3>
Many thanks to the generous efforts of our translators:
<ul>
<li>Czech (cs-CZ) — <a href="http://www.klusik.cz/" rel="nofollow ugc">Rudolf Klusal</a></li>
<li>English (en_CA) — <a href="https://translate.wordpress.org/locale/en-ca/default/wp-plugins/log-emails" rel="nofollow ugc">the English (Canadian) translation team</a></li>
<li>English (en_GB) — <a href="https://translate.wordpress.org/locale/en-gb/default/wp-plugins/log-emails" rel="nofollow ugc">the English (British) translation team</a></li>
<li>French (fr-FR) — <a href="http://www.eticweb.ca/" rel="nofollow ugc">Hugo Catellier</a></li>
<li>Korean (ko_KR) — <a href="https://translate.wordpress.org/locale/ko/default/wp-plugins/log-emails" rel="nofollow ugc">the Korean translation team</a></li>
</ul>
If you’d like to help out by translating this plugin, please <a href="https://translate.wordpress.org/projects/wp-plugins/log-emails" rel="nofollow ugc">sign up for an account and dig in</a>.

Log Emails

Thanks for a plguin, it was thoroughly coded and seems have all that I need.

Simple and useful plugin

Seriously, this plugin is so freakin' helpful. I work on a lot of sites that I have set up on my local development machine and don't have outgoing email set up on purpose. Only rarely do I need access to test those emails. But when I need it, it's typically urgent. This plugin has completely saved the day multiple times over the past month.

Thank you so much for the great work!

Only sad I didn't find this plugin sooner!

I've checked it's functionality and with first sight, it didn't contained vulnerable parts. Thank you.

compact and free from vulnerabilities

Log emails to the database, to enable email problem analysis

Custom Logging Service vs Log Emails