I think it would be majorly helpful to update the UI documentation / help text when using the wizard to say, setup a D6 > D7 migration in these two respects:

Scenario 1:
I need to add new node types to my wizard-based D6 migration group, but I can't once I've already run the d2d migration wizard setup!

The UI and documentation gives us no info on how to deal with this common situation. It turns out you can re-run the wizard with the same database information and effectively "update" your mappings with new node/term/etc components, but you have to be extremely cautious as to what you click on or else rather than adding the new entity mappings, you wipe out all your previously, carefully mapped settings/values.

Trial and error has shown me that if you have a set of mappings in a wizard group that have been customized and then need to add mappings for new content types -- added after the initial wizard has run -- you must NOT select any content types / terms / etc besides the newly added ones on the wizard step that asks what to import -- the newly added content types will automatically be selected. Simply hit the NEXT button at that point and you safely merge in your new mappings. So yeah, lots of hair pulling on that.

Scenario 2:
I'm working on a new/different computer with my D7 site and when I try to import or edit my wizard-based migration group, it gives me the following error:

SQLSTATE[HY000] [1130] Host 'xxxxxx' is not allowed to connect to this MySQL server

The first thing I and my co-worker tried to do this in this scenario was try and review/edit our migration database connection settings, but the migrate module obfuscates this information (hashes it, I believe), so it's impossible to view and edit, even directly in the database.

It turns out this is a simple fix and is related to the source MySQL user permissions. By entering PHPmyAdmin on the source server, you can add additional allowed host names to a database user. In my case I needed to add my new static IP address of the new computer for the user I remember entering in my Migration group wizard steps (root) and after restarting the MySQL service, everything worked.

It would be wonderful if notes on this could somehow be incorporated in the Wizard (UI) documentation as help text or better watchdog errors. Either way, I hope this post provides people Googling with help for these scenarios.

Comments

amaisano created an issue. See original summary.

amaisano’s picture

Issue summary: View changes