Migrate node translation settings.
This was originally part of #2225775: Migrate Drupal 6 core node translation to Drupal 8. It is moved here to reduce the scope of that issue. And it conforms to the existing practice of a separate issue for each migration item.
Credit goes to phenaproxima.
Comment | File | Size | Author |
---|---|---|---|
#20 | interdiff-2660028-11-20.txt | 3.15 KB | quietone |
#20 | 2660028-20.patch | 5.65 KB | quietone |
#18 | interdiff-2660028-11-18.txt | 4.94 KB | quietone |
#18 | 2660028-18.patch | 7.63 KB | quietone |
#11 | interdiff-2660028-5-11.txt | 1.56 KB | quietone |
Comments
Comment #2
quietone CreditAttribution: quietone commentedComment #3
quietone CreditAttribution: quietone commentedAdded blank line after namespace in two files.
Comment #4
quietone CreditAttribution: quietone commentedThis should be a serialized string. My D6 test site and the D6 dump have, < s:1:"2"; >
Comment #5
quietone CreditAttribution: quietone commentedChanged the value to string to match the source data.
Comment #6
quietone CreditAttribution: quietone commentedHow to run this test with PHP 5.5 & MySQL 5.5?
Comment #7
quietone CreditAttribution: quietone as a volunteer commentedthx drumm for removing the test that was stuck in the queue.
This is really ready for review now.
Comment #8
Gábor HojtsyComment #9
quietone CreditAttribution: quietone as a volunteer commentedComment #10
Kristen PolThanks for the patch! Here's some feedback:
Nitpick: Rather than use 22, I think it would be more clear to count the characters of the 'language_content_type_' string.
Nitpick: Use single quotes instead of double.
Nitpick: Over 80 characters.
Where is the Company node type defined? Perhaps this is leftover from some other code?
Comment #11
quietone CreditAttribution: quietone as a volunteer commentedThx for the review.
1. Changed.
2. Fixed.
3. I guess you are referring to line 5. If so, I'm not sure how to fix it. (Quick search of the standards and I didn't see it. Can do more , I have to catch a bus).
4. The Company node is in the Drupal 6 test fixture, migrate_drupal/tests/fixtures/drupal6.php, the source db for these tests.
And on looking at this again, I think the source_provider is wrong.
Comment #12
Kristen PolWow! That was fast. :)
What's the best way to test this?
Comment #13
quietone CreditAttribution: quietone as a volunteer commentedTo test, I suppose you can run a full migration and then edit the article and company content types to see how the language settings are different.
And the source_provider is correct.
Comment #14
Kristen PolThanks for the info. How does one "run a full migration"? :) I haven't done any migration testing before (though I've done migrations between Drupal to Drupal before... just not to D8 yet).
Comment #15
quietone CreditAttribution: quietone as a volunteer commentedStart with a fresh D8, then install Drupal Upgrade. Then you can use the UI or drush. For the UI, go to /upgrade. For drush just use,
drush migrate-upgrade --legacy-db-url=mysql://user:pass@12.34.56.78/d6db --legacy-root=http://myd6site.com
.To use the drupal6 test fixture as the source import it using db-tools.
php core/scripts/db-tools.php import --database d6_connection core/modules/migrate_drupal/tests/fixtures/drupal6.php
Generating database fixtures for D8 Migrate tests has more info about working with the test fixture.
That should do it, I hope.
Comment #18
quietone CreditAttribution: quietone as a volunteer commentedReroll for 8.1.x
Comment #20
quietone CreditAttribution: quietone as a volunteer commentedAh, #18 is a bad patch, ignore it. (Where I work is full of interruptions and noise).
Try again.
Comment #21
quietone CreditAttribution: quietone as a volunteer commentedComment #22
Gábor HojtsyHm, so what does this do that #2225271: Migrate content type language settings from Drupal 6 & 7 did not do? That one is marked fixed and it deals with
'language_content_type_' . $type
and even i18n node type level settings. How is this different? :) That one landed on June 21st.Comment #24
maxocub CreditAttribution: maxocub commentedComment #25
quietone CreditAttribution: quietone as a volunteer commentedYes, it does appear that #2225271: Migrate content type language settings from Drupal 6 & 7 takes care of migrating the node translation settings. Therefore, closing this as a duplicate.
Comment #26
Gábor HojtsyRemoving from sprint too.