JS Error Logger

Skildring

The plugin catches most JS errors, logs them, and displays them in a dashboard widget.

Here are some of its features:

  • Except for the plugin settings, there is no database storage involved. Log is written in a «.log» file.
  • Display latest JS errors in a dashboard widget.
  • Refresh errors from the dashboard widget.
  • See the full error log on a separate page.
  • Ignore errors if the user agent contains a specific string.
  • Ignore errors if the error contains a specific string.
  • Ignore errors if the script url contains a specific string.
  • See which page and which script triggered the errors.
  • Choose the maximum amount of errors to log per page load.
  • Exclude logging errors from specific post types.
  • Choose how ajax calls are made.

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: add_filter('jserrlog_max_log_entries',function(){return 200;})

Multisite

The plugin works with multisite. There’s one error log per site.

Skjermbilete

  • The JS Error Logger dashboard widget
  • The full error log from within the plugin settings
  • Some of the settings

Installasjon

  1. Visit the Plugins page within your dashboard and select «Add New»
  2. Search for «JS Error Logger»
  3. Click «Install»

Omtalar

14. januar 2025 1 reply
My users are having an annoying issue on the frontend of my website that I cannot reproduce. It’s causing chaos, this plugin seems to be exactly what I need to get to the bottom of this!
Les 1 omtale

Bidragsytarar og utviklarar

“JS Error Logger” is open source software. The following people have contributed to this plugin.

Contributors

“JS Error Logger” er omsett til 1 språk. Takk til omsetjarane for bidraga deira.

Omset “JS Error Logger” til ditt eige språk.

Interested in development?

Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.

Endringslogg

1.2

  • Accessibility improvements
  • Fix: Make sure the mu-plugin is also deleted when deactivating the plugin, and not just when uninstalling it
  • Added 3 more settings to the UI that were previously only accessible through WP filters

1.1.11

  • Fix: Properly dequeue the early loaded script in the front-end, if js error logging is not enabled

1.1.10

  • Security hardening
  • Documentation of variables for the translators
  • Minor Fix: Ensure the mu-plugins directory is writable before creating the early loader, to avoid PHP warnings

1.1.9

  • Fix: Properly dequeue the early loaded script in admin, if back end logging is not enabled

1.1.7

  • Improvement: better update mechanism to make sure the mu-plugin also gets updated

1.1.6

  • New: it is now possible to also log back end js errors

1.1.5

  • Fix: An HTML attribute was escaped with wp_kses instead of esc_attr, which could lead to some display issues if double quotes were in the attribute text

1.1.4

  • Fix: When the dashboard widget was initially empty, then refreshed, and an error was there, the «View» button was not clickable

1.1.3

  • Fix: A change in the ID of the dashboard widget was preventing the «Refresh log» button from working properly

1.1.2

  • Fix: Removed the «string» return type on rewrite_script_src to prevent potential issues

1.1.1

  • Fix: issue with special character encoding
  • Fix: Missing trailing slash during the creation of the «js-error-logger-log» directory
  • Improvement: Plugin should detect the most popular caching plugins, and remind users to clear their cache after changing some settings

1.0

  • Initial Release