By the final release of Migrate 2.6, we need to update the online documentation with all the new features and other changes. Good time to do an overall review and make sure any obsolete/deprecated stuff is removed too.

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

See also #1984534: Update examples for Migrate 2.6.

wusel’s picture

wusel commented

I have build a test-dev (XAMPP 1.7.7 Win7) like http://drupal.org/node/1285276 (Import new users and their Profile2 fields from one CSV file), but with the newest dev-versions of date, migrate and migrate_extras:
D7.22
date 7.x-2.6+2-dev (2012-Sep-30) with patch #1832544-2: Class registration for Migrate 2.5 or later
Migrate 7.x-2.5+109-dev (2013-May-02)
migrate_extras 7.x-2.5+2-dev (2012-Nov-29)
Drush 5.8 Windows Installer / for an update look at #1980282: Release Drush 5.9 (or 6.0) Windows Installer on drush.ws

Like http://drupal.org/node/1958170 :
I have set 'migrate_drush_path' under Apache Environment to 'C:\ProgramData\Drush' and the 'PATH' value under Apache Environment includes the directory containing PHP ('C:\xampp\php').

When I go to 'http://example.com/admin/content/import/configure', I can read:

Background operations
To enable running operations in the background with drush, (which is recommended), some configuration must be done on the server. See the documentation on drupal.org.

Something is wrong in my test-dev. Please give me a hint.

Thank you very much.

Wusel

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

@wusel: Your question deserves its own issue, it's not really relevant to the general documentation rewrite for Migrate 2.6. But briefly, I imagine there's probably something that needs to be done differently to support a Windows server environment, but I don't have one to test on. I would suggest doing some debugging in migrate_ui_configure_form() where it tries to run a "drush status" command to see why that might be failing. You might try using forward slashes in migrate_drush_path, or doubling the backslashes, in case there's an escaping issue. Please open a separate issue to report back.

wusel’s picture

wusel commented

@mikeryan: Thanks for your great hint.
I have found that my migrate_drush_path was incomplete, so I have added a hint on your doc-page.
Now I get:

Background operations
Configure the use of drush version 5.8 to run import and rollback operations in the background.

The next time I will make an own issue. Sorry for this mistake.

Wusel

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

An update - I am starting work on updating the documentation to reflect Migrate 2.6. As a first pass, I will update each existing page to reflect any relevant changes. Then, I will add pages where necessary to reflect new functionality. Finally, I plan on doing some reorganization (just moving some pages around for the most part). This is something of a background project over the next few weeks.

geerlingguy’s picture

geerlingguy commented

mikeryan - really appreciate your hard work on this! Unlike many other modules, where on-site documentation languishes and the only help you can find is via google search, Migrate's canonical source of documentation (besides beer and wine example modules) is the Migrate pages on Drupal.org, and I'm amazed how well you keep them up to date already. Just wanted to show a little appreciation for the effort. Looks like 2.6 will be a pretty nice update.

wusel’s picture

wusel commented

@mikeryan:
Thanks in advance, really great!

I will also update the page 'Import new users and their Profile2 fields from one CSV file' (http://drupal.org/node/1285276).
Or should I leave the old version for comparison purposes (a certain time) exist?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

Go right ahead - I'm being aggressive about focusing the docs on 2.6, no reason you shouldn't too;).

wusel’s picture

wusel commented

@mikeryan:
I have updated the page 'Import new users and their Profile2 fields from one CSV file' (http://drupal.org/node/1285276), based on Migrate version "7.x-2.6-beta1+9-dev".

In due time I will also try to use the new way of the UI (step-by-step wizards).

Wusel

wusel’s picture

wusel commented

This former comment was wrong, sorry. But I cannot delete it.

Wusel

Anonymous’s picture

Anonymous (not verified) commented

I'm available to contribute some documentation. I finally wrapped my head around the new registration process after reading through the old docs and finding this gem:

https://drupal.org/node/1778952#comment-6578360

Registrations had always confused me a bit, they seemed to always take a bit of fiddling to get it to work... but after reading that note it all finally clicked for me. It has also made it (more) obvious to me that some contrib modules work with 2.4 + 2.5, while others are going to be 2.5 + 2.6. In particular I'm looking at commerce_migrate_ubercart, because it uses the auto-registration method from 2.4 that no longer works in 2.6.

I'm thinking of adding a page to either the migrate or mirgrate_d2d docs to show how to upgrade old migration modules but if there are specific pages that need urgent updates I could focus on that. Right now I'm doing lots of migrations so I can even just make small updates as I work through specific issues.

Thanks for all the amazing work on these modules. I really cut my teeth on Migrate (mostly because my OOP was a bit rusty) but I enjoy working with it so much now that I get it!

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Issue summary: View changes

per https://drupal.org/comment/8607483#comment-8607483, document queueMessage().

shaundychko’s picture

shaundychko
Location Vancouver, Canada
commented

Added:

To record an error message for the current row

If you wish to record an error, use $this->queueMessage('your message text') and it will appear among the messages for this migration, automatically including the source ID.
Note: don't use $this->setMessage('message text') in prepareRow().
to prepareRow() section of https://www.drupal.org/node/1132582