This is a legacy I would like to clean up before going to beta - however, it will cause some pain for current users of the migrate module. When originally implemented, the module had parallel sets of "source" and "destination" hooks - the former involved with pulling raw data into the Drupal database, and the latter with transmogrifying that data into Drupal objects. The source-handling parts of the migrate module were separated out into the Table Wizard module, so that "destination" in the middle of all the function and hook names really serves no purpose any more - other than to inflate hook names.
This won't be difficult to handle - a few global replace actions should get your code updated to the new world. Just a heads-up, and a reminder not to blindly update the Migrate module - always check CHANGELOG.txt before bringing in a new update. Until we go to beta (at which point I will consider the API locked in), incompatible changes may happen at any time (but will always be documented in CHANGELOG.txt).
One can even anticipate the change - e.g., rename mymodule_migrate_destination_prepare_node() to mymodule_migrate_prepare_node(), and add a temporary
mymodule_migrate_destination_prepare_node() that just calls mymodule_migrate_prepare_node().
Thanks.
Comments
Comment #1
mikeryanCommitted. Pay attention when running update.php!
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).