Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Create a set of migration files to enable users to migrate Drupal 7 Contact to Drupal 8
Comment | File | Size | Author |
---|---|---|---|
#85 | 2382703-85.patch | 23.19 KB | phenaproxima |
#83 | 2382703-82.patch | 21.95 KB | phenaproxima |
#73 | 2382703-73.patch | 17.79 KB | phenaproxima |
#69 | 2382703-69-EXPERIMENT.patch | 19.01 KB | phenaproxima |
#65 | 2382703-65-EXPERIMENT.patch | 19 KB | phenaproxima |
Comments
Comment #1
miguelc303 CreditAttribution: miguelc303 commentedI did a patch to enable user to import Drupal 7 Contact in Drupal 8 following the same logic applied in Drupal 6 migrations files.
Comment #2
-enzo- CreditAttribution: -enzo- commentedComment #3
benjy CreditAttribution: benjy commentedWork on Drupal 7 is still a little quiet so thanks for making a start. This will require tests, there should be plenty of examples in core already.
Comment #4
-enzo- CreditAttribution: -enzo- commented@benjy correct I start because I don't see the options, so I'm working in a migrate my own website and creating the code necessary to do the job, I know tests are missing, but I'm tests are not my stuff. so I will add more changes waiting to someone contribute test.
Comment #5
hosef CreditAttribution: hosef commentedMoving to the IMP issue queue.
Comment #6
miguelc303 CreditAttribution: miguelc303 commentedSee parent issue #2181257: [meta] Variables to config migration [d7] for instructions.
Comment #7
benjy CreditAttribution: benjy at CodeDrop commentedComment #8
miguelc303 CreditAttribution: miguelc303 at Anexus commentedComment #9
-enzo- CreditAttribution: -enzo- at Anexus commentedAdded organization support to Anexus IT
Comment #10
phenaproximaSelf-assigning -- let's bring it home!
Comment #11
-enzo- CreditAttribution: -enzo- at Anexus commented@phenaproxima what does mean? what is the next step?
Comment #12
phenaproxima@-enzo-, that's just an expression :) The next step is to write a passing automated test for the d7_contact_category migration, and add it to the patch in #6.
Comment #13
phenaproximaAdded a test of the migration.
I also made the d6_contact_category source plugin into a generic contact_category source, since it's identical between D6 and D7 and it seems sad-making to not reuse that code.
Comment #14
phenaproximaMoving into the core issue queue so testbot will put the patch through its paces.
Comment #15
phenaproximaRe-upping the patch so testbot will (hopefully) test it.
Comment #21
phenaproximaFixed errors in the contact_category plugin's unit test.
Comment #22
phenaproximaMinor test cleanup.
Comment #24
phenaproximaBlocked by #2495755: Create MigrateDrupal7TestBase.
Comment #25
phenaproximaComment #26
dawehnerIs it intended to lose d6 test coverage?
Comment #27
benjy CreditAttribution: benjy at CodeDrop commentedYeah that doesn't seem right.
Comment #28
phenaproximaWhat? There are two distinct tests of this migration:
src/Tests/d6/MigrateContactCategoryTest.php
andsrc/Tests/d7/MigrateContactCategoryTest.php
. The former one is already in HEAD, though, so this patch adds the latter one.Comment #29
benjy CreditAttribution: benjy at CodeDrop commentedAh right, the diff was confusing, bit clearer once I actually applied it. I checked the D7 contact module and the fields are the same so I think this is good apart from a few small bits:
Missing function doc.
Why is this assertEqual when surrounded by assertIdentical's?
This is contact_category now?
Comment #30
phenaproximaFixed. Regarding #3 -- yes, I've renamed the plugin since the functionality is identical.
Comment #37
phenaproximaRe-rolled and merged #2353697: Variable to config: contact.settings [d7].
Comment #39
phenaproximaWhoops.
Comment #41
phenaproximaRe-rolling again.
Comment #42
quietone CreditAttribution: quietone commentedNearly finished rerolling but too late to continue.
Comment #43
quietone CreditAttribution: quietone commentedReroll
Comment #46
quietone CreditAttribution: quietone commentedNo interdiff due to changes in Variable.php
Comment #49
quietone CreditAttribution: quietone commentedThis should fix d7/MigrateContactSettingsTest but not the other errors. And it is too late to continue.
Comment #52
quietone CreditAttribution: quietone commentedPutting the schema in the correct file definitely helps.
Comment #55
quietone CreditAttribution: quietone commentedLooks like it was some overzealous editing.
Comment #56
phenaproximaA few fixes...
Comment #62
phenaproxima@mikeryan tells me that the failures in #59 have to do with the beta update path. So this patch is an experiment to see if adding an update function to Contact will fix the failures...
Comment #64
quietone CreditAttribution: quietone commentedI meant to mark this unassigned after doing a reroll 3 weeks ago.
Comment #65
phenaproximaAnother experiment.
Comment #69
phenaproximaYet another experiment, suggested by @gábor-hojtsy -- trying to see if calling save(TRUE) in the update function will avoid these maddening schema errors.
Comment #72
benjy CreditAttribution: benjy commentedSurely we don't provide update paths for migrations just yet?
As to the schema errors, could it be possible migrate isn'e enabled?
Comment #73
phenaproximaRe-rolled and removed the update path hook.
Comment #75
phenaproximaPostponing on #2569469: [Policy, no patch] No need to provide an upgrade path for Migrations and potentially #2569605: Remove migrations from update path test fixtures, since they need to be resolved before these tests will pass.
Comment #77
phenaproximaNuh-uh.
Comment #78
phenaproximaUnblocked!
Comment #81
phenaproximaComment #83
phenaproximaRe-rolled.
Comment #85
phenaproximaI'm fixin' to fix them test failures...
Comment #86
neclimdulApplied and looked at it with git diff -M and mostly moves. New tests look good. Lets do it.
Comment #89
webchickCommitted and pushed to 8.0.x. Thanks!