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.

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!


simple and lightweight. with this you have the absolute control over what was successfully send. besides that you can also send a manual email from the dashboard. nice


Perfect companion for wp mail smtp or wpo365


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

LogStore vs Mail logging – WP Mail Catcher