benecaster_sponsor_manager_after_save_sponsor
Fires once a sponsor has been created or changed on the Sponsors screen, or through POST /benecaster-sponsor-manager/v1/sponsors or PUT, PATCH /benecaster-sponsor-manager/v1/sponsors/{id}. It fires only when the write succeeded.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
$sponsor_id |
int |
— | The sponsor saved |
$fields |
array |
— | The keys sent, cleaned: `company`, `contact_name`, `contact_email` (lowercased), `notes`. On a create, every key, with `''` for those not sent |
$created |
bool |
— | `true` for a new sponsor, `false` for a change |
Example
add_action( 'benecaster_sponsor_manager_after_save_sponsor', function ( int $sponsor_id, array $fields, bool $created ): void {
if ( isset( $fields['company'] ) ) {
my_crm_rename_company( $sponsor_id, $fields['company'] );
}
}, 10, 3 );
Notes
$fields holds the contact's email: never pass it to anything public. Walkthrough: Read, create, change, archive or restore the site's sponsors and a show's sponsor campaigns from code, as the Sponsors screen does.
Affects
- Benecaster → Sponsors
- POST benecaster-sponsor-manager/v1/sponsors
- PUT, PATCH benecaster-sponsor-manager/v1/sponsors/{id}
Need this built rather than just documented? See our services →