FieldStorageConfig::$persist_with_no_fields
Same name in other branches
- 8.9.x core/modules/field/src/Entity/FieldStorageConfig.php \Drupal\field\Entity\FieldStorageConfig::persist_with_no_fields
- 10 core/modules/field/src/Entity/FieldStorageConfig.php \Drupal\field\Entity\FieldStorageConfig::persist_with_no_fields
- 11.x core/modules/field/src/Entity/FieldStorageConfig.php \Drupal\field\Entity\FieldStorageConfig::persist_with_no_fields
Flag indicating whether the field storage should be deleted when orphaned.
By default field storages for configurable fields are removed when there are no remaining fields using them. If multiple modules provide bundles which need to use the same field storage then setting this to TRUE will preserve the field storage regardless of what happens to the bundles. The classic use case for this is node body field storage since Book, Forum, the Standard profile and bundle (node type) creation through the UI all use same field storage.
Type: bool
File
-
core/
modules/ field/ src/ Entity/ FieldStorageConfig.php, line 165
Class
- FieldStorageConfig
- Defines the Field storage configuration entity.
Namespace
Drupal\field\EntityCode
protected $persist_with_no_fields = FALSE;
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.