Purpose

This article explains how to make field value input selectable, as shown below.

Below, I’ll explain both the text case and the entity reference case.

Text Case

Create a field called age. Here, select “List (text)”.

Enter the choices as follows.

As a result, the field can be edited in a “Select list” format as shown below.

Furthermore, from the content type list page, click “Manage form display”.

/admin/structure/types

Then change the widget for the age field to “Checkboxes/radio buttons”.

As a result, the form changes as follows.

Entity Reference

The entity reference case is similar to the above. For example, let’s target the field created in the following article.

From “Manage form display”, change the widget to “Checkboxes/radio buttons”. Then the form changes as follows.

Summary

I hope this serves as a helpful reference for managing form display.

Reference

I asked about whether to use the text list format or Vocabulary (taxonomy) when managing values in Drupal. I hope this is also helpful.

Answer by GPT-4

Whether to use the text list format or Vocabulary (taxonomy) when managing values in Drupal depends on the actual usage scenario and requirements. Below are the characteristics, advantages, and limitations of each option.

Text List Format

Advantages:

  1. Simple and easy to set up.
  2. Suitable for small, fixed lists.
  3. Can be easily displayed as select lists, checkboxes, etc.

Limitations:

  1. Cannot establish relationships or hierarchical structures between items.
  2. Management can become difficult as the list grows.

Vocabulary (Taxonomy)

Advantages:

  1. Can establish relationships and hierarchical structures between items.
  2. Can add metadata, descriptions, related images, etc. to items.
  3. Suitable for managing large quantities of items or dynamically changing items.
  4. Rich integration with extension features and modules.

Limitations:

  1. Setup and management may be more complex than the text list format.

Which Should You Choose?

  1. List size and variability: For small, rarely changing lists, the text list format is suitable. For large or frequently changing lists, Vocabulary is more suitable.

  2. Need for related data: When additional information or attributes are needed for items, using Vocabulary is recommended.

  3. Hierarchy and relationships: When hierarchy or relationships between items are needed, like categories, Vocabulary is suitable.

  4. Simplicity: If you want to set up easily and keep things simple, the text list format is a good choice.

Ultimately, it is important to make the optimal choice considering the project requirements and future extensibility.