Error Monitor & Notifier

FAQ

How does the plugin send error notifications if my site is down or returns a 500 Internal Server Error?

Error Monitor & Notifier hooks into PHP’s shutdown function — a special handler that runs even after fatal errors occur. This means the plugin can detect and report issues like Fatal Error, ParseError, Uncaught Exception, memory limit exhaustion, and other critical PHP crashes.

Even when your site shows a white screen of death (WSOD) or returns a 500 error, the plugin captures detailed information about the error — including stack trace, file and line number, URL, user agent, and more — and sends it via email or Telegram right before PHP stops execution.

This ensures you’re notified of problems the moment they happen, so you can fix them fast — even if no one reports the issue manually.

How do I stop getting dozens of duplicate error notifications?

Enable the «Skip repeated errors» setting.

During development or on live sites, you might receive tens or even hundreds of alerts for the same error. When this option is enabled, the plugin generates a unique hash for each error and skips sending duplicates, reducing spam significantly.

Tip: Temporarily disable notifications for specific error types while fixing bugs. Re-enable them once the issue is resolved.

Can uncaught exceptions crash my site?

No — thanks to the enot_exception_handler_should_exit filter, uncaught exceptions won’t crash your site.

Error Monitor & Notifier catches 100 % of uncaught exceptions and errors from PHP code — including Error, Exception, and custom exception types. Even if an exception isn’t handled in a try-catch block or comes from a theme/plugin/core, the plugin intercepts it before PHP terminates the script.

Using the enot_exception_handler_should_exit filter, you can decide whether to exit the script or continue execution safely:

add_filter('enot_exception_handler_should_exit', static function (bool $should_exit, \Throwable $e): bool {
    if ($e instanceof MyCustomException) {
        my_logger()->log("Caught exception: " . $e->getMessage());
        return false; // Prevent script termination
    }

    return $should_exit;
}, 10, 2);

Can I ignore certain errors — like warnings from WooCommerce?

Yes — use the enot_ignore_error filter.

Sometimes you want to suppress noisy or non-critical errors from third-party plugins like WooCommerce or themes. Here’s how:

add_filter('enot_ignore_error', static function (bool $ignore, \ErrorException $e): bool {
    if ($e->getSeverity() === E_WARNING && strpos($e->getFile(), '/plugins/woocommerce/') !== false) {
        return true; // Ignore this error
    }

    return $ignore;
}, 10, 2);

Best practice: Add this to mu-plugins/enot-ignore-error.php to ensure it runs early, even during cron events or AJAX requests.