Andy Whalen

Creates a log file for network/multisite super admin actions.
The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:
<ul>
<li>change network settings (update_site_option)</li>
<li>grant super admin privileges (granted_super_admin)</li>
<li>revoke super admin privileges (revoked_super_admin)</li>
<li>upgrade blog (wpmu_upgrade_site)</li>
<li>add blog (wpmu_new_blog)</li>
<li>set blog archived (archive_blog/unarchive_blog)</li>
<li>set blog deleted (make_delete_blog/make_undelete_blog)</li>
<li>set blog mature (mature_blog/unmature_blog)</li>
<li>set blog spam (make_spam_blog/make_ham_blog)</li>
<li>delete blog (delete_blog)</li>
<li>delete user (wpmu_delete_user)</li>
<li>delete user (deleted_user)</li>
<li>change other user’s settings (edit_user_profile_update) [NOTE: doesn’t show diff]</li>
<li>change blog setting (updated_option) [NOTE: may occasionally log annoyingly large diffs]</li>
</ul>
The following actions are logged for ANY user:
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
Some actions that change data will show what the value was before and after.
Below is an example of a log entry when the user ‘smith’ has changed the Network site name from “WP Local Network” to “WP Local Networks”:
<pre><code>[Tue, 03 Sep 2013 13:45:49 +0000] [smith:1] [update_site_option] [1] [site_name] [(WP Local Network)->(WP Local Networks)] [127.0.0.1] </code></pre>
Each line in the log file will roughly follow the below example. Individual actions may log slightly different information, but the DATETIME, USERNAME, USER_ID, ACTION, and IP_ADDRESS sections should always be populated.
<pre><code>[DATETIME] [USERNAME:USER_ID] [ACTION] [AFFECTED_OBJECT_ID] [DATA_TITLE_OR_KEY] [(VALUE_BEFORE)->(VALUE_AFTER)] [IP_ADDRESS] </code></pre>

Observer

Creates a log file for network/multisite super admin actions.

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.

Observer vs Log Deprecated Notices