This plugin is derived from the no longer supported
WordPress Logging Service.
Despite that it is not compatiple with it, and there is no upgrade path from one
to the other.
- No log entries generated by the plugin itself, all come from external API calls
- Organisation of log entries in freetext categories
- Severity levels
- Freetext log messages
- Entries can be marked as seen and then filtered from being displayed again
- Filtering by minimum severity level
- Sort by date, category, user name, severity or blog name (in Multisite installations)
- Access to the log page can be granted by user role
Check to test if the plugin is active:
CLGS = true
Defined severity levels:
CLGS_NOSEVERITY = 0 CLGS_INFO = 1 CLGS_NOTICE = 2 CLGS_WARNING = 3 CLGS_ERROR = 4 CLGS_FATALERROR = 5
clgs_is_registered ( $category )
$category is registered.
clgs_register ( $category, $description )
$category as a log category.
$description will be shown in the
It is good practice to use unique categories for each plugin that publishes
string $categoryAt most 190 (unicode) characters
string $descriptioncan contain HTML same as comments (filtered by
false if the category is already registered or it is too long.
clgs_clear ( $category )
deletes all log entries of
string $descriptionexisting category
returns number of deleted entries or
false if action failed.
clgs_unregister( $category );
deletes all log entries and then removes
string $descriptionexisting category
false if false if action failed.
clgs_log( $category, $text, $severity = null, $user = null, $blog_id = null, $date = null );
writes a new log entry in the specified category
string $descriptiona registered category name
string $textthe logged message, can contain HTML same as comments (filtered
int $severityone of defined severity levels (see above); if missing defaults to
int | string | WP_User $useruser id, slug or WP user object are aceptable; if missing
defaults to current user (or a placeholder if none is logged in)
int $blog_idblog id; if missing defaults to current blog
int | double | string $datea UNIX timestamp or a string recognized by
if missing defaults to current time
false if entering the log failed.
- Install from Plugins -> Add New
- Or download the .zip and extract to
- Activate the plugin from the Plugins menu. In Multisite installations, feel free
to activate as a network plugin or to leave it to individual blogs.
- Go to Settings -> Custom Logging Service for the next steps
- Minimum severity for notification: You will see the number of unseen log entries
of that level or above next to the menu entry for the log page.
- Default minimum severity filter: Which severity levels you will see in the log page.
You can change this filter later on the page.
- Roles that can manage Custom Logs: Decide who can see and interact with the log page.
- Log entries per page: Set the number of entries per page.
Generating Log messages
This plugin does not generate any log messages by itself. You need other plugins to
interact with it through the API; see the API section for details.
- Where are the logs?
Find them under Dashboard -> Selected Logs.
- I can’t find the option to add roles for log management!
If the plugin has been installed network-wide in Multisite, only the Super Admin
has access to the logs. Sorry, I don’t understand role management in Multisite.
There are no reviews for this plugin.
Contributors & Developers
“Custom Logging Service” is open source software. The following people have contributed to this plugin.Contributors
“Custom Logging Service” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “Custom Logging Service” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Compatibility with WP 4.7
Compatibility with WP 4.6
Compatibility with WP 4.5
First version, derived from zaantar’s
WordPress Logging Service