JFG Media

<p>The plugin catches most JS errors, logs them, and displays them in a dashboard widget.</p>
<p>Here are some of its features:</p>
<ul>
<li>
Except for the plugin settings, there is no database storage involved. Log is written in a “.log” file.
</li>
<li>
Display latest JS errors in a dashboard widget.
</li>
<li>
Refresh errors from the dashboard widget.
</li>
<li>
See the full error log on a separate page.
</li>
<li>
Ignore errors if the user agent contains a specific string.
</li>
<li>
Ignore errors if the error contains a specific string.
</li>
<li>
Ignore errors if the script url contains a specific string.
</li>
<li>
See which page and which script triggered the errors.
</li>
<li>
Choose the maximum amount of errors to log per page load.
</li>
<li>
Exclude logging errors from specific post types.
</li>
<li>
Choose how ajax calls are made.
</li>
</ul>
<h4>Developer hooks and filters</h4>
<p>The plugin cleans the log every 24 hours, to only keep the last 100 entries.<br />
You may use the “jserrlog_max_log_entries” WP filter to enable more or less entries, by returning an integer: <code>add_filter('jserrlog_max_log_entries',function(){return 200;})</code></p>
<p>Alter error data:<br />
You may use the “jserrlog_pre_insert_error” WP filter to modify the error data before it’s inserted into the log file: <code>add_filter('jserrlog_pre_insert_error',function($error_data){return $error_data;})</code></p>
<p>Trigger integrations:<br />
You may use the “jserrlog_after_log” WP hook to trigger an action (Slack notification, etc.) after an error was logged: <code>add_action('jserrlog_after_log',function($error_data){//do something})</code></p>
<p>Backup old errors:<br />
You may use the “jserrlog_before_log_maintenance” WP hook to trigger an action (archive errors, etc.) before old errors are deleted: <code>add_action('jserrlog_before_log_maintenance',function($errors){//do something})</code></p>
<p>Request hardening:<br />
You may use the “jserrlog_enforce_same_host_origin” WP filter to require same-host Origin/Referer checks for logging requests (default true): <code>add_filter('jserrlog_enforce_same_host_origin',function(){return true;})</code><br />
You may use the “jserrlog_rate_limit_requests” and “jserrlog_rate_limit_window” WP filters to control request throttling (defaults: 60 requests per 60 seconds): <code>add_filter('jserrlog_rate_limit_requests',function(){return 120;}); add_filter('jserrlog_rate_limit_window',function(){return 60;});</code><br />
You may use the “jserrlog_max_payload_bytes”, “jserrlog_max_batch_errors” and “jserrlog_max_error_field_length” WP filters to limit incoming payload sizes (defaults: 16384 bytes, 20 errors per batch, 512 chars per field): <code>add_filter('jserrlog_max_payload_bytes',function(){return 32768;});</code><br />
You may use the “jserrlog_duplicate_window” WP filter to suppress duplicate errors for a short period (default: 60 seconds): <code>add_filter('jserrlog_duplicate_window',function(){return 30;});</code></p>
<h4>Multisite</h4>
<p>The plugin works with multisite. There’s one error log per site.</p>


JS Error Logger

Logs front-end javascript errors, and displays them in a dashboard widget

Think201

<h4>Salient Features</h4>
<ul>
<li>Report issues faced by your users</li>
<li>
<p>Plugin allows you to integrate Echoza for your website</p>
</li>
<li>
<p>Like the plugin or want features? Tweet to us <a href="https://twitter.com/think201/" rel="nofollow ugc">@think201</a></p>
</li>
</ul>
<h4>Plugin Support</h4>
<p>Dedicated Support: talk to us on Twitter <a href="https://twitter.com/think201/" rel="nofollow ugc">@think201</a></p>
<p>To raise issues or if you have a question for us, post to the support forum here https://wordpress.org/support/plugin/echoza and we are happy to help.</p>
<h4>Requirements</h4>
<ul>
<li>WordPress 4.6 or greater</li>
<li>PHP 5.6 or greater (7.0 recommended)</li>
<li>MySQL 5.2 or greater (5.x recommended)</li>
</ul>


JS Error Logger vs Echoza