Problem/Motivation

Starting to test D6 migrations.
Testing D8.0.0-Beta4 D6 Block Migration from production database.

  1. Duplicate blocks ONLY IN Block Layout (D8 site has 3 "footer-Phone", 2 "Footer menu"s and 2 "Social Rocks" blocks)
  2. This Block Migration appears to import Text formats too. In D8 under Configuration: Text formats and editors, the site has a duplicate Full HTML (full_html1). When you click Configure for that format and attempt to save, it returns the error "Text format names must be unique. A format named Full HTML already exists." So renamed to "Full HTML OLD".
  3. NOT RELATED TO MIGRATION! See the attached screenshot. Is there an explanation on why clicking on a block's "Configure" button from the Block Layout page DOES NOT show the content? I haven't played with blocks in D8 until testing and realized that there is an extra step now when editing blocks. Even when using the Context menu(Pencil) to attempt to edit the "Powered by Drupal" block you can only Configure and not Edit the block's content! I will be looking into this usability issue.

drush migrate-manifest --legacy-db-url=mysql://STUFF D6Manifest-block_0.yml

Running d6_block_content_type                                                                                                                                                                [ok]
Running d6_block_content_body_field                                                                                                                                                          [ok]
Running d6_menu                                                                                                                                                                              [ok]
Running d6_filter_format                                                                                                                                                                     [ok]
The "php_code" plugin does not exist. (/home/devemenc/public_html/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php:57)                                                [error]
Running d6_custom_block                                                                                                                                                                      [ok]
Running d6_block                                                                                                                                                                             [ok]

The error below d6_filter_format above may be due to one of the D6 site's modules added filtering to the text format; a module like email address encoding.
The important thing is that the contents of the blocks are there! Great job!

Performance Observations

Please note that the site has about 30 Custom Blocks and this count does NOT include Views-based blocks as you have to recreate those. The import was done in seconds using Drush.

CommentFileSizeAuthor
ss-20150106-d8-beta4-migrate-block-empty.jpg106.83 KBgreenskunk

Comments

greenskunk’s picture

greenskunk
Location Great Valley, NY
commented
Issue summary: View changes
ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented
Status: Active » Closed (works as designed)

Note that a D6->D8 migration is additive. Meaning that if you have blocks in D8 prior to migration, those blocks will remain in D8 post migration. This includes standard core blocks like user login, powered by Drupal etc. This is the designed behavior. This also goes for text formats and various other migrated configurations. Migration has no way of knowing if "filtered HTML" (for example) has been modified on the D6 source, so we migrate it as is while also keeping any text formats in D8.

Also, note that block content in D8 cannot be accessed via the "config" link on the main block layout page. Block content for custom blocks can be accessed via the custom block library page.

Thanks,
-mike