public function View::preSave in Drupal 8

Same name and namespace in other branches

9 core/modules/views/src/Entity/View.php \Drupal\views\Entity\View::preSave()
10 core/modules/views/src/Entity/View.php \Drupal\views\Entity\View::preSave()

Acts on an entity before the presave hook is invoked.

Used before the entity is saved and before invoking the presave 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. This is different from its counterpart in the Field API, FieldItemListInterface::preSave(), which is fired on all field translations automatically. @todo Adjust existing implementations and the documentation according to https://www.drupal.org/node/2577609 to have a consistent API.

Parameters

\Drupal\Core\Entity\EntityStorageInterface $storage: The entity storage object.

Throws

\Exception When there is a problem that should prevent saving the entity.

Overrides ConfigEntityBase::preSave

File

core/modules/views/src/Entity/View.php, line 293

Class

View: Defines a View configuration entity class.

Namespace

Drupal\views\Entity

Code

public function preSave(EntityStorageInterface $storage) {
  parent::preSave($storage);
  $displays = $this
    ->get('display');

  // @todo Remove this line and support for pre-8.3 table names in Drupal 9.
  // @see https://www.drupal.org/project/drupal/issues/3069405 .
  $this
    ->fixTableNames($displays);

  // Sort the displays.
  ksort($displays);
  $this
    ->set('display', [
    'default' => $displays['default'],
  ] + $displays);

  // Calculating the cacheability metadata is only needed when the view is
  // saved through the UI or API. It should not be done when we are syncing
  // configuration or installing modules.
  if (!$this
    ->isSyncing() && !$this
    ->hasTrustedData()) {
    $this
      ->addCacheMetadata();
  }
}

You are here