A white page, a broken contact form or a checkout that stops working after an update: on a WordPress site you often only notice when a visitor or your client calls. The debug.log is off, or nobody looks at it. With the errors.nl plugin every error comes in at one dashboard, with the plugin or theme where things went wrong.
1. Create a project
Create a free account at errors.nl (or log in), create an organization and a project and copy the DSN. It looks like https://<key>@ingest.errors.nl/<project>.
2. Install the plugin
Download the plugin and upload it in WordPress through Plugins > Add New Plugin > Upload Plugin. Then activate it.
3. Paste the DSN
Go to Settings > errors.nl, paste the DSN and save. Click Stuur een testfout (send a test error): within seconds it shows up under Issues in the dashboard. The plugin's settings screen is in Dutch for now.
4. Choose what you want to see
- PHP errors are on by default: fatals and uncaught exceptions.
- PHP warnings are off by default. Older plugins often produce many, and every stored error costs a credit.
- JavaScript errors from visitors are turned on with one checkbox. The script ships with the plugin itself; no external CDN is loaded.
Every error shows which plugin or theme caused it, plus the WordPress and PHP versions. So after an update you know right away which plugin to roll back.
5. Many sites? Put it in wp-config.php
If you manage sites for clients, you don't want to go through the settings screen for every site. Put the settings in wp-config.php, or in your deploy script:
define( 'ERRORSNL_DSN', 'https://<key>@ingest.errors.nl/<project>' ); define( 'ERRORSNL_ENVIRONMENT', 'production' ); define( 'ERRORSNL_RELEASE', '[email protected]' );
Create a project per client site, and you see per site what goes wrong. Credits are shared across all your projects. Also read error monitoring for web agencies.
6. Personal data
The plugin sends the error message, the stack trace with the relevant lines of code, the URL without query string and the versions of WordPress, PHP and the theme. No cookies, form data or data of logged-in users. To change or stop an event, use the errorsnl_event filter and return null to send nothing.
On top of that, errors.nl filters passwords, tokens, e-mail addresses and account numbers from every error before we store it. Read more in Error monitoring and the GDPR.
Notifications
Want to know when something goes wrong without keeping the dashboard open? Turn on e-mail notifications for your project, or connect Slack, Teams, Discord or ntfy for push notifications on your phone.