CategoryField Model Extension Hooks
before_category_field_insert($category_field, $values)after_category_field_insert($category_field, $values)before_category_field_update($category_field, $values, $modified)after_category_field_update($category_field, $values, $modified)before_category_field_save($category_field, $values)after_category_field_save($category_field, $values)before_category_field_delete($category_field, $values)after_category_field_delete($category_field, $values)before_category_field_bulk_delete($delete_ids)after_category_field_bulk_delete($delete_ids)
before_category_field_insert($category_field, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField model object data as an array |
| Returns | NULL |
void |
Called before the category field object is inserted. Changes made to the object will be saved automatically.
How it’s called:
ee()->extensions->call('before_category_field_insert', $this, $this->getValues());
after_category_field_insert($category_field, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField model object data as an array |
| Returns | NULL |
void |
Called after the category field 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_field_insert', $this, $this->getValues());
before_category_field_update($category_field, $values, $modified)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField 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 field object is updated. Changes made to the object will be saved automatically.
How it’s called:
ee()->extensions->call('before_category_field_update', $this, $this->getValues(), $modified);
after_category_field_update($category_field, $values, $modified)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField 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 field 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_field_update', $this, $this->getValues(), $modified);
before_category_field_save($category_field, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField model object data as an array |
| Returns | NULL |
void |
Called before the category field object is inserted or updated. Changes made to the object will be saved automatically.
How it’s called:
ee()->extensions->call('before_category_field_save', $this, $this->getValues());
after_category_field_save($category_field, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField model object data as an array |
| Returns | NULL |
void |
Called after the category field 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_field_save', $this, $this->getValues());
before_category_field_delete($category_field, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField model object data as an array |
| Returns | NULL |
void |
Called before the category field 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_field_delete', $this, $this->getValues());
after_category_field_delete($category_field, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_field | Object |
Current CategoryField model object |
| $values | Array |
The CategoryField model object data as an array |
| Returns | NULL |
void |
Called after the category field 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_field_delete', $this, $this->getValues());
before_category_field_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 field objects are deleted. If you need to do an expensive operation when category fields are deleted, it may be more efficient to handle it in bulk here.
How it’s called:
ee()->extensions->call('before_category_field_bulk_delete', $delete_ids);
after_category_field_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 field objects are deleted. If you need to do an expensive operation when category fields are deleted, it may be more efficient to handle it in bulk here.
How it’s called:
ee()->extensions->call('after_category_field_bulk_delete', $delete_ids);