Useful loggers for SimpleHistory for developers during development of a site or to maintain a live site.
Bring more loggers to WordPress user history plugin Simple History.
That are useful for developers during development of a site or to maintain a live site.
Post to Slack
All your events is posted to a Slack channel of your choice, using an incoming webhook. Yes, with this plugin enabled
there is no need what so ever to ever leave Slack to see what’s happening on your site or the site of your
clients or… well, on any site where you have Simple Histor and this plugin enabled.
WP_Mail-logger
See all mails sent with wp_mail(), no matter what the recipient address is.
changelog
404 logger
View page visits that load the 404 template.
JavaScript error logger
See what JavaScript errors users that visit your site is getting.
SystemLog logger
Log all messages from Simple History to the syslog on the server. With this logger enabled there is no need to use the beautiful GUI of Simple History ;).
HTTP API logger
Log all usage of HTTP calls from functions like wp_remote_post() and wp_remote_get().
You can the URL requested, the arguments posted and the full returned result, including server headers.
The time for the request to complete is also logged. Great for debugging!
Enable the loggers you want in Settings » Simple History » Developer loggers.
Example output of the WordPress Cron debug logger.
Example output of the WPMail logger. You can see the subject, who the mail is sent to, and the contents of the body.
Example output form the HTTP API logger. View method and target URL.
Details from the HTTP API logger. Even more details here, like all the headers in the response and also the full response.
Example output from the WordPress post to Slack Logger. Here you can see me failing to login, then succeeding to login, updating a plugin, and finally I log out.
simple_history/developer_loggers/enabled_loggers
to modify what plugins are enabled.simple_history/developer_loggers/slackit/settings
to modify the settings of the Slackit logger.examples.php
with some examples of filter usage.sys_getloadavg()
exists before trying to use. Could cause error on Windows.wp_remote_get()
and wp_remote_post()
.__return_empty_string
is not called _return_empty_string
…$initiator_text
in the post to Slack pluginsimple_history/developer_loggers/before_plugins_table
and simple_history/developer_loggers/before_plugins_table
.