JFG Media

The plugin catches most JS errors, logs them, and displays them in a dashboard widget.
Here are some of its features:
<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>
The plugin cleans the log every 24 hours, to only keep the last 100 entries. 
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>
Alter error data: 
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>
Trigger integrations: 
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>
Backup old errors: 
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>
Request hardening: 
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> 
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> 
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> 
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>
<h4>Multisite</h4>
The plugin works with multisite. There’s one error log per site.

JS Error Logger

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

WikiFleeksMedia

wikifleeksmedia

BugPost adds a lightweight bug reporting button to your site’s frontend. When clicked, it opens a clean overlay panel where visitors or team members can describe an issue. Browser details, operating system, viewport size, page URL, page load time, and JavaScript console errors are captured automatically — no extra effort needed from the reporter.
Key Features:
<ul>
<li>One-click reporting — A “Report” tab on the right side of every page opens a simple form.</li>
<li>Auto-captured context — Browser name and version, OS, viewport dimensions, page URL, page load time, and console errors are sent along with every report.</li>
<li>Console error capture — JavaScript errors and unhandled promise rejections are logged automatically and attached to the report.</li>
<li>Reporter fields — Optional name and email fields let reporters identify themselves.</li>
<li>Honeypot spam protection — A hidden field traps bots without annoying humans with CAPTCHAs.</li>
<li>Rate limiting — 3 reports per IP per hour prevents abuse.</li>
<li>“Me too” duplicate grouping — When multiple reports target the same page, earlier open reports get a +1 count so you can see which issues affect the most people.</li>
<li>Visibility modes — Choose Beta (logged-in users only) or Public (everyone). Turn it off entirely when not needed.</li>
<li>Admin dashboard — All reports in a familiar WordPress list table with status badges, reporter info, page URL, and date columns.</li>
<li>Report detail view — Each report has a full meta box showing all captured context data.</li>
<li>Status workflow — Mark reports as New, Acknowledged, In Progress, Resolved, or Closed.</li>
<li>CSV export — Download all reports as a CSV file for use in spreadsheets or external tools.</li>
<li>Customizable button color — Match the report button to your site’s brand via a color picker.</li>
<li>Fully translatable — All strings use WordPress i18n functions with the <code>bugpost</code> text domain.</li>
</ul>
What this plugin does NOT do (by design):
<ul>
<li>No external API calls, no tracking, no phoning home.</li>
<li>No CDN dependencies — all assets are bundled locally.</li>
<li>No account required to use the plugin.</li>
</ul>

BugPost

Simple frontend bug reporting overlay for WordPress. Visitors submit reports with auto-captured browser context and console errors.

JS Error Logger vs BugPost