ExpressionEngine Docs

# Category Model Extension Hooks

- `before_category_insert($category, $values)`
- `after_category_insert($category, $values)`
- `before_category_update($category, $values, $modified)`
- `after_category_update($category, $values, $modified)`
- `before_category_save($category, $values)`
- `after_category_save($category, $values)`
- `before_category_delete($category, $values)`
- `after_category_delete($category, $values)`
- `before_category_bulk_delete($delete_ids)`
- `after_category_bulk_delete($delete_ids)`

### `before_category_insert($category, $values)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
Returns | `NULL` | void

Called before the category object is inserted. Changes made to the object will be saved automatically.

How it’s called:

    ee()->extensions->call('before_category_insert', $this, $this->getValues());

### `after_category_insert($category, $values)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
Returns | `NULL` | void

Called after the category object is inserted. Changes made to the object object will not be saved automatically. Saving the object may trigger the save and update hooks.

How it’s called:

    ee()->extensions->call('after_category_insert', $this, $this->getValues());

### `before_category_update($category, $values, $modified)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
$modified | `Array` | An array of all the old values that were changed
Returns | `NULL` | void

Called before the category object is updated. Changes made to the object will be saved automatically.

How it’s called:

    ee()->extensions->call('before_category_update', $this, $this->getValues(), $modified);

### `after_category_update($category, $values, $modified)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
$modified | `Array` | An array of all the old values that were changed
Returns | `NULL` | void

Called after the category object is updated. Changes made to the object will not be saved automatically. Calling save may fire additional hooks.

How it’s called:

    ee()->extensions->call('after_category_update', $this, $this->getValues(), $modified);

### `before_category_save($category, $values)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
Returns | `NULL` | void

Called before the category object is inserted or updated. Changes made to the object will be saved automatically.

How it’s called:

    ee()->extensions->call('before_category_save', $this, $this->getValues());

### `after_category_save($category, $values)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
Returns | `NULL` | void

Called after the category object is inserted or updated. Changes made to the object will not be saved automatically. Calling save may fire additional hooks.

How it’s called:

    ee()->extensions->call('after_category_save', $this, $this->getValues());

### `before_category_delete($category, $values)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
Returns | `NULL` | void

Called before the category object is deleted. If you are conditionally deleting one of your own models, please consider creating an inverse relationship instead. This will provide better performance and strictly enforce data consistency.

How it’s called:

    ee()->extensions->call('before_category_delete', $this, $this->getValues());

### `after_category_delete($category, $values)`

Parameter | Type | Description
--- | --- | ---
$category | `Object` | Current Category model object
$values | `Array` | The Category model object data as an array
Returns | `NULL` | void

Called after the category object is deleted. If you are conditionally deleting one of your own models, please consider creating an inverse relationship instead. This will provide better performance and strictly enforce data consistency.

How it’s called:

    ee()->extensions->call('after_category_delete', $this, $this->getValues());

### `before_category_bulk_delete($delete_ids)`

Parameter | Type | Description
--- | --- | ---
$delete_ids | `Array` | The primary key IDs of the models being deleted
Returns | `NULL` | void

Called before a bulk of category objects are deleted. If you need to do an expensive operation when categories are deleted, it may be more efficient to handle it in bulk here.

How it’s called:

    ee()->extensions->call('before_category_delete', $delete_ids);

New in version 4.3.0.

### `after_category_bulk_delete($delete_ids)`

Parameter | Type | Description
--- | --- | ---
$delete_ids | `Array` | The primary key IDs of the models being deleted
Returns | `NULL` | void

Called after a bulk of category objects are deleted. If you need to do an expensive operation when categories are deleted, it may be more efficient to handle it in bulk here.

How it’s called:

    ee()->extensions->call('after_category_bulk_delete', $delete_ids);

New in version 4.3.0.