Need Migrate module for Phone module support [#1883754]

The Phone module is an add-on for CCK that provides a CCK field formatted for phone numbers. The automated upgrade fails unless you also install the Migrate module; see #1867340: When migrating from Drupal 6 to Drupal 7 using CCK module, but without migrate, fatal error happens. It seems to me that could be added to the drush_sup workflow pretty easily. If I have time I'll submit a patch, but thought someone with more experience might like to beat me to it. :-)

Comments

Comment #1

greg.1.anderson CreditAttribution: greg.1.anderson commented 9 January 2013 at 00:29

Do you only need to install and enable the migrate module in order for the updatedb to work, or do you need to run the migrate module in order to do the data conversion that the phone module needs?

If the later, then this issue is blocked on #1724532: Integrate Drupal-to-Drupal data migration with drush site-upgrade.

In either event, it is an interesting question how drush_sup will know that the phone module needs the migrate module. If migrate were a dependency of phone, then drush_sup would find migrate, download it and enable it (n.b. this feature only works when the module name == its project name due to a limitation in drush_sup). However, the phone module probably does not want to declare migrate as a dependency, since it is only needed for the upgrade path, and not for general usage.

Comment #2

koppie CreditAttribution: koppie commented 9 January 2013 at 01:47

At second glance, it looks like the Migrate module is needed to migrate all content from a D6 site to a D7 site, at least if CCK is present. I ran drush_sup and it seemed to complete the entire process, but none of my content made it over. Now I'm re-running it with the Migrate module installed, and it's actually processing my nodes.

I wonder if this should be in the documentation? Or hard-coded into drush_sup? Did the designers really contemplate a use case where Migrate wouldn't be necessary? Maybe it should be an option for the user? Seems like relatively little overhead considering how much work drush_sup does anyway.

Should this ticket be changed to documentation or feature request? Or is there something I'm missing here? (That's quite possible.)

Comment #3

greg.1.anderson CreditAttribution: greg.1.anderson commented 9 January 2013 at 02:09

I guess that phone calls migrate from its update hooks? If so, there's no dependence on #1724532.

I'd be happy to make drush_sup automatically download and enable the migrate module, but ideally it should only do it if it needs to. It doesn't seem like there's a good way to tell if it needs it. I suppose I could add another step that asks the user if they want the migrate module; they'd get it if they ran with --auto, but it's easy enough to uninstall when you're all done, and it beats the alternative of not noticing that one of your modules has an upgrade path.