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.
IS could use a description of the problem - on a cursory reading, the issue is that migrate_drupal_migration_plugins_alter() is being used as a hacky deriver-substitute for d6_term_node migrations, because "the 'd6_taxonomy_vocabulary' definition is not available to the deriver as it is running inside getDefinitions()."?
Comments
Comment #3
mikeryanIS could use a description of the problem - on a cursory reading, the issue is that migrate_drupal_migration_plugins_alter() is being used as a hacky deriver-substitute for d6_term_node migrations, because "the 'd6_taxonomy_vocabulary' definition is not available to the deriver as it is running inside getDefinitions()."?
Comment #4
benjy CreditAttribution: benjy at PreviousNext commentedYeah, I think that sums this up pretty well. Low priority this though.
Comment #6
mikeryan#2597650: Term references should be incorporated into D6 node migration is my proposed solution to this problem (also solving #2754787: d6_term_node migration overwrites node changed timestamps).