Score:0

Why does Drush:migrate not generate config entities for separate content types?

in flag

When using Drupal 9 with modules migrate, migrate_drupal, migrate_upgrade and migrate_plus, and calling drush:migrate --configure-only with a Drupal 7 source database

  • I see migrations at drush migrate-status, also one for each content type, like d7_node_complete:page
  • I see a lot of yamls appear after drush config:export, but none for content types
  • I see configs appear in the ui at admin/config/development/configuration/single/export, but none for content types

I specifically want to migrate certain content types, so I was expecting to get their yamls (like in the example here https://www.drupal.org/docs/drupal-apis/migrate-api/migrate-api-overview#s-highwater-marks ) and modify them.

Am I doing something wrong, or was I expecting something wrong ?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.