[Summary view] [Print] [Text view]

   1  //$Id: CHANGELOG.txt,v 1.1.2.62 2009/09/22 20:03:56 mikeryan Exp $
   2  
   3  Migrate 1.0 Beta 3
   4  ===========
   5  - #430100 - Fix to filefield support
   6  - #576330 - Cleanup of comment migration
   7  - #392404 - More simpletest work.
   8  - #579064 - Fixed semaphore handling.
   9  - #579068 - Added a toggle to control cron processing. Note that it defaults to on for
  10              existing installations, but off for new installations.
  11  - #572896 - Fix xlat support (mapping of source URLs to Drupal URLs)
  12  - #567686 - Fixed sorting, tweaked layout of content set listing
  13  - #531474 - Support for comment parent IDs
  14  - #546398 - Drush improvements - message and timer logging
  15  - #572670 - Drush - import specific IDs
  16  - #568558 - Support for datetime fields
  17  - #430100 - Filefield support
  18  Validation functions for content set creation/editing.
  19  Fixed a couple of annoying notices.
  20  
  21  Migrate 1.0 Beta 2
  22  ===========
  23  - #566562 - Objects not being passed by reference to prepare and complete hooks
  24  - #566588 - Provide public API functions for map and message table names. 
  25              _migrate_map_table_name() and _migrate_message_table_name() are now
  26              deprecated.
  27  
  28  Migrate 1.0 Beta 1
  29  ===========
  30  
  31  IMPORTANT!
  32  
  33  If you have been using a pre-beta version of the migrate module, please note that
  34  shortly before the release of beta 1 some refactoring was done that requires manual attention.
  35  
  36  Updating from a version before 2009/08/23:
  37  
  38  All hook names containing "destination" no longer contain "destination". The update function
  39  will attempt to identify hook implementations you will need to rename, but please go through
  40  your code carefully to make sure there's nothing else that needs to change. Also, the content
  41  set pages are now under admin/content/migrate/content_sets (rather than
  42  admin/content/migrate/destinations).
  43  
  44  The map and message table names have been renamed. If you have constructed any views
  45  specifically accessing these tables, the views will need to be reconstructed.
  46  
  47  Updating from a version before 2009/08/18:
  48  
  49  The way content_profile mappings are stored has changed - if you are migrating users
  50  using content_profile, you must edit your user content sets and reestablish your mappings 
  51  to any content_profile fields.