kunalb

<ul>
<li>Call <code>kb_debug</code> with any arguments that you want to log and they will be pretty printed at the end of the document.</li>
<li>To log and show a list of all warnings, errors and notices generated by your plugin, add  <code>?KB_Debug_Errors</code> to your URL. </li>
<li>To see a list of all hooks in the order they fire as well as what arguments they are called with and what functions run on them (again, in which order),<br />
add a <code>?KB_Debug_Hooks</code> to the URL.</li>
</ul>
<p>To see both just add ?KB_Debug_Errors&KB_Debug_Hooks. (Essentially $_GET[var] must be set to enable that feature).</p>
<h3>Features</h3>
<ul>
<li>Logs and displays all warnings, errors, etc. alongwith their context.</li>
<li>Logs and displays all hooks alongwith the argument(s) each hook is called with and the functions that run on that particular hook (in order).</li>
</ul>


kb_debug.php

Jarred Kennedy

Grant Derepas

<p>This plugin makes it safe and easy to work with email in your testing environments. When enabled the plugin catches any instance of wp_mail and redirects the email to your chosen email address.</p>
<p>Key Features</p>
<ul>
<li>Set a custom email address target to redirect emails to</li>
<li>Emails intercepted will have [Debug] added to the subject line to make them identifyable in your inbox</li>
<li>Interception rules can be limited by plugin allowing you to debug a specific plugin on your live site without affecting other operations</li>
<li>Notice in the WP Admin Bar when enabled.</li>
</ul>
<h4>For Bugs Reports or to contribute</h4>
<p>Please visit our public <a href="https://github.com/GForceWeb/WP-Email-Debug/" rel="nofollow ugc">GitHub Repo</a></p>


WP Email Debug

Debugging emails can be incredibly frustrating. This makes it so, so much easier!



Works perfectly and great for debugging

The plugins still works. I use it regularly for development.

Still great

Never accidentally send users emails from your testing sites again!

kb_debug.php vs WP Email Debug