Introduction

quiet-guard/monitor-wordpress is a WordPress plugin that forwards PHP errors, exceptions and fatal shutdowns from a WordPress site to a Quiet Guard server. Once configured, your site reports into the same dashboard as your Laravel and Symfony projects, so a small agency can watch every site it maintains from one place.

What it does

The plugin boots on the WordPress plugins_loaded hook and, as soon as it is enabled and pointed at a server, installs the global PHP handlers that capture problems:

• Uncaught exceptions: anything that bubbles up to PHP's exception handler.
• PHP errors: warnings, notices and recoverable errors (it respects @-suppression and your error_reporting level).
• Fatal shutdowns: E_ERROR, E_PARSE, E_CORE_ERROR and E_COMPILE_ERROR, caught on shutdown so even a fatal that ends the request is reported.

Each captured problem is sent as a JSON payload to your Quiet Guard server's ingestion endpoint, authenticated with your per-project API key. Capture is additive: WordPress's own error handling keeps running, so the plugin never changes how your site behaves for visitors.

Built on the framework-agnostic core

The plugin is a thin WordPress adapter (namespace QuietGuard\Monitor\WordPress) around the shared PHP engine quiet-guard/monitor-php, the same core that powers the Laravel and Symfony clients. WordPress supplies the settings screen and the boot hook; the core supplies the error handlers, the payload builder, the sensitive-data scrubber and the HTTP transport.

Requirements

• PHP 8.2 or higher (declared in the plugin header and composer.json).
• A reachable Quiet Guard server and a project API key from its dashboard.
• The ext-curl extension (used by the default HTTP transport).

The plugin is distributed as Quiet Guard (version 0.2.0, MIT licence, by Alexandre Ribes). Dependency and vulnerability scanning tailored to the WordPress ecosystem, core, plugins and themes, is on the roadmap.

Where to go next

• Installation: get the plugin into wp-content/plugins/ and activate it.
• Configuration: the Settings → Quiet Guard screen and every field.
• Usage: what is captured automatically and how to verify it works.
• Upgrading: updating the plugin safely.