When the Query Monitor plugin is active on dev or stage sites, we get a "critical error" message in the browser and I got the following email. I haven't experienced this on production, but that may be because WP-DEBUG is disabled on production.
Subject: Your site is experiencing a technical issue
Body:
Howdy!
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Query Monitor.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.1.1
Active theme: Twenty Twenty-Three (version 1.0)
Current plugin: Query Monitor (version 3.10.1)
PHP version 8.0.22
Error Details
An error of type E_COMPILE_ERROR was caused in line 5 of the file /home/mrengyscv/dev.historyscv/wp-content/plugins/query-monitor/vendor/composer/autoload_real.php. Error message: Cannot declare class ComposerAutoloaderInitd4d7d7d11152077b8234a5ecb185a7c0, because the name is already in use
When the Query Monitor plugin is active on dev or stage sites, we get a "critical error" message in the browser and I got the following email. I haven't experienced this on production, but that may be because WP-DEBUG is disabled on production.
Subject: Your site is experiencing a technical issue
Body: