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.

Andrew Nacin

Aaron Jorbin

<p>This plugin logs the usage of deprecated files, functions, and function arguments. It identifies where the deprecated functionality is being used and offers the alternative if available.</p>
<p>This is a plugin for developers. WP_DEBUG is not needed, though its general usage is strongly recommended. Deprecated notices normally exposed by WP_DEBUG will be logged instead.</p>
<p>This plugin also logs incorrect function usage, which WordPress started reporting in 3.1.</p>
<p>Please report any bugs to plugins in a <a href="https://wordpress.org/support/plugin/log-deprecated-notices" rel="ugc">support thread</a>.</p>
<p>This is young software. It works, but there’s a lot left on the todo (check out the Other Notes tab). Have an idea? Let me know.</p>
<h3>Ideas</h3>
<p>These are the various things on the @todo:</p>
<ul>
<li>Plugin identification. Also, an unobstrusive note on plugins page next to said plugins.</li>
<li>Perhaps the ability to auto-purge the log.</li>
<li>Ability to filter on file or plugin in which the deprecated functionality is used.</li>
<li>Offer some kind of better multisite support.</li>
</ul>
<p>Want to add something here? I’m all ears. plugins at <a href="http://andrewnacin.com/" rel="nofollow ugc">andrewnacin.com</a> or @<a href="http://twitter.com/nacin" rel="nofollow ugc">nacin</a> on Twitter.</p>
<p>I will prioritize these tasks based on feedback, so let me know what you’d like to see.</p>


Log Deprecated Notices

Very easy to use and useful for debugging your own plugins.

(CA)

Senzill d'utilitzar i necessari per fer la depuració de les extensions.

Very easy to use and useful for debugging

I had a deprecated notice and this logged it perfectly.

A+++ Would use again


Always on dev site. Awesome! Thank you!


Must have for dev

Logs the usage of deprecated files, functions, and function arguments, and identifies where the deprecated functionality is being used.

LogStore vs Log Deprecated Notices