Bachir Soussi Chiadmi
f2b8ace9b7
FINAL suepr merge step : added all modules to this super repos
|
9 years ago | |
|---|---|---|
| .. | ||
| migrate_extras_examples | 9 years ago | |
| tests | 9 years ago | |
| LICENSE.txt | 9 years ago | |
| README.txt | 9 years ago | |
| addressfield.inc | 9 years ago | |
| cck_phone.inc | 9 years ago | |
| entity_api.inc | 9 years ago | |
| flag.inc | 9 years ago | |
| geofield.inc | 9 years ago | |
| interval.inc | 9 years ago | |
| media.inc | 9 years ago | |
| migrate_extras.info | 9 years ago | |
| migrate_extras.migrate.inc | 9 years ago | |
| migrate_extras.module | 9 years ago | |
| name.inc | 9 years ago | |
| pathauto.inc | 9 years ago | |
| privatemsg.inc | 9 years ago | |
| profile2.inc | 9 years ago | |
| rules.inc | 9 years ago | |
| user_relationships.inc | 9 years ago | |
| votingapi.inc | 9 years ago | |
| webform.inc | 9 years ago | |
README.txt
The Migrate Extras module provides extensions to Migrate (http://drupal.org/project/migrate)
to support various contributed modules. The ideal place to implement migration support
for a contributed module is in that module. That way, the migration support is always
self-consistent with the current module implementation - it's not practical for the
migrate_extras module to keep up with changes to all other contrib modules. Support
for contributed modules may be added to migrate_extras for two reasons - if the module's
maintainer does not accept a patch providing migration support, or as an intermediate
step before submitting such a patch to the other module.
In cases where modules supported by migrate_extras end up implementing the support
themselves, you could at least temporarily end up with redundant implementations.
The extra implementation may be disabled at admin/content/migrate/configure.
The following modules are currently supported in Migrate Extras on Drupal 7 (note
that Date module support has moved into the Date module itself):
Address Field
Entity API
Flag
Geofield
Interval
Media
Name Field
Pathauto
Phone Number (cck_phone)
Private Messages
Profile2
Rules
User Relationships
Voting API
Webform
Compatibility
-------------
This release of Migrate Extras requires Migrate V2.4-beta1 or later.
Migrate_Extras_Examples
----------------
See the Examples folder for a few implemented Migrations that you can run and
inspect.
Maintainers
-----------
Frank Carey http://drupal.org/user/112063
Mike Ryan - http://drupal.org/user/4420
Moshe Weitzman - http://drupal.org/user/23
to support various contributed modules. The ideal place to implement migration support
for a contributed module is in that module. That way, the migration support is always
self-consistent with the current module implementation - it's not practical for the
migrate_extras module to keep up with changes to all other contrib modules. Support
for contributed modules may be added to migrate_extras for two reasons - if the module's
maintainer does not accept a patch providing migration support, or as an intermediate
step before submitting such a patch to the other module.
In cases where modules supported by migrate_extras end up implementing the support
themselves, you could at least temporarily end up with redundant implementations.
The extra implementation may be disabled at admin/content/migrate/configure.
The following modules are currently supported in Migrate Extras on Drupal 7 (note
that Date module support has moved into the Date module itself):
Address Field
Entity API
Flag
Geofield
Interval
Media
Name Field
Pathauto
Phone Number (cck_phone)
Private Messages
Profile2
Rules
User Relationships
Voting API
Webform
Compatibility
-------------
This release of Migrate Extras requires Migrate V2.4-beta1 or later.
Migrate_Extras_Examples
----------------
See the Examples folder for a few implemented Migrations that you can run and
inspect.
Maintainers
-----------
Frank Carey http://drupal.org/user/112063
Mike Ryan - http://drupal.org/user/4420
Moshe Weitzman - http://drupal.org/user/23