You are here

Home » API reference » Migrate Webform 7

README.txt in Migrate Webform 7

README for Migrate Webform

File

README.txt
View source 
  1. 

  2. /**

  3.  *  @file

  4.  *  README for Migrate Webform

  5.  */

  6. 

  7. This module is intended to bring the contents of a Drupal 6 Webform

  8. implementation into a new Drupal 7 site, done though the UI using migrate.

  9. It relies on the migrate_d2d package so that it is possible to bring over nodes

  10. created in the webform type without doing any other configration. It could in

  11. theory support reliance on a different node migration class in the future.

  12. 

  13. Should you need to add custom fields to your nodes, be sure to use migrate 2.6

  14. and enable the ui-related modules so you can see the "edit" tab on each

  15. migration class in the group.

  16. 

  17. INSTALLATION

  18. 

  19.  - After enabling, go to /admin/content/migrate

  20.  - Note the group "Webform Migrations" now appears but is empty.

  21. 

  22.  - Click "Configure Webform Migration"

  23.  - Put in the key of the secondary database you added to settings.php db array

  24.  - Save

  25.  - Back on the migrate page click "Configuration"

  26.  - Click "Register statically-defined classes"

  27.  - Now all your migrations will appear under the "Webform Migrations" group

  28. 

  29. 

  30. After you have done this it is important to know some things about how to get

  31. out of trouble if things go wrong:

  32. 

  33. - If the tables are not found, go to the main Migrate page, click

  34. the "Configuration" button and "Register statically-defined classes" again.

  35. 

  36. - Should you lose connection to the DB and it keeps importing/rolling back

  37. you can use the "reset" function in the bulk actions on the migrate page and

  38. then restart the process from where you were.

  39. 

  40. - If you changed code while running and/or did some other major breakage

  41. you can (1) use the remove the migration settings bulk action, (2) re-register

  42. the classes as outlined above. If you had items that were not rolled back

  43. you will have to go delete them the "Drupal way" as removing the migration

  44. settings deletes the map and abandons the content.

  45. 

  46. - If it is not possible to get to the /admin/content/migrate page for any

  47. reason it is safe to truncate the migrate_status table as long as you

  48. re-register classes after doing so. It will leave partially-migrated settings

  49. in-place (if you did not "remove migration settings" as outlined above, the

  50. content map will remain in-place).

  51. 

  52. NOTES

  53. 

  54.  - Files will need a "FilesMigration" or other class. Recommended to use

  55. migrate_d2d. Currently the module does not hook into this yet for the

  56. components.

  57. 

  58.  - Roles are matched by the name of the role in the old system, not by relying

  59. on a RuleMigration class. This allows migrate_api_alter to change things. It

  60. would be good if someone wrote a patch to do a second way of doing Roles that

  61. utilizes a migration class.

  62. 

  63. CREDITS

  64. 

  65. Special thanks to the commerce_migrate_ubercart devs for some ideas I borrowed.

  66. 

  67. Thanks to the two sponsors who helped make this module possible. If you are

  68. interesed in funding further work on this project please contact me.