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.

Poly Plugins

<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/k1o4zZC6dzs?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<p><strong>About</strong><br />
Debugging WordPress can sometimes be a pain, our goal is to make it easy, which is why Loginator was built with this in mind. From creating a log folder, to securing it from prying eyes, Loginator is here to save you time and resources, so you can focus on creating astonishing applications. Once activated, Loginator essentially becomes a core part of WordPress, which is why we disable deactivation as it is highly recommended to not uninstall Loginator until you have removed all references to the loginator function inside your WordPress installation.</p>
<p><strong>Update</strong><br />
2.0 has been released with backwards compatibility with 1.0. Your loginator function calls will still work so you can continue to use it, or our new static methods.</p>
<p><strong>Functional Example</strong></p>
<pre><code>loginator('Logging this message', array('flag => 'd', 'id' => '', 'file' => 'logger', 'pipedream' => 'https://your-id-here.m.pipedream.net'));
</code></pre>
<p><strong>Static Method Examples</strong></p>
<pre><code>Loginator::emergency('log data here'); // Email triggers to site admin or configured emails
Loginator::alert('log data here');
Loginator::critical('log data here'); // Email triggers to site admin or configured emails
Loginator::error('log data here');
Loginator::warning('log data here');
Loginator::notice('log data here');
Loginator::info('log data here');
Loginator::debug('log data here'); // PipeDream flag is set to true by default
Loginator::success('log data here');
</code></pre>
<p>You can also pass arguments</p>
<pre><code>$args = array(
  'flag'      => 'd',
  'id'        => 23,
  'file'      => 'test',
  'pipedream' => false,
);

Loginator::info('log data here', $args);
</code></pre>
<p>Features:</p>
<ul>
<li>Global Enable/Disable</li>
<li>Flags for Errors, Debug, and Info</li>
<li>Creates separate files based on flags<br />
Our beautiful comments follow WordPress Developer Standards, that when paired with Visual Studio Code or other supporting IDE\’s will elaborately explain how to use the loginator function</li>
<li>Auto detect if data being logged is an array and pretty prints it to the file</li>
<li>Disable Loginator deactivation to prevent function not existing errors</li>
<li>Email on CRITICAL flag</li>
<li>Pipe Dream logging</li>
</ul>


Loginator

Adds a simple global function for logging to files for developers.

WP Log Action vs Loginator