The Drupal Starter Kits content model is intended to be used as provided or as a starting point. You can update the content model to meet the requirements of your information architecture. This page provides information on what happens if you add, update, or remove fields from the content model.
This page uses content types as an example, but the same applies for media types and taxonomy vocabularies.
To add new fields to content types:
Select the number of items you want to allow.
Based on you requirements, select Limited or Unlimited.
Add help text
Based on your requirements, confirm whether the default value is required.
Verify the changes on your site.
These steps adhere to Drupal best practices for adding new fields to content types.
To capture configurations from the applications administrative user interface:
Your configurations are kept when a new update is released to Drupal Starter Kits. Drupal only reads and updates configuration once when the module is first installed.
Acquia does not recommend that you make changes to the fields that are included with Drupal Starter Kits. Instead, Acquia recommends that you create new fields based on your requirements. For information about adding new fields, see Adding a new field.
To remove an existing field:
Click Delete.
The system redirects you to the confirmation page.
Verify the changes on your site.
These steps adhere to Drupal best practices for removing existing fields.
You must capture the configuration once you make changes for future reference. You can use Drush to export configurations such as drush cex. If it exists, delete the configuration file of the deleted field from the config/sync directory.
Your configurations are kept when a new update is released to Drupal Starter Kits. Drupal only reads and updates configuration once when the module is first installed.
If any changes occur in the deleted field in subsequent module updates, hook_update_N() returns an error that the configuration does not exist.
If Drupal Starter Kits update a field type on a content type and you have not made any changes to that field, the update from Drupal Starter Kits is applied when you update Drupal Starter Kits.
For example, there is a provided content type and it has an autocomplete text box field. A future update changes that field to a checkbox. The following are applied:
The Drupal Starter Kits update only applies if the original field exists with no modifications.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
The Drupal Starter Kits content model is intended to be used as provided or as a starting point. You can update the content model to meet the requirements of your information architecture. This page provides information on what happens if you add, update, or remove fields from the content model.
This page uses content types as an example, but the same applies for media types and taxonomy vocabularies.
To add new fields to content types:
Select the number of items you want to allow.
Based on you requirements, select Limited or Unlimited.
Add help text
Based on your requirements, confirm whether the default value is required.
Verify the changes on your site.
These steps adhere to Drupal best practices for adding new fields to content types.
To capture configurations from the applications administrative user interface:
Your configurations are kept when a new update is released to Drupal Starter Kits. Drupal only reads and updates configuration once when the module is first installed.
Acquia does not recommend that you make changes to the fields that are included with Drupal Starter Kits. Instead, Acquia recommends that you create new fields based on your requirements. For information about adding new fields, see Adding a new field.
To remove an existing field:
Click Delete.
The system redirects you to the confirmation page.
Verify the changes on your site.
These steps adhere to Drupal best practices for removing existing fields.
You must capture the configuration once you make changes for future reference. You can use Drush to export configurations such as drush cex. If it exists, delete the configuration file of the deleted field from the config/sync directory.
Your configurations are kept when a new update is released to Drupal Starter Kits. Drupal only reads and updates configuration once when the module is first installed.
If any changes occur in the deleted field in subsequent module updates, hook_update_N() returns an error that the configuration does not exist.
If Drupal Starter Kits update a field type on a content type and you have not made any changes to that field, the update from Drupal Starter Kits is applied when you update Drupal Starter Kits.
For example, there is a provided content type and it has an autocomplete text box field. A future update changes that field to a checkbox. The following are applied:
The Drupal Starter Kits update only applies if the original field exists with no modifications.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Drupal Starter Kits