ExpressionEngine® 3 User Guide

Legacy Documentation

You are using the documentation for version 3.5.17. Go here for the latest version or check here for your available upgrades to the latest version.

Template Model Extension Hooks

before_template_insert

before_template_insert($template, $values)

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

How it’s called:

ee()->extensions->call('before_template_insert', $this, $this->getValues());
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
Returns:

void

Return type:

NULL

New in version 3.3.0.

after_template_insert

after_template_insert($template, $values)

Called after the template 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_template_insert', $this, $this->getValues());
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
Returns:

void

Return type:

NULL

New in version 3.3.0.

before_template_update

before_template_update($template, $values, $modified)

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

How it’s called:

ee()->extensions->call('before_template_update', $this, $this->getValues(), $modified);
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
  • $modified (array) – An array of all the old values that were changed
Returns:

void

Return type:

NULL

New in version 3.3.0.

after_template_update

after_template_update($template, $values, $modified)

Called after the template 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_template_update', $this, $this->getValues(), $modified);
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
  • $modified (array) – An array of all the old values that were changed
Returns:

void

Return type:

NULL

New in version 3.3.0.

before_template_save

before_template_save($template, $values)

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

How it’s called:

ee()->extensions->call('before_template_save', $this, $this->getValues());
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
Returns:

void

Return type:

NULL

New in version 3.3.0.

after_template_save

after_template_save($template, $values)

Called after the template 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_template_save', $this, $this->getValues());
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
Returns:

void

Return type:

NULL

New in version 3.3.0.

before_template_delete

before_template_delete($template, $values)

Called before the template 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_template_delete', $this, $this->getValues());
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
Returns:

void

Return type:

NULL

New in version 3.3.0.

after_template_delete

after_template_delete($template, $values)

Called after the template 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_template_delete', $this, $this->getValues());
Parameters:
  • $template (object) – Current Template model object
  • $values (array) – The Template model object data as an array
Returns:

void

Return type:

NULL

New in version 3.3.0.