public function FieldConfigBase::postSave in Drupal 10
Same name and namespace in other branches
- 8 core/lib/Drupal/Core/Field/FieldConfigBase.php \Drupal\Core\Field\FieldConfigBase::postSave()
- 9 core/lib/Drupal/Core/Field/FieldConfigBase.php \Drupal\Core\Field\FieldConfigBase::postSave()
Acts on a saved entity before the insert or update hook is invoked.
Used after the entity is saved, but before invoking the insert or update hook. Note that in case of translatable content entities this callback is only fired on their current translation. It is up to the developer to iterate over all translations if needed.
Parameters
\Drupal\Core\Entity\EntityStorageInterface $storage: The entity storage object.
bool $update: TRUE if the entity has been updated, or FALSE if it has been inserted.
Overrides EntityBase::postSave
File
- core/
lib/ Drupal/ Core/ Field/ FieldConfigBase.php, line 285
Class
- FieldConfigBase
- Base class for configurable field definitions.
Namespace
Drupal\Core\FieldCode
public function postSave(EntityStorageInterface $storage, $update = TRUE) {
// Clear the cache.
\Drupal::service('entity_field.manager')
->clearCachedFieldDefinitions();
// Invalidate the render cache for all affected entities.
$entity_type = $this
->getFieldStorageDefinition()
->getTargetEntityTypeId();
if ($this
->entityTypeManager()
->hasHandler($entity_type, 'view_builder')) {
$this
->entityTypeManager()
->getViewBuilder($entity_type)
->resetCache();
}
}