Downloads
Release notes
Migrate 1.0 Beta 3
===========
- #430100 - Fix to filefield support
- #576330 - Cleanup of comment migration
- #392404 - More simpletest work.
- #579064 - Fixed semaphore handling.
- #579068 - Added a toggle to control cron processing. Note that it defaults to on for
existing installations, but off for new installations.
- #572896 - Fix xlat support (mapping of source URLs to Drupal URLs)
- #567686 - Fixed sorting, tweaked layout of content set listing
- #531474 - Support for comment parent IDs
- #546398 - Drush improvements - message and timer logging
- #572670 - Drush - import specific IDs
- #568558 - Support for datetime fields
- #430100 - Filefield support
Validation functions for content set creation/editing.
Fixed a couple of annoying notices.
Migrate 1.0 Beta 2
===========
- #566562 - Objects not being passed by reference to prepare and complete hooks
- #566588 - Provide public API functions for map and message table names.
_migrate_map_table_name() and _migrate_message_table_name() are now
deprecated.
Migrate 1.0 Beta 1
===========
IMPORTANT!
If you have been using a pre-beta version of the migrate module, please note that
shortly before the release of beta 1 some refactoring was done that requires manual attention.
Updating from a version before 2009/08/23:
All hook names containing "destination" no longer contain "destination". The update function
will attempt to identify hook implementations you will need to rename, but please go through
your code carefully to make sure there's nothing else that needs to change. Also, the content
set pages are now under admin/content/migrate/content_sets (rather than
admin/content/migrate/destinations).
The map and message table names have been renamed. If you have constructed any views
specifically accessing these tables, the views will need to be reconstructed.
Updating from a version before 2009/08/18:
The way content_profile mappings are stored has changed - if you are migrating users
using content_profile, you must edit your user content sets and reestablish your mappings
to any content_profile fields.
