protected ContentEntityNullStorage::doDelete($entities) Performs storage-specific entity deletion. Parameters \Drupal\Core\Entity\EntityInterface[] $entities: An array of entity objects to delete. Overrides ContentEntityStorageBase::doDelete File core/lib/Drupal/Core/Entity/ContentEntityNullStorage.php, line 63 Class ContentEntityNullStorage Defines a null entity storage. Namespace Drupal\Core\Entity Code protected function doDelete($entities) { }

public ContentEntityNullStorage::deleteRevision($revision_id) Delete a specific entity revision. A revision can only be deleted if it's not the currently active one. Parameters int $revision_id: The revision id. Overrides ContentEntityStorageBase::deleteRevision File core/lib/Drupal/Core/Entity/ContentEntityNullStorage.php, line 44 Class ContentEntityNullStorage Defines a null entity storage. Namespace Drupal\Core\Entity Code public function deleteRevision($revision_id) { }

public ContentEntityNullStorage::delete(array $entities) Deletes permanently saved entities. Parameters array $entities: An array of entity objects to delete. Throws \Drupal\Core\Entity\EntityStorageException In case of failures, an exception is thrown. Overrides EntityStorageBase::delete File core/lib/Drupal/Core/Entity/ContentEntityNullStorage.php, line 57 Class ContentEntityNullStorage Defines a null entity storage. Namespace Drupal\Core\Entity Code public function delete(array $e

public ContentEntityNullStorage::countFieldData($storage_definition, $as_bool = FALSE) Determines the number of entities with values for a given field. Parameters \Drupal\Core\Field\FieldStorageDefinitionInterface $storage_definition: The field for which to count data records. bool $as_bool: (Optional) Optimises the query for checking whether there are any records or not. Defaults to FALSE. Return value bool|int The number of entities. If $as_bool parameter is TRUE then the value will either

Defines a null entity storage. Used for content entity types that have no storage. Hierarchy class \Drupal\Core\Entity\EntityHandlerBase uses DependencySerializationTrait, StringTranslationTraitclass \Drupal\Core\Entity\EntityStorageBase implements EntityHandlerInterface, EntityStorageInterfaceclass \Drupal\Core\Entity\ContentEntityStorageBase implements ContentEntityStorageInterface, DynamicallyFieldableEntityStorageInterfaceclass \Drupal\Core\Entity\ContentEntityNullStorage File core/li

public ContentEntityInterface::setRevisionTranslationAffected($affected) Marks the current revision translation as affected. Parameters bool|null $affected: The flag value. A NULL value can be specified to reset the current value and make sure a new value will be computed by the system. Return value $this File core/lib/Drupal/Core/Entity/ContentEntityInterface.php, line 45 Class ContentEntityInterface Defines a common interface for all content entity objects. Namespace Drupal\Core\Ent

public ContentEntityInterface::isRevisionTranslationAffected() Checks whether the current translation is affected by the current revision. Return value bool TRUE if the entity object is affected by the current revision, FALSE otherwise. File core/lib/Drupal/Core/Entity/ContentEntityInterface.php, line 54 Class ContentEntityInterface Defines a common interface for all content entity objects. Namespace Drupal\Core\Entity Code public function isRevisionTranslationAffected();

public ContentEntityInterface::hasTranslationChanges() Determines if the current translation of the entity has unsaved changes. If the entity is translatable only translatable fields will be checked for changes. Return value bool TRUE if the current translation of the entity has changes. File core/lib/Drupal/Core/Entity/ContentEntityInterface.php, line 34 Class ContentEntityInterface Defines a common interface for all content entity objects. Namespace Drupal\Core\Entity Code public fu

Defines a common interface for all content entity objects. Content entities use fields for all their entity properties and are translatable and revisionable, while translations and revisions can be enabled per entity type. It's best practice to always implement ContentEntityInterface for content-like entities that should be stored in some database, and enable/disable revisions and translations as desired. When implementing this interface which extends Traversable, make sure to list IteratorAggr

public ContentEntityFormInterface::validateForm(array &$form, FormStateInterface $form_state) Note that extending classes should not override this method to add entity validation logic, but define further validation constraints using the entity validation API and/or provide a new validation constraint if necessary. This is the only way to ensure that the validation logic is correctly applied independently of form submissions; e.g., for REST requests. For more information about entity valid