benecaster_manager_addon_install_failed
Fires when an install was refused or failed. Nothing was installed, and nothing was removed: an install runs only for an add-on that is not already on the site, so there is no earlier copy to lose. An add-on that is already there is activated instead, and fires benecaster_manager_addon_installed.
Order. Each pair fires once, nested: benecaster_manager_addon_before_update → benecaster_manager_package_before_verify → (benecaster_manager_package_verified … benecaster_manager_addon_updated) or (benecaster_manager_package_rejected → benecaster_manager_addon_update_failed). An install fires benecaster_manager_addon_before_install → (benecaster_manager_addon_installed or benecaster_manager_addon_install_failed), with the package actions in between. The Manager’s own update fires only the package actions. Nothing an action returns is read.
Fired by the Benecaster Add-on Manager, not by Benecaster itself, and only while the Manager is active, so no function_exists() guard is needed. No hook can switch the signature check off, change the updates host, change where the download goes or where the site token is sent, or turn a refusal into an install. No argument carries a site token.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
$slug |
string |
— | The add-on's entitlement slug, such as `benecaster-addon-guest-manager`. |
$error |
WP_Error |
— | The REST error the install route returns, its message already filtered by `benecaster_manager_install_error_message`. |
Need this built rather than just documented? See our services →