Set up to test:
Important: See https://groups.drupal.org/node/398588 to get set up. This page also includes instructions for re-setting to a clean destination.
Ensure modules are enabled on the source and destination sites:
D6: Block module is enabled by default.
D8: Custom block module is enabled by default.
Place the manifest file in the D8 site root
Download the attached .yml file.
Run the migration
From the D8 site root:
drush migrate-manifest --db-url=mysql://user:pass@source/source D6Manifest-CustomBlocks.yml
If you've updated/installed drush 7.x after July 16, 2014, you'll want to use:
drush migrate-manifest --legacy-db-url=mysql://user:pass@source/source D6Manifest-CustomBlocks.yml
Compare post-migration settings
Ensure custom blocks from D6 migrated properly into D8. Until #2250429: d6_block migration not migrating all blocks and #2248407: D6 Block Mapping are committed, blocks will probably not end up in the proper region.
Success?
If your site migrates successfully, let us know with a comment on this issue. We'd love to hear details like:
- the size and complexity of the site you migrated
- performance observations
- any customizations you made to the migration manifest!
Problems?
Open a new issue as a normal priority support request. Describe what happened, including the exact text of error messages. Depending on the nature of the problem, someone may ask for a sample of the data you're trying to migrate or follow up with other questions.
Remember, too, that this is pre-Beta. The focus is on D6 core > D8 core, not custom work or contributed modules, so there may be portions of your site that need special consideration that won't get addressed at this point in the process.
Important: Please connect your issue to this issue when you create it by using entering this ticket number, 2221815 , in the Parent issue field!
Comment | File | Size | Author |
---|---|---|---|
#2 | D6Manifest-CustomBlocks.yml | 52 bytes | ultimike |
Comments
Comment #1
eliza411 CreditAttribution: eliza411 commentedComment #2
ultimikeComment #3
bdone CreditAttribution: bdone commentedi've updated instructions' migrate-manifest command to use the db-url option, per latest version of migrate-manifest.
Comment #4
brockfanning CreditAttribution: brockfanning commentedI ran this migration and it was successful. Note that in addition to applying the patch mentioned in the issue description, you need to add "- d6_block" to the manifest if you want the blocks mapped to regions. (which isn't necessary to test this)
Comment #5
ultimikeComment #6
benjy CreditAttribution: benjy at CodeDrop commentedMarking this issue fixed as I think we've reached a point now where the Drupal 6 to Drupal 8 issue path is stable enough that we can simply open individual issues as problems arise.