MultiCmsManager

PHP errors

PHP fatal error monitoring for WordPress and Joomla

A fatal error on an inner page, the checkout or the admin area goes unnoticed by uptime checks. The agent sees it the moment it happens.

The problem

The home page works. The checkout doesn’t.

After a PHP or plugin update, a single page can stop working. Home page uptime stays at 100% and nobody reads the hosting logs.

Your client notices when the orders stop.

How it works

The agent listens only for the errors that matter.

  1. 1

    Fatal error handler

    During visits the agent only records fatal errors, without slowing the site down.

  2. 2

    Signed event

    The error is sent to the platform with file, line and message, signed.

  3. 3

    Grouped alert

    You get one alert per distinct error, not one per visit.

In detail

Especially useful after updates.

  • File, line and message, with the path relative to the site
  • One alert per error, not one per visit
  • Used by safe updates to decide whether to roll back
  • No impact on normal visits

FAQ

Frequently asked questions

Does recording errors slow the site down?

No: the agent only registers a handler for fatal errors, which runs only once the page has already stopped with an error.

Is any visitor data sent?

No, only the error message, the file and the line.

Try it on your clients’ sites.

During the beta we welcome agencies in small groups and set up the first sites together.