Manual Testing: Nodes [#2222375]

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: Ensure "node" module is enabled. CCK and the following related modules can also be enabled: Phone, Text, Link, Email, Date, FileField, Image.
D8: Ensure "node" and "field" modules are enabled.

Place the manifest file in the D8 site root

Download the attached file.

Run the migration

From the D8 site root:
drush migrate-manifest --db-url=mysql://user:pass@source/source D6Manifest-Node.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-Node.yml

(Ensure that the .yml filename matches up with the one you downloaded.)

Compare post-migration settings

Ensure nodes from D6 migrated properly into D8. Note that only fields of type phone, text, link, email, date, file, and image in D6 will be migrated.

Known issues

Link fields aren't migrated properly yet. Upon initial testing, this should be resolved by #2235457: Use link field for shortcut entity
Single On/Off Checkboxes aren't migrated properly yet: #2262275: D6->D8 CCK Single On/Off Checkbox, Checkboxes/Radio buttons, and Select formatters

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, 2222375 , in the Parent issue field!

Comment	File	Size	Author
#27	D6Manifest-Node.yml	518 bytes	ultimike
#6	D6Manifest-Node.yml	309 bytes	ultimike
#5	D6Manifest-Node.yml	253 bytes	eliza411
#3	D6Manifest-Node.yml_.txt	311 bytes	eliza411
	D6Manifest-Node.yml_.txt	271 bytes	ultimike

Comments

Comment #2

eliza411 commented 23 March 2014 at 14:11

Issue summary:

View changes

Comment #3

eliza411 commented 24 March 2014 at 14:00

Status	File	Size
new	D6Manifest-Node.yml_.txt	311 bytes

1 file was hidden/shown/deleted

Status	File	Size
hidden	D6Manifest-Node.yml_.txt	271 bytes

Added the cck migrations to the manifest

Comment #4

benjy commented 26 March 2014 at 00:47

I used this manifest file to test

- d6_field_instance_settings
- d6_field_instance_defaults

These aren't migrations.

I used:

- d6_node_type
- d6_node
- d6_view_modes
- d6_filter_format
- d6_field_instance_per_form_display
- d6_field_instance_widget_settings
- d6_field_instance
- d6_field
- d6_field_settings
- d6_node_settings
- d6_cck_field_values:*
- d6_cck_field_revision:*

Comment #5

eliza411 commented 26 March 2014 at 11:43

Issue summary:

View changes

Status	File	Size
new	D6Manifest-Node.yml	253 bytes

1 file was hidden/shown/deleted

Status	File	Size
hidden	D6Manifest-Node.yml_.txt	311 bytes

Uploading the revised manifest, now a plain .yml file.

Comment #6

ultimike

English

Florida, USA

commented 5 April 2014 at 02:24

Status	File	Size
new	D6Manifest-Node.yml	309 bytes

1 file was hidden/shown/deleted

Status	File	Size
hidden	D6Manifest-Node.yml	253 bytes

Updated the manifest, based on more testing.

-mike

Comment #7

awasson commented 16 April 2014 at 00:47

I've been madly getting up to speed to contribute to this effort and I think I'm finally to the point where I can join in. I've got a Ubuntu64 Server VM running in VirtualBox with real-world data from a small website that has approximately 200 pages and fairly simple content types.

I've used the updated manifest.yml from #6

# nodes
- d6_node
- d6_node_revision
- d6_node_type
- d6_view_modes
- d6_filter_format
- d6_field_instance_per_form_display
- d6_field_instance_widget_settings
- d6_field_formatter_settings
- d6_field_instance
- d6_field
- d6_field_settings
- d6_node_settings
- d6_cck_field_values:*
- d6_cck_field_revision:*

My first couple of passes (now that I'm up to speed) took place this afternoon and it looks to me like about 25% of the node content has migrated. This site was initially built in 2010 and all of the content I can see is from that era; none of the newer content has been migrated over. So about 50 nodes out of just under 200 made it.

drush migrate-manifest mysql://dbuser:dbpass@localhost/d6_database manifest.yml

My errors are as follows:

Migration d6_field_instance did not meet the requirements            [error]
Migration d6_field_instance_widget_settings did not meet the         [error]
requirements
Migration d6_field_formatter_settings did not meet the requirements  [error]

I removed the offending entries and ran the drush command again and it ran without any errors. Success!

I'm still only seeing 25% of the node content though so I'm not sure what that is about.

On a side note, I've also been following the progress on upgrading the UI at: https://drupal.org/node/2200379. That is pretty cool!

UPDATE:
I've been lurking around my IMP site's database for a few minutes and although I'm only seeing 38 nodes that have been migrated, I'm pretty sure that all of them actually made it over. If I look at my node table there are 183 results. If I go to my node_field_data table, again 183 results with very familiar looking titles.

So I'm not sure where the disconnect is between what I can readily access and what is in the database but it looks like the majority of node content was migrated.

Comment #8

ultimike

English

Florida, USA

commented 8 May 2014 at 20:42

Project:	IMP	» Drupal core
Version:		» 8.x-dev
Component:	Miscellaneous	» migration system
Issue summary:	View changes

Comment #9

bdone commented 13 May 2014 at 20:20

Issue summary:

View changes

i've updated instructions' migrate-manifest command to use the db-url option, per latest version of migrate-manifest.

Comment #10

ultimike

English

Florida, USA

commented 21 May 2014 at 17:33

Issue summary:

View changes

Comment #11

ultimike

English

Florida, USA

commented 21 May 2014 at 17:34

Issue summary:

View changes

Comment #12

ultimike

English

Florida, USA

commented 26 May 2014 at 15:18

Issue summary:

View changes

Comment #13

Anonymous (not verified) commented 31 May 2014 at 20:40

I ran an import targeting some revisions and the items came through successfully... but with some minor issues.

The revision dates are all getting default values, set to 1969, so they are all being set to zero (the beginning of Unix time - January 1 1970 GMT).

Field migrations failed because my test source did not utilize CCK fields.

Comment #14

Anonymous (not verified) commented 2 June 2014 at 20:31

In D6 I added a text field and an integer field, then added two revisions to the node I have been testing. This node already had 3 revisions, and now has 2 more, with data in the new fields.

Result:

dates are still incorrect
new fields have the correct revision
~~body text field is GONE~~ edit: it appears in the "edit" version of the page, this may be a regression from other work that is ongoing today. edit2: caused by view modes #2278613: Body text display is blank for migrated content types

Comment #15

Anonymous (not verified) commented 1 June 2014 at 18:01

Today I connected to a real-life d6 database. The site has 21 content types and uses CCK heavily.

Here is the log:

Running d6_node_type                                                                                              [ok]
Running d6_filter_format                                                                                          [ok]
Running d6_field_settings                                                                                         [ok]
Running d6_field                                                                                                  [ok]
Attempt to create a field of unknown type <em class="placeholder">link</em>.                [error]
(/var/www/drupal/core/modules/field/src/Entity/FieldConfig.php:316)
Attempt to create a field of unknown type <em class="placeholder">link</em>.                [error]
(/var/www/drupal/core/modules/field/src/Entity/FieldConfig.php:316)
Attempt to create a field of unknown type <em class="placeholder">link</em>.                [error]
(/var/www/drupal/core/modules/field/src/Entity/FieldConfig.php:316)
Running d6_field_instance                                                                                         [ok]
Running d6_field_instance_widget_settings                                                                         [ok]
Running d6_view_modes                                                                                             [ok]
Running d6_field_formatter_settings                                                                               [ok]
Failed to lookup array (                                                                                          [error]
  0 => 'filefield',
  1 => 'thumbnail_default',
) in the static map.

Results:

content types and fields were migrated
no content was migrated.

Also, I found the following errors in the site log:

 	filter 	06/01/2014 - 13:51 	Missing filter plugin: php_code. 	Anonymous (not verified) 	
	filter 	06/01/2014 - 13:51 	Missing filter plugin: filter_null. 	Anonymous (not verified)

Comment #16

Anonymous (not verified) commented 1 June 2014 at 18:15

Second run on the real-life dataset (see above #15) after enabling "link" module :

Running d6_node_type                                                                                              [ok]
Running d6_filter_format                                                                                          [ok]
Running d6_field_settings                                                                                         [ok]
Running d6_field                                                                                                  [ok]
Running d6_field_instance                                                                                         [ok]
Running d6_field_instance_widget_settings                                                                         [ok]
Running d6_view_modes                                                                                             [ok]
Running d6_field_formatter_settings                                                                               [ok]
Failed to lookup array (                                                                                          [error]
  0 => 'filefield',
  1 => 'thumbnail_default',
) in the static map.

... same results:

content types: YES
content: NO
log errors same as in #15

Comment #17

flashwebcenter

he/him

English

Austin TX

commented 11 August 2017 at 16:07

I tested the migration using fresh drupal 6 install with devel generated nodes. No custom fields was added to drupal 6. CCK modules were enabled.

Running d6_node_type                                                                                                             [ok]
Running d6_filter_format                                                                                                         [ok]
Running d6_field_settings                                                                                                        [ok]
Running d6_field                                                                                                                 [ok]
Running d6_field_instance                                                                                                        [ok]
Migration d6_field_instance did not meet the requirements                                                                        [error]
Running d6_field_instance_widget_settings                                                                                        [ok]
Migration d6_field_instance_widget_settings did not meet the requirements                                                        [error]
Running d6_view_modes                                                                                                            [ok]
Running d6_field_formatter_settings                                                                                              [ok]
Migration d6_field_formatter_settings did not meet the requirements                                                              [error]
Running d6_node_settings                                                                                                         [ok]
Running d6_node                                                                                                                  [ok]
Running d6_node_revision                                                                                                         [ok]
Running d6_cck_field_values:page                                                                                                 [ok]
Migration d6_cck_field_values:page did not meet the requirements                                                                 [error]
Running d6_cck_field_values:story                                                                                                [ok]
Migration d6_cck_field_values:story did not meet the requirements                                                                [error]
Running d6_cck_field_revision:page                                                                                               [ok]
Migration d6_cck_field_revision:page did not meet the requirements                                                               [error]
Running d6_cck_field_revision:story                                                                                              [ok]
Migration d6_cck_field_revision:story did not meet the requirements

Comment #18

Anonymous (not verified) commented 2 June 2014 at 20:32

Missing body text is documented in #2278613: Body text display is blank for migrated content types.

Comment #19

oadaeh commented 2 June 2014 at 20:52

I'm posting this here as a kind of place holder for now, until I can nail down the details.

Fields that have "Number of values:" set to "Unlimited" do not import.

When I did this with an integer text field, this is what the results were:

Running d6_node_type                                                                                                                                                                   [ok]
Running d6_filter_format                                                                                                                                                               [ok]
Running d6_field_settings                                                                                                                                                              [ok]
Running d6_field                                                                                                                                                                       [ok]
Running d6_field_instance                                                                                                                                                              [ok]
Running d6_field_instance_widget_settings                                                                                                                                              [ok]
Running d6_view_modes                                                                                                                                                                  [ok]
Running d6_field_formatter_settings                                                                                                                                                    [ok]
Running d6_node_settings                                                                                                                                                               [ok]
Running d6_node                                                                                                                                                                        [ok]
Running d6_node_revision                                                                                                                                                               [ok]
Running d6_cck_field_values:image                                                                                                                                                      [ok]
Running d6_cck_field_values:page                                                                                                                                                       [ok]
Running d6_cck_field_values:story                                                                                                                                                      [ok]
Migration failed with source plugin exception: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your [error]
MariaDB server version for the right syntax to use near 'FROM 
content_type_story f
WHERE  (vid = '3')' at line 1: SELECT 
FROM 
{content_type_story} f
WHERE  (vid = :db_condition_placeholder_0) ; Array
(
    [:db_condition_placeholder_0] => 3
)

Running d6_cck_field_revision:image                                                                                                                                                    [ok]
Migration d6_cck_field_revision:image did not meet the requirements                                                                                                                    [error]
Running d6_cck_field_revision:page                                                                                                                                                     [ok]
Migration d6_cck_field_revision:page did not meet the requirements                                                                                                                     [error]
Running d6_cck_field_revision:story                                                                                                                                                    [ok]
Migration d6_cck_field_revision:story did not meet the requirements                                                                                                                    [error]

When I did this with an textfield text field, this is what the results were:

Running d6_node_type                                                                                                                                                                   [ok]
Running d6_filter_format                                                                                                                                                               [ok]
Running d6_field_settings                                                                                                                                                              [ok]
Running d6_field                                                                                                                                                                       [ok]
Running d6_field_instance                                                                                                                                                              [ok]
Running d6_field_instance_widget_settings                                                                                                                                              [ok]
Running d6_view_modes                                                                                                                                                                  [ok]
Running d6_field_formatter_settings                                                                                                                                                    [ok]
Running d6_node_settings                                                                                                                                                               [ok]
Running d6_node                                                                                                                                                                        [ok]
Running d6_node_revision                                                                                                                                                               [ok]

It is possible that the second run didn't have errors because it wasn't run on a clean install, but I have yet to determine that.

In both cases, the field was migrated and "Allowed number of values" appears to have been set to "Unlimited", but neither had any of the entered content migrated.

Comment #20

Anonymous (not verified) commented 2 June 2014 at 22:04

We need to add some items to the manifest file to enable taxonomy term references as fields. These have some bugs, so we should probably create a new issue.

In order to get the fields to appear I added these to the manifest:

- d6_term_node_revision
- d6_term_node
- d6_vocabulary_entity_display
- d6_vocabulary_entity_form_display
- d6_vocabulary_field_instance
- d6_vocabulary_field

However, the fields that get created have the following problems:

No terms are selected, even though the terms exist and are selectable;
only one term can be selected, even if the field was set to multiselect in D6;
required status is not carried over.

#2281591: Author information does not migrate over - Patch created, tests pass.

#2277695: D6 > D8 link migration testing - BLOCKED. None of the patches apply even after PSR-4 re-rolls.

Comment #24

ultimike

English

Florida, USA

commented 17 July 2014 at 22:28

Issue summary:

View changes

Comment #25

benjy commented 16 March 2015 at 12:58

Status:

Active

» Fixed

Marking 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.

Comment #26

30 March 2015 at 13:04

Status:

Fixed

» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Comment #27

ultimike

English

Florida, USA

commented 8 April 2015 at 17:48

Status	File	Size
new	D6Manifest-Node.yml	518 bytes

1 file was hidden/shown/deleted

Status	File	Size
hidden	D6Manifest-Node.yml	309 bytes

Updating the test manifest file...

-mike

Manual Testing: Nodes

Set up to test:

Place the manifest file in the D8 site root

Run the migration

Compare post-migration settings

Known issues

Success?

Problems?

Comments

Parent issue

Child issues