Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.It's broken - fix it.
Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.It's broken - fix it.
Top Drupal contributor Acquia would like to thank their partners for their contributions to Drupal.
Drupal is a registered trademark of Dries Buytaert.
Comments
Comment #3
mikeryanDone. Bonus - since we now control the migration configuration entity, we can make the group a proper property rather than resorting to third_party_settings.
Comment #4
agoradesign CreditAttribution: agoradesign commentedI've followed your changes in the example for my custom migrations. But when I call
drush migrate-status, everything gets listed under "default" group. Can you confirm that this works for you?Comment #5
mikeryanYes, it works for me with migrate_example. Note per my comment above that the migration_group property has been moved out of third_party_settings, you should be setting that as a top-level property in your migration .yml files.
Comment #6
agoradesign CreditAttribution: agoradesign commentedYeah, I know.. I've moved them, and I compared my migration files with the beer example.... strange. I will look at this again
Comment #7
agoradesign CreditAttribution: agoradesign commentedNow it's clear... you were working with a patched migrate_tools already, After you committed http://cgit.drupalcode.org/migrate_tools/commit/?id=1893c98 and update to the latest dev, the groups are working as expected for me too
Comment #8
mikeryanYep, I had neglected to commit and push that change, finally did so...