Jan Štětina

This plugin provides a simple API for storing miscellaneous log entries and their overview in admin area (or network 
admin area, if activated on a multisite).
Developed for private use (heavily used by my other plugins), but has perspective for more extensive usage. I can’t guarantee any support in the future nor further development, but it is to be expected. Kindly inform me about bugs, if you find any, or propose new features: <a href="mailto:zaantar@zaantar.eu?subject=[wordpress-logging-service]" rel="nofollow ugc">zaantar@zaantar.eu</a>.
See Usage and FAQ for more information.
<h3>API</h3>
Definitions:
<pre><code>WLS
</code></pre>
<ul>
<li>
should be checked before using any wls function
WLS_VERSION
</li>
<li>
should(!) contain current WLS version string
</li>
<li>
severity levels:
<pre><code>WLS_NOCATEGORY = 0

WLS_INFO = 1

WLS_NOTICE = 2

WLS_WARNING = 3

WLS_ERROR = 4

WLS_FATALERROR = 5
</code></pre>
</li>
</ul>
Functions:
<pre><code>wls_is_registered( $category_name );
</code></pre>
<ul>
<li>
returns <code>true</code>, if <code>$category_name</code> is registered
wls_register( $category_name, $description );
</li>
<li>
registers <code>$category_name</code> as a log category.
</li>
<li>
<code>$description</code> will be shown in admin area
wls_clear( $category_name );
</li>
<li>
deletes all log entries of category $category_name
wls_unregister( $category_name );
</li>
<li>
same as wls_clear & removes category $category_name from the list
wls_log( $category_name, $text, $user_id, $date, $blog_id, $severity = 0 );
</li>
<li>
inserts a new log entry into specified category
</li>
<li><code>$date</code> must be formated according to ISO 8601</li>
<li>
<code>$severity</code> should be one of defined severity levels (see above)
wls_simple_log( $log_name, $text, $severity = 0 );
</li>
<li>
equivalent to <code>wls_log( $category_name, $text, get_current_user_id(), date( 'c' ), get_current_blog_id(), $severity);</code>
</li>
</ul>

WordPress Logging Service

Provides a simple API for storing miscellaneous log entries and their overview in admin area.

Andrew Nacin

Aaron Jorbin

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.
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.
This plugin also logs incorrect function usage, which WordPress started reporting in 3.1.
Please report any bugs to plugins in a <a href="https://wordpress.org/support/plugin/log-deprecated-notices" rel="ugc">support thread</a>.
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.
<h3>Ideas</h3>
These are the various things on the @todo:
<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>
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.
I will prioritize these tasks based on feedback, so let me know what you’d like to see.

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.

WordPress Logging Service vs Log Deprecated Notices