Automattic

Donncha O Caoimh (a11n)

This plugin logs the activity of supported plugins to a file, making it easier to figure out why there’s a problem.
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.
Developers who want to use this plugin to add logging to their own plugin should see the Developers section of this documentation.
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!
<h4>Developers</h4>
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:
<pre><code>$GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = 'Some important event';
</code></pre>
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.
<pre><code>$GLOBALS[ 'wp_log_plugins' ][] = 'name_of_plugin';
</code></pre>
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:
<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>
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.
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.
<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.

Max Chirkov

Joris Le Blansch

Simple log of user logins. Tracks user name, time of login, IP address and browser user agent.
Features include:
<ol>
<li>ability to filter by user name, successful/failed logins, month and year;</li>
<li>export into CSV file;</li>
<li>log auto-truncation;</li>
<li>option to record failed login attempts.</li>
</ol>
Translations:
<ul>
<li>German [de_DE] by Philipp Moore</li>
<li>Russian [ru_RU]</li>
<li>Ukrainian [ua_UA]</li>
<li>
French [fr_FR] by Mehdi Hamida
</li>
<li>
Author: Max Chirkov
</li>
<li>Author: Joris Le Blansch</li>
</ul>
<h4>Translation</h4>
If you would like to contribute, the POT file is available in the languages folder. Translation file name convention is sll-{locale}.mo, where {locale} is the locale of your language. Fore example, Russian file name would be sll-ru_RU.po.

Simple Login Log

Хороший плагин и полезный

Simple login log

This plugin keeps a log of WordPress user logins. Offers user and date filtering, and export features.

WP Debug Logger vs Simple Login Log