webheadcoder

<p>This plugin uses hooks in the opposite way most plugins do.  You add <code>do_action</code> where you want to do some logging and this plugin will save it to the database only when active.</p>
<h4>Log Activity</h4>
<p>This plugin now logs plugin activity (when activated, deactivated, deleted, updated, installed), when wordpress is updated, and when functions are used wrong or deprecated.</p>
<p>Example:</p>
<pre><code>do_action( 'wp_log_info', 'So far ok', 'Details of what is ok.' );
if ( $something_bad_happened ) {
    do_action( 'wp_log_error', 'This Happened!', 'Details of what happened.' );
    ...
}
</code></pre>
<p>See Tools->Logs to view, delete, and export the logs on the admin side.  Only users with the manage_options capability will have access.</p>
<p>This plugin automatically logs deprecated and doing_it_wrong errors.  The rest is what you add to your code.</p>
<p>You can log what functions will be run for a specific action or filter.  For example if you want to see what runs in the ‘init’ hook:</p>
<pre><code>function check_init_hook() {
    do_action( 'wp_log_debug_hook', 'init' );
}
add_filter( 'init', 'check_init_hook', 0 );
</code></pre>
<p>The following are the different levels of logging to add to your code.  You can use any level how you see fit, the descriptions of each level are just guidelines.</p>
<h4>Emergency</h4>
<p>System is unusable<br />
    do_action( ‘wp_log_emergency’, $label, $message );</p>
<h4>Alert</h4>
<p>Action must be taken immediately.<br />
    do_action( ‘wp_log_alert’, $label, $message );</p>
<h4>Critical</h4>
<p>Critical conditions.<br />
    do_action( ‘wp_log_critical’, $label, $message );</p>
<h4>Error</h4>
<p>Runtime errors that do not require immediate action but should typically be logged and monitored.<br />
    do_action( ‘wp_log_error’, $label, $message );</p>
<h4>Warning</h4>
<p>Exceptional occurrences that are not errors.<br />
    do_action( ‘wp_log_warning’, $label, $message );</p>
<h4>Notice</h4>
<p>Normal but significant events.<br />
    do_action( ‘wp_log_notice’, $label, $message );</p>
<h4>Info</h4>
<p>Interesting events.<br />
    do_action( ‘wp_log_info’, $label, $message );</p>
<h4>Debug</h4>
<p>Detailed debug information.<br />
    do_action( ‘wp_log_debug’, $label, $message );</p>


WP Log Action

Add error or debug logging in your code and leave it there.  Logs will only be recorded with this plugin, otherwise will be ignored.

Simon Wheatley

<p>This plugin adds a page in the admin area where you can see all the queued Cron events, when they are due, which schedule they are on (or if they are one off) and which hook they will call. Future development might include:</p>
<ul>
<li>Removing Cron events</li>
<li>Seeing which functions/methods are currently called by which hooks</li>
<li>Manually adding Cron events</li>
<li>Editing Cron events</li>
</ul>
<p>However, do not hold your breath! Development for this plugin will be as and when I need it, or when someone submits a handy patch. I’m definitely open to co-development on this one, so if you want to join in then <a href="http://www.simonwheatley.co.uk/contact-me/" rel="nofollow ugc">contact me</a>.</p>
<p>Any issues: <a href="http://www.simonwheatley.co.uk/contact-me/" rel="nofollow ugc">contact me</a>.</p>


Cron View

Allows you to view all WP Cron events. Handy for development.

WP Log Action vs Cron View