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.

webaware

<p>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.</p>
<p>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.</p>
<p>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.</p>
<h3>Translations</h3>
<p>Many thanks to the generous efforts of our translators:</p>
<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>
<li>Russian (ru) — <a href="https://translate.wordpress.org/locale/ru/default/wp-plugins/log-emails" rel="nofollow ugc">the Russian translation team</a></li>
</ul>
<p>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>.</p>


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

LogStore vs Log Emails