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.

JWardee

<p>Logging your mail will stop you from ever losing your emails again! This fast, lightweight plugin (under 140kb in size!) is also useful for debugging or backing up your messages.</p>
<p>Just install and activate then all of your contact form emails will be logged and saved to your DB with no additional configuration required.</p>
<p>View and manage all your form submissions through the default WordPress interface. An email failed to send? With a single click you can resend the backed up email.</p>
<p>Send emails out directly from the WordPress interface. Also includes support for attachments.</p>
<p>Immediately find out if your contact form submission was successfully sent.</p>
<h3>Features</h3>
<ul>
<li>Zero setup required – just install and away you go</li>
<li>Minimalistic – no overbloated features you never use weighing your site down – under 140kb in size!</li>
<li>Bulk export emails to CSV for easy inclusion into Excel or any other program</li>
<li>Compose new emails with the WordPress controls you’re already familiar with</li>
<li>Resend your emails in bulk</li>
<li>Debugging – see exactly which file and code line was responsible for sending the email, along with any errors encountered</li>
<li>Manage what user permissions can see the logs</li>
<li>Routinely have your logs cleared out at a specified time – or keep them forever</li>
<li>Need to be notified when there’s a problem sending your mail? We’ve got hooks that allow you to do just that</li>
<li>Completely free</li>
</ul>
<h3>Hooks and actions</h3>
<ul>
<li><code>wp_mail_catcher_mail_success</code> is triggered when a message is sent and logged successfully. It has a single argument that is an array containing the log
<ul>
<li><code>id</code> related to the id in the <code>mail_catcher_logs</code> MySQL table</li>
<li><code>time</code> relative, readable time to when the log was saved</li>
<li><code>email_to</code> the email address(es) that the message was sent to</li>
<li><code>subject</code> the subject line of the message</li>
<li><code>message</code> the contents of the message</li>
<li><code>status</code> an integer depicting if the message was sent successfully or not (1 = sent successfully. 0 = sending failed)</li>
<li><code>error</code> the error that occurred – if any</li>
<li><code>backtrace_segment</code> a json_encoded object that shows which file and line the mail was initially triggered from</li>
<li><code>attachments</code> a list of any attachments that were sent along with the email</li>
<li><code>additional_headers</code> a list of any headers that were sent</li>
<li><code>attachment_file_paths</code> a list of the location of any attachments that were sent</li>
<li><code>timestamp</code> a unix timestamp of when the email was sent</li>
<li><code>is_html</code> a boolean, that will be true if the message is a html email and false if not</li>
<li><code>email_from</code> the from value of the email</li>
</ul>
</li>
<li><code>wp_mail_catcher_mail_failed</code> is triggered when a message failed to send and logged successfully. It has a single argument that is an array containing the log (same as the arguments for <code>wp_mail_catcher_mail_success</code>)</li>
<li><code>wp_mail_catcher_deletion_intervals</code> is a filter that should return an array where each key is an amount of time in seconds, and the value is the label. Used to determine when a message has expired and should be deleted</li>
<li><code>wp_mail_catcher_before_success_log_save</code> is a filter that is called just before a successful log is saved. It has a single argument that is the transformed log that will be saved – use this to alter the log before it’s saved. Returning <code>false</code> will stop the log from being saved. Also note that this is fired even when an email has errored, because all logs are initially saved as “successful” before being possibly updated with an error (if applicable). This is because of the way the <code>wp_mail</code> and <code>wp_mail_failed</code> are implemented in WordPress.
<ul>
<li><code>time</code> a unix timestamp of when the email was sent</li>
<li><code>email_to</code> the email address(es) that the message was sent to</li>
<li><code>subject</code> the subject line of the message</li>
<li><code>message</code> the contents of the message</li>
<li><code>backtrace_segment</code> an array that shows which file and line the mail was initially triggered from</li>
</ul>
</li>
<li><code>wp_mail_catcher_before_error_log_save</code>
<ul>
<li><code>time</code> a unix timestamp of when the email was sent</li>
<li><code>email_to</code> the email address(es) that the message was sent to</li>
<li><code>subject</code> the subject line of the message</li>
<li><code>message</code> the contents of the message</li>
<li><code>backtrace_segment</code> an array that shows which file and line the mail was initially triggered from</li>
<li><code>error</code> the error that occurred</li>
</ul>
</li>
</ul>


Mail logging – WP Mail Catcher


Works great. It needs a some adjustments though on mobile screens.


Works Great


Really well done thank you!Very useful debug function with the code that sent the email!


Keeps track of all emails sent


Works perfectly as expected, every single time, for years and years!


The Best!

just perfect!


This is a great extension, and does everything that you need of an email logging extension. 



Very useful for debugging purposes!


Easy to use, with no bloat.


tested it for a few weeks and it's very fine, lite and fast.



only one small proposal: option to redirect an email - some users input their email wrong and admins can see this and redirect to the correct email address (ex. @yhoo.com instead of yahoo.com)


perfect for mail logging and preview

Stop from ever losing your emails again! This fast, lightweight plugin (under 140kb in size!) is also useful for debugging or backing up your messages

Custom Logging Service vs Mail logging – WP Mail Catcher