CategoryGroup Model Extension Hooks
before_category_group_insert($category_group, $values)after_category_group_insert($category_group, $values)before_category_group_update($category_group, $values, $modified)after_category_group_update($category_group, $values, $modified)before_category_group_save($category_group, $values)after_category_group_save($category_group, $values)before_category_group_delete($category_group, $values)after_category_group_delete($category_group, $values)before_category_group_bulk_delete($delete_ids)after_category_group_bulk_delete($delete_ids)
before_category_group_insert($category_group, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup model object data as an array |
| Returns | NULL |
void |
Called before the category group object is inserted. Changes made to the object will be saved automatically.
How it’s called:
ee()->extensions->call('before_category_group_insert', $this, $this->getValues());
after_category_group_insert($category_group, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup model object data as an array |
| Returns | NULL |
void |
Called after the category group 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_group_insert', $this, $this->getValues());
before_category_group_update($category_group, $values, $modified)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup 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 group object is updated. Changes made to the object will be saved automatically.
How it’s called:
ee()->extensions->call('before_category_group_update', $this, $this->getValues(), $modified);
after_category_group_update($category_group, $values, $modified)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup 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 group 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_group_update', $this, $this->getValues(), $modified);
before_category_group_save($category_group, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup model object data as an array |
| Returns | NULL |
void |
Called before the category group object is inserted or updated. Changes made to the object will be saved automatically.
How it’s called:
ee()->extensions->call('before_category_group_save', $this, $this->getValues());
after_category_group_save($category_group, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup model object data as an array |
| Returns | NULL |
void |
Called after the category group 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_group_save', $this, $this->getValues());
before_category_group_delete($category_group, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup model object data as an array |
| Returns | NULL |
void |
Called before the category group 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_group_delete', $this, $this->getValues());
after_category_group_delete($category_group, $values)
| Parameter | Type | Description |
|---|---|---|
| $category_group | Object |
Current CategoryGroup model object |
| $values | Array |
The CategoryGroup model object data as an array |
| Returns | NULL |
void |
Called after the category group 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_group_delete', $this, $this->getValues());
before_category_group_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 group objects are deleted. If you need to do an expensive operation when category groups are deleted, it may be more efficient to handle it in bulk here.
How it’s called:
ee()->extensions->call('before_category_group_bulk_delete', $delete_ids);
New in version 4.3.0
after_category_group_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 group objects are deleted. If you need to do an expensive operation when category groups are deleted, it may be more efficient to handle it in bulk here.
How it’s called:
ee()->extensions->call('after_category_group_bulk_delete', $delete_ids);
New in version 4.3.0