The Acquia CMS 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.
Note
This page uses content types as an example, but the same applies for media types and taxonomy vocabularies.
Follow Drupal best practices to add new fields to content types:
Sign in to Acquia CMS.
In the Acquia CMS administrative interface, click Manage > Structure > Content Types > Select Content Type > Manage Fields.
Click Add field.
In Add a new field, select field type from the dropdown menu.
In Label, enter a name.
Click Save and continue.
Select the number of items you want to allow. You can select Limited or Unlimited based on your requirements.
Add help text
Based on your requirements, confirm whether the default value is required.
Click on Save settings.
Verify the changes on your site.
You can capture configurations from the applications administrative user interface.
Your configurations are kept when a new update is released to the Acquia CMS module. Drupal only reads and updates configuration once when the module is first installed.
Acquia does not recommend making changes to the fields that are included with Acquia CMS. Instead, Acquia recommends creating new fields as per your requirement. For information about adding new fields, see Adding a new field.
Follow Drupal best practices for adding new fields to content types:
Sign in to Acquia CMS.
In the Acquia CMS administrative interface, click Manage > Structure > Content Types > Select Content Type > Manage Fields.
In the Operation of the field you wish to remove, click on the drop-down arrow.
Click Delete.
The system redirects you to the confirmation page.
Click Delete.
Verify the changes on your site.
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 the Acquia CMS module. Drupal only reads and updates configuration once when the module is first installed.
Note
If there are updates to the deleted field in subsequent module updates,
hook_update_N()
throws an error that the configuration does not exist.
If Acquia CMS makes an update to a field type on a content type, and you have not made any changes to that field, the Acquia CMS update is applied when you update Acquia CMS.
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 Acquia CMS update only applies if the original field exists with no modifications.