The migrate module provides a flexible framework for migrating content into
Drupal from other sources (e.g., when converting a web site from another CMS
to Drupal). Out-of-the-box, support for creating core Drupal objects such as
nodes, users, files, terms, and comments are included - it can easily be
extended for migrating other kinds of content. Content is imported and rolled
back using a bundled web interface (Migrate UI module) or included Drush
commands (strongly recommended ).
This package provides the following Drupal modules:
**Features and enhancements**
* Issue #2379289: migrate-import --update does not seem to work as expected, if map is not joinable, due to highwater field?
* Issue #2403643: Migration::applyMappings() unable to handle multifield subfields
* Issue #2472045: Add language subfields only if field is translatable
* Issue #2474809: Obtuse error message when migration dependencies are missing
* Issue #2397791: MigrationBase::handleException should handle multiple errors via field_attach_validate()
* Issue #2309563: Add support for running migrations via wildcard name
* Issue #2095841: Add MigrationBase methods to enable/disable mail system.
* Issue #2419373: Performance improvement when using Source migrations in combination with MigrateSQLMap
* Issue #2141687: Make error messages include more information when migrating files
* Field sanitization added to prevent possibility of XSS - see security advisory https://security.drupal.org/node/155268.
* Issue #2447115: Mapping editor does not properly save XML mappings
* Issue #2497015: Remapping taxonomy terms breaks term reference import on dependant migrations
* Issue #2488560: MigrateSourceList and MigrateSourceMultiItems getNextRow() stops after only one iteration
* Issue #2446105: Source fields getting reset as "do not migrate" after mapping and saving
* Issue #2415977: /tmp is hard-coded in migrate_ui
* Issue #2475473: Drush idlist option broken
* Issue #2465387: Unknown option: --stop during migrate-import via Drush
**Important: If you are upgrading from Migrate 2.5 or earlier**
Migration developers will need to add the "advanced migration information" permission to their roles to continue seeing all the info in the UI they're used to.
Auto-registration (having classes be registered just based on their class name, with no call to registerMigration or definition in hook_migrate_api()) is no longer supported. Registration of classes defined in hook_migrate_api() is no longer automatic - do a drush migrate-register or use the Register button in the UI to register them.
Migration class constructors should now always accept an $arguments array as the first parameter and pass it to its parent. This version does support legacy migrations which pass a group object, or nothing, but these methods are deprecated.