Automattic

Donncha O Caoimh (a11n)

<p>This plugin logs the activity of supported plugins to a file, making it easier to figure out why there’s a problem.</p>
<p>If you have been asked to install this plugin because of a support issue then installing this plugin is just like installing any other plugin. Once installed, go to Settings->WP Logger and enable logging. If you have a number of supported plugins enable the one you are interested in.</p>
<p>Developers who want to use this plugin to add logging to their own plugin should see the Developers section of this documentation.</p>
<p>Mark Jaquith’s <a href="https://wordpress.org/extend/plugins/monitor-pages/" rel="ugc">Monitor Pages</a> plugin was used as a template for this plugin. Thanks Mark!</p>
<h4>Developers</h4>
<p>Other plugins can use this plugin to record important events which are then dumped to a log file. Plugins must add the event to a global array in the following way:</p>
<pre><code>$GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = 'Some important event';
</code></pre>
<p>Plugins must also add themselves to a list of enabled plugins. This will make it easier for blog owners to filter out which plugin they want to debug on the settings page. Add and edit the following code so it is executed when the plugin is loaded.</p>
<pre><code>$GLOBALS[ 'wp_log_plugins' ][] = 'name_of_plugin';
</code></pre>
<p>A hypothetical example might be a plugin (let’s call it “Big A”) that uses the output buffer to change the letter “a” to “A”. The events recorded by this might include the following:</p>
<pre><code>$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Created output buffer';
$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Output buffer callback';
$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Replaced a with A in page';
</code></pre>
<p>This plugin takes the “wp_log” array and dumps it to a file in the upload directory of the blog it’s activated on. The file is linked from the plugin settings page and can be deleted on that page too. The file is a simple text file and is not protected in any way so be careful if auth cookies are logged by a plugin.</p>
<p>A “log” function isn’t included but if you want to add one to your plugin check the constant WP_DEBUG_LOG is defined before adding to the log array. If your plugin doesn’t use a class make sure that you call the log function a unique name so it doesn’t conflict with other plugins.</p>
<pre><code>function log( $message ) {
    if ( defined( 'WP_DEBUG_LOG' ) )
        $GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = $message;
}
</code></pre>


WP Debug Logger

A plugin that makes it easy to log code activity to a file.

Matt Gibbs

<h4>Log and view all WP HTTP requests</h4>
<p>How long do [core / plugin / theme] update checks take to run? What data about my site is being sent out? What about all those ajax requests? The answers to these questions are just a few clicks away.</p>
<p>This plugin logs all WP_HTTP requests and displays them in a table listing for easy viewing. It also stores the runtime of each HTTP request.</p>
<h4>Available Hooks</h4>
<p>Customize the length (in days) before older log items are removed:</p>
<pre>
add_filter( 'lhr_expiration_days', function( $days ) {
    return 7; // default = 1
});
</pre>
<p>Don’t log items from a specific hostname:</p>
<pre>
add_filter( 'lhr_log_data', function( $data ) {
    if ( false !== strpos( $data['url'], 'wordpress.org' ) ) {
        return false;
    }
    return $data;
});
</pre>
<p>In the above example, the <code>$data</code> array keys correspond to columns within the <code>lhr_log</code> database table.</p>
<h4>Important Links</h4>
<ul>
<li><a href="https://github.com/FacetWP/log-http-requests" rel="nofollow ugc">Github <span aria-hidden="true" class="wp-exclude-emoji">→</span></a></li>
</ul>


Log HTTP Requests

Exactly what you need when you debug API requests. Thanks!

Excellent.

Works exactly as advertised so far. Really helpful for figuring out if any plugins/themes are phoning home unnecessarily.
FYI after you've used this plugin to find out who's calling where, you can add "define('WP_HTTP_BLOCK_EXTERNAL', true);" to your wp-config.php to block ANY requests outwards. You'll probably want to also whitelist domains you trust with the WP_ACCESSIBLE_HOSTS parameter. E.g. if you're polling data from instagram or youtube api, and what not.
(Credit to Markus Philipp Stefanko for those tips)

Really helpful!

This plugin has become indispensable for plugin development particularly debugging API requests. Thank you very much.

Thank You!

The Log HTTP Requests plugin might be my favorite troubleshooting tool of all time. It's helped me pinpoint intermittent issues that we never would have seen otherwise. THANK YOU, FacetWP!  :)

My favorite troubleshooting tool

The plugin is very good and useful and I am very grateful to its developer. 

Bravo 😍

This plugin is so helpful for tracking down whether an HTTP request was made at all, and when it was, what data was sent and what response was received. It's invaluable for tracking down bugs tied to unexpected responses and requests.

Great Troubleshooting Aid


This plugin has proven to be an indispensable tool for tracking and analyzing HTTP requests. Its ability to reveal whether a request was made, along with detailed insights into the transmitted data and received responses, is simply remarkable. The clarity it provides is instrumental for troubleshooting and optimizing processes. A must-have for anyone dealing with HTTP interactions


Invaluable Insight for HTTP Requests

The plugin does exactly what it says it does, and works perfect every time.

I've used it quite a lot for troubleshooting purposes and have yet to discover any issues.

Kind regards, Jarno 

WP Debug Logger vs Log HTTP Requests