Allow specifying dependencies in arguments [#2125123]

Hello everyone,

I'm running into this problem with my module, migrate_webform, where the sort order of the migrations does not register correctly. I'm looking for someone to take a look at the registrations in the module and/or provide some insight.

The user has the ability to configure a user migration. If it is specified, the Node migration (which is the first to run) moves to the bottom of the listing of webform migrations. If they do not configure a migration, Node often shows up as the THIRD item in the list, but on some sites it registers as the first item as it should. Without a user migration, Node has no dependencies. All the others do have dependencies.

I double checked the dependencies so they have a strict ordering... each depends only on the one before it. I've tried fresh snapshots of the site to see if that would clear out the settings and register it correctly but that doesn't work either.

My latest commit for the module is here: http://drupalcode.org/project/migrate_webform.git/tree/019ae80

Comments

Comment #1

Anonymous (not verified) CreditAttribution: Anonymous commented 19 November 2013 at 22:50

I have another migration that was showing this problem. I noticed when I changed the problematic migration to extend the DrupalMigration like the rest of my items suddenly things went into the right order.

I suspect that on some level the inheritance must be the same or it will not sort?

Comment #2

mikeryan

he/him

English

Murphysboro, IL, USA

CreditAttribution: mikeryan commented 4 April 2014 at 19:47

Title:	Migrations listed in wrong order	» Allow specifying dependencies in arguments
Category:	Bug report	» Feature request
Status:	Active	» Postponed

Had a WTF reply going, but looking at your hook_migrate_api() and thinking about the implications of #1 made the light dawn. You're setting the dependencies in the arguments in hook_migrate_api(), not in the code - this is a feature of the migrate_d2d module, implemented in the DrupalMigration class. Yeah, it probably would be nice to have the basic Migrate module support dependencies in arguments, so making this a feature request (won't add it for 2.6, though).