public function Block::postSave in Drupal 10

Same name and namespace in other branches

1. 8 core/modules/block/src/Entity/Block.php \Drupal\block\Entity\Block::postSave()
2. 9 core/modules/block/src/Entity/Block.php \Drupal\block\Entity\Block::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/modules/block/src/Entity/Block.php, line 245

Class

Block

Defines a Block configuration entity class.

Namespace

Drupal\block\Entity

Code

public function postSave(EntityStorageInterface $storage, $update = TRUE) {
  parent::postSave($storage, $update);

  // Entity::postSave() calls Entity::invalidateTagsOnSave(), which only
  // handles the regular cases. The Block entity has one special case: a
  // newly created block may *also* appear on any page in the current theme,
  // so we must invalidate the associated block's cache tag (which includes
  // the theme cache tag).
  if (!$update) {
    Cache::invalidateTags($this
      ->getCacheTagsToInvalidate());
  }
}