Create Files to enable end user to migrate Content Types from Drupal 7 to Drupal 8.
| Comment | File | Size | Author |
|---|---|---|---|
| #52 | 2423103-51.patch | 50.14 KB | phenaproxima |
| #49 | 2423103-49.patch | 52 KB | phenaproxima |
| #48 | 2423103-48.patch | 51.99 KB | phenaproxima |
| #46 | diff-2423103.txt | 13.09 KB | phenaproxima |
| #44 | interdiff-2423103-43-44.txt | 8.26 KB | phenaproxima |
Comments
Comment #1
miguelc303 commentedI did a patch to enable end users to migrate Content Types from Drupal 7 to Drupal 8.
Comment #2
miguelc303 commentedThis patch add to the content type the information body to display content correctly.
Comment #3
benjy commentedComment #4
miguelc303 commentedComment #5
miguelc303 commentedAdded organization support to Anexus IT
Comment #6
phenaproximaWrote a very, very basic test of this migration. In the meantime, it's blocked by #2495755: Create MigrateDrupal7TestBase.
Comment #7
phenaproximaComment #8
phenaproximaRenaming to reflect the closure of #2466795: Migration Files for Drupal 7 Nodes .
Comment #9
phenaproximaAdded a basic d7_node migration and a test for it. This migration does NOT migrate any field data -- only the metadata about the nodes and their revisions. Given the unified way in which D7 handles fields, I think it makes sense to migrate field data after the owning entities' metadata.
Comment #10
phenaproximaAnnnd a patch would be helpful.
Comment #11
phenaproximaAdded unit tests of the d7_node and d7_node_type source plugins.
Comment #12
phenaproximaMerged #2466793: Migration Files for Drupal 7 Node Settings and wrote a test for it.
Comment #13
phenaproximaImproved the tests, particularly the one for node type migration. I'd say this is now truly ready for review and commit.
Comment #14
benjy commentedIt would be nice to have a diff between the D6 versions so we can get an idea of how much is copy/paste vs new stuff. Not sure how easy that is?
Comment #15
phenaproximaIt's tedious, but not beyond a bit of shell scripting. Now if only I knew how to write proper shell scripts :)
Comment #18
quietone commentedWorking on a re-roll
Comment #19
quietone commentedThis is an incomplete reroll and left at Needs Work.
phenaproxima suggested on IRC that this needs to wait on other work (sorry don't know the issues numbers).
Comment #20
phenaproximaIt's OK to continue re-rolling it; it simply won't be commit-able until migration paths for text formats and fields have landed.
Comment #21
webchickSince this is one of the "big 4" content migrations, escalating to a Migrate critical.
Comment #22
quietone commented@phenapromixa, ok. I guess I misunderstood part of what you said. I'll continue then.
Comment #23
quietone commentedReroll.
Comment #25
quietone commentedOne of the failures is on the test of the title field label for the migrated node, in NodeTypeTest. That got me looking at the d6 version and that doesn't test for the title field label. So, I added a test and that fails too. But when running a D6->D8 migration, I used migrate_upgrade module, the title field is correctly migrated. Please enlighten me on how to properly test for this.
Comment #26
phenaproximaLooks like that needs a separate migration, because alterations to the title field are overrides of base node fields. The attached patch provides such a migration, along with a test.
Comment #28
phenaproximaWhoa -- somehow the patch got a lot of extra cruft attached to it (my fault, apparently -- see the jump in file size at #13 :). This is re-roll without the cruft.
Comment #30
phenaproximaFixing the test failures and re-added the unit tests to the patch.
Comment #32
phenaproximaFixing the test failure. Configuring the node types to pass the test put a lot of stuff into the {variable} table, but due to migrate-db.sh's hashing system, there's not much I can do about that.
Comment #33
phenaproximaThis is blocked by #2414651: Migration Files for Drupal 7 Users.
Comment #34
phenaproximaUnblocked!
Comment #35
phenaproximaJust changing the status. Nothing to see here.
Comment #42
mikeryanAs expected.
Comment #43
phenaproximaRe-rolled from the IMP2 sandbox.
Comment #44
phenaproximaFixing failures and other assorted sadnesses.
Comment #45
mikeryanComment #46
phenaproximaDiffed the relevant migration templates and source plugins.
Comment #47
mikeryanD6 should do the same thing, if we don't fix it here we need to open an issue for it.
I think I see why the other dependencies are gone, but it seems we have no dependencies on field migrations? And, although nodes themselves don't need filter formats, 99.9% of the time they will have fields that do (maybe fields should have a dependency on d7_filter_format?).
As above, should followup with D6 fix.
Not seeing any significant issues here, but I'm not sure I'm comfortable RTBCing this until we can actually test with migrate_upgrade (brokenness elsewhere is preventing that)...
Comment #48
phenaproximaRe-rolled due to Variable.php conflicts, and fixed #47.1 and #47.3.
Comment #49
phenaproximaFixed a YAML parse error. I never cease to marvel at just how badly a one-line error can hose everything.
Comment #50
mikeryanWorks with migrate_upgrade, RTBC!
Comment #52
phenaproximaReverted to statically mapping the uid in d7_node and d7_node_revision. The test failures tie directly into #2560637: Improve handling of uid 1 during migration and are outside the scope of this issue.
Comment #53
phenaproximaTestbot seems to be having a tough day today, so I'm pre-emptively re-RTBCing this since it's passed DrupalCI.
Comment #56
webchickAdam walked me through this patch on IRC. The one thing that was weird was switching from uid 1 to uid 2 as the owner of the node in the database dump, but this was done because of #2560637: Improve handling of uid 1 during migration, which has now been escalated to a Migrate critical.
Everything else looks great, and I had the opportunity to see it actually work LIVE on a hangout with Adam and Mike. W00t!
Committed and pushed to 8.0.x. YEAH! :D