d6_vocabulary_entity_form_display.yml in Drupal 10
Same filename and directory in other branches
core/modules/taxonomy/migrations/d6_vocabulary_entity_form_display.yml
File
core/modules/taxonomy/migrations/d6_vocabulary_entity_form_display.ymlView source
- id: d6_vocabulary_entity_form_display
- label: Vocabulary form display configuration
- migration_tags:
- - Drupal 6
- - Configuration
- source:
- plugin: d6_taxonomy_vocabulary_per_type
- constants:
- entity_type: node
- form_mode: default
- options:
- weight: 20
- field_prefix: field_
- process:
- entity_type: 'constants/entity_type'
- form_mode: 'constants/form_mode'
- options/type:
- plugin: static_map
- source: tags
- map:
- 0: options_select
- 1: entity_reference_autocomplete_tags
- options/weight: 'constants/options/weight'
- bundle:
- -
- plugin: migration_lookup
- migration: d6_node_type
- source: type
- -
- plugin: skip_on_empty
- method: row
- # This value is only used in the 'field_name' process pipeline below.
- raw_field_name:
- -
- plugin: migration_lookup
- migration: d6_taxonomy_vocabulary
- source: vid
- -
- plugin: skip_on_empty
- method: row
- field_name:
- # Prepend field_ to avoid conflicts with base fields, and make sure the
- # result is no longer than 32 characters.
- -
- plugin: concat
- source:
- - constants/field_prefix
- - '@raw_field_name'
- -
- plugin: substr
- length: 32
- -
- # This plugin checks if the vocabulary being migrated is the one used by
- # Forum. If so, we use the machine name that Forum expects. Otherwise, we
- # leave it unchanged.
- plugin: forum_vocabulary
- machine_name: taxonomy_forums
- destination:
- plugin: component_entity_form_display
- migration_dependencies:
- required:
- - d6_vocabulary_field_instance