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.

Stefan Boonstra

<p>Developer Tools currently only supports logging of variables, errors and exceptions. Features such as profiling a<br />
website’s database queries and server memory usage are not yet supported.</p>
<h4>Features</h4>
<ul>
<li>Log any type of variable</li>
<li>Log any catchable error or exception</li>
<li>Watch for new log entries through the backend interface</li>
<li>No bloating the live environment with developer dumps</li>
<li>That’s it for now 🙂</li>
</ul>
<h4>Need the (uncompressed) source code?</h4>
<p>Find the Slideshow project’s source code in my <a href="https://github.com/Boonstra/WordPress-Developer-Tools" rel="nofollow ugc">GitHub</a> repository. The<br />
uncompressed files can be compiled using <a href="http://alphapixels.com/prepros/" rel="nofollow ugc">Prepros</a>, or <a href="http://incident57.com/codekit/" rel="nofollow ugc">CodeKit</a>.</p>
<h3>Links</h3>
<ul>
<li><a href="http://stefanboonstra.com/" rel="nofollow ugc">Stefan Boonstra</a></li>
<li><a href="https://github.com/Boonstra/WordPress-Developer-Tools" rel="nofollow ugc">GitHub</a></li>
</ul>


Basic Developer Tools

Basic Developer Tools helps developers to log any variable, error or exception of which they need the value, without bloating their live environment.

LogStore vs Basic Developer Tools