# Compat_Monitor

Updates to Clanbite itself come from wordpress.org (or an auto-update, or FTP) and the update server cannot gate them. This class is the safety net on the site: any plugin whose main file declares `Requires Clanbite: <constraint>` is checked against the Clanbite that is actually installed, and when it does not fit it is **deactivated** (silently, so none of its code runs) instead of being left to fatal the site. It also covers the add-ons' other declared needs: `Requires Clanbite Add-ons`, `Requires PHP` and `Requires at least`.

When the check runs:
 - right after Clanbite or any plugin is updated or installed (using the **new** version found on disk, before the next request
   loads old add-ons on a new core),
 - right after a plugin is activated,
 - on the first request after anything relevant changed (an FTP update, a manual downgrade).

What it does: deactivates the plugin, remembers why (`clanbite_disabled_addons`), shows a notice and a Site Health entry, warns before a
Clanbite update that would turn add-ons off, and **re-enables** what it disabled as soon as the plugin is compatible again (for
example after the add-on is updated). Opt out with the `clanbite_addon_guard_enabled` filter or the `CLANBITE_DISABLE_ADDON_GUARD`
constant. Plugins without a `Requires Clanbite` header are not touched, except first-party add-ons (they use the Clanbite update
server), which are assumed to be built for Clanbite 1.x.

## Changelog

| Version | Description |
| --- | --- |
| 1.6.0 | Introduced |
