Skip to main content
edited body
Source Link
4uk4
  • 101.7k
  • 7
  • 173
  • 217

Field storage is not bundle specific. The easiest way is to install the field storage via a config yml file in the module config install folder and then add a bundle field to each existing or later added bundle, like core is doing it for the body field. See Add content type field programmatically

Or remove any existing bundle field with that field name and add a non-bundle specific-specific base field for each entity type in the hook_entity_base_field_info() you are already using.

I would recommendedrecommend the first way via config, this is in general a more reliable way to install and uninstall fields to existing entities.

Field storage is not bundle specific. The easiest way is to install the field storage via a config yml file in the module config install folder and then add a bundle field to each existing or later added bundle, like core is doing it for the body field. See Add content type field programmatically

Or remove any existing bundle field with that field name and add a non-bundle specific base field for each entity type in the hook_entity_base_field_info you are already using.

I would recommended the first way via config, this is in general a more reliable way to install and uninstall fields to existing entities.

Field storage is not bundle specific. The easiest way is to install the field storage via a config yml file in the module config install folder and then add a bundle field to each existing or later added bundle, like core is doing it for the body field. See Add content type field programmatically

Or remove any existing bundle field with that field name and add a non-bundle-specific base field for each entity type in the hook_entity_base_field_info() you are already using.

I would recommend the first way via config, this is in general a more reliable way to install and uninstall fields to existing entities.

Source Link
4uk4
  • 101.7k
  • 7
  • 173
  • 217

Field storage is not bundle specific. The easiest way is to install the field storage via a config yml file in the module config install folder and then add a bundle field to each existing or later added bundle, like core is doing it for the body field. See Add content type field programmatically

Or remove any existing bundle field with that field name and add a non-bundle specific base field for each entity type in the hook_entity_base_field_info you are already using.

I would recommended the first way via config, this is in general a more reliable way to install and uninstall fields to existing entities.