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.

chandima

<p>Display log messages from PHP in the browser console in Safari, Firefox (with firebug), and Opera (with the new Dragonfly debugging environment). Essential debugging tool for<br />
plugin and theme developers. You no longer have to use ‘print_r’ statements from PHP to figure out what is going<br />
on in the code, which more often than not, messes up the DOM and HTML layout. Displays complex PHP structures like arrays and objects<br />
in pretty print.</p>
<p><strong>Features</strong></p>
<ul>
<li>Log debug messages directly from themes and plugins.</li>
<li>Display log messages in the browser console, without muddying up the browser display.</li>
<li>Displays complex structures such as arrays and objects in pretty print.</li>
<li>Shows the line number and file from where the message was logged ( you won’t lose track of log statements ).</li>
</ul>
<p>For more info, comments, and feature requests, visit <a href="http://www.turingtarpit.com/2009/05/wplogger" title="Wordpress Logger" rel="nofollow ugc">the plugin homepage</a>.</p>
<h3>Credits</h3>
<p>Code that forces the wplogger plugin to load first was adapted from the WordPress<br />
<a href="http://inchoo.net/wordpress/wordpress-firephp-plugin/" title="FirePHP plugin" rel="nofollow ugc">FirePHP plugin</a><br />
developed by Ivan Weiller.</p>
<p>This plugin is based on <a href="http://pear.php.net/package/Log" title="PEAR Log" rel="nofollow ugc">PEAR Log</a>, the logging framework that is part of the<br />
PHP PEAR library. Current maintainers Jon Parise, Jan Schneider, and Chuck Hagenbuch. PEAR Log is based on code first<br />
developed for the Horde 1.3 framework – original authors Chuck Hagenbuch, and Jon Parise.</p>
<h3>Release Notes</h3>
<p><strong>0.3</strong> : Added support for Opera ;</p>
<p><strong>0.2.2</strong> : Fixed formatting issues in <em>readme.txt</em> file;</p>
<p><strong>0.2.1</strong> : Added more detail to the <em>readme.txt</em> file;</p>
<p><strong>0.2</strong> : First official public release;</p>
<p><strong>0.1</strong> : First internal release;</p>


WordPress Logger

Display log messages during plugin and theme development on the console in Safari and Firefox (with Firebug) browsers.

LogStore vs WordPress Logger