Comments

miguelc303’s picture

Issue summary: View changes
StatusFileSize
new4.24 KB

I did a patch to enable end users to migrate Content Types from Drupal 7 to Drupal 8.

miguelc303’s picture

StatusFileSize
new4.75 KB

This patch add to the content type the information body to display content correctly.

benjy’s picture

miguelc303’s picture

miguelc303’s picture

Added organization support to Anexus IT

phenaproxima’s picture

Status: Active » Postponed
StatusFileSize
new8.16 KB

Wrote a very, very basic test of this migration. In the meantime, it's blocked by #2495755: Create MigrateDrupal7TestBase.

phenaproxima’s picture

Project: IMP » Drupal core
Version: » 8.0.x-dev
Component: Code » migration system
Status: Postponed » Needs review
StatusFileSize
new8.39 KB
phenaproxima’s picture

Title: Migration Files for Drupal 7 Content Types » Migration Files for Drupal 7 Content

Renaming to reflect the closure of #2466795: Migration Files for Drupal 7 Nodes .

phenaproxima’s picture

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

phenaproxima’s picture

StatusFileSize
new17.42 KB
new8.4 KB

Annnd a patch would be helpful.

phenaproxima’s picture

StatusFileSize
new25.45 KB
new9.63 KB

Added unit tests of the d7_node and d7_node_type source plugins.

phenaproxima’s picture

StatusFileSize
new27.51 KB
phenaproxima’s picture

StatusFileSize
new50.82 KB

Improved the tests, particularly the one for node type migration. I'd say this is now truly ready for review and commit.

benjy’s picture

It 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?

phenaproxima’s picture

StatusFileSize
new24.13 KB

It's tedious, but not beyond a bit of shell scripting. Now if only I knew how to write proper shell scripts :)

quietone queued 13: 2423103-13.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 13: 2423103-13.patch, failed testing.

quietone’s picture

Working on a re-roll

quietone’s picture

StatusFileSize
new53.38 KB

This 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).

phenaproxima’s picture

It's OK to continue re-rolling it; it simply won't be commit-able until migration paths for text formats and fields have landed.

webchick’s picture

Priority: Normal » Major
Issue tags: +Migrate critical

Since this is one of the "big 4" content migrations, escalating to a Migrate critical.

quietone’s picture

@phenapromixa, ok. I guess I misunderstood part of what you said. I'll continue then.

quietone’s picture

Status: Needs work » Needs review
StatusFileSize
new44.2 KB
new14.27 KB

Reroll.

Status: Needs review » Needs work

The last submitted patch, 23: 2423103-23.patch, failed testing.

quietone’s picture

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

phenaproxima’s picture

Status: Needs work » Needs review
StatusFileSize
new46.16 KB
new6.84 KB

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

Status: Needs review » Needs work

The last submitted patch, 26: 2423103-26.patch, failed testing.

phenaproxima’s picture

Status: Needs work » Needs review
StatusFileSize
new21.39 KB

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

Status: Needs review » Needs work

The last submitted patch, 28: 2423103-28.patch, failed testing.

phenaproxima’s picture

Status: Needs work » Needs review
StatusFileSize
new27.34 KB

Fixing the test failures and re-added the unit tests to the patch.

Status: Needs review » Needs work

The last submitted patch, 30: 2423103-30.patch, failed testing.

phenaproxima’s picture

Status: Needs work » Needs review
StatusFileSize
new41.74 KB
new14.91 KB

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

phenaproxima’s picture

Status: Needs review » Postponed
phenaproxima’s picture

Status: Postponed » Active

Unblocked!

phenaproxima’s picture

Status: Active » Needs review

Just changing the status. Nothing to see here.

The last submitted patch, 6: 2423103-6.patch, failed testing.

The last submitted patch, 19: 2423103-19.patch, failed testing.

The last submitted patch, 1: migration_files_for-2423103-1.patch, failed testing.

The last submitted patch, 2: migration_files_for-2423103-2.patch, failed testing.

mikeryan queued 32: 2423103-32.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 32: 2423103-32.patch, failed testing.

mikeryan’s picture

Issue tags: +Needs reroll

As expected.

phenaproxima’s picture

Status: Needs work » Needs review
StatusFileSize
new49.05 KB

Re-rolled from the IMP2 sandbox.

phenaproxima’s picture

StatusFileSize
new49.51 KB
new8.26 KB

Fixing failures and other assorted sadnesses.

mikeryan’s picture

Issue tags: -Needs reroll
phenaproxima’s picture

StatusFileSize
new13.09 KB

Diffed the relevant migration templates and source plugins.

mikeryan’s picture

  1. +++ b/core/modules/node/migration_templates/d7_node.yml
    @@ -15,44 +15,22 @@ process:
    +  uid:
    ...
    +    migration: d7_user
    

    D6 should do the same thing, if we don't fix it here we need to open an issue for it.

  2. +++ b/core/modules/node/migration_templates/d7_node.yml
    @@ -15,44 +15,22 @@ process:
    -    - d6_filter_format
    

    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?).

  3. +++ b/core/modules/node/migration_templates/d7_node_revision.yml
    @@ -15,30 +15,21 @@ process:
    -  uid: node_uid
    

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

phenaproxima’s picture

StatusFileSize
new51.99 KB

Re-rolled due to Variable.php conflicts, and fixed #47.1 and #47.3.

phenaproxima’s picture

StatusFileSize
new52 KB

Fixed a YAML parse error. I never cease to marvel at just how badly a one-line error can hose everything.

mikeryan’s picture

Status: Needs review » Reviewed & tested by the community

Works with migrate_upgrade, RTBC!

The last submitted patch, 43: 2423103-43.patch, failed testing.

phenaproxima’s picture

Status: Reviewed & tested by the community » Needs review
StatusFileSize
new50.14 KB

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

phenaproxima’s picture

Status: Needs review » Reviewed & tested by the community

Testbot seems to be having a tough day today, so I'm pre-emptively re-RTBCing this since it's passed DrupalCI.

The last submitted patch, 48: 2423103-48.patch, failed testing.

The last submitted patch, 49: 2423103-49.patch, failed testing.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

Adam 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

  • webchick committed 982d01f on 8.0.x
    Issue #2423103 by phenaproxima, quietone, miguelc303, mikeryan:...

Status: Fixed » Closed (fixed)

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