First off, WOW. I am easily amused, but this is a seriously crafty body of work, and you're really keeping the issue queue flowing! Kudos.

From what I can tell, simply registering a D6 Node migration should actually create the destination D7 content types and fields, so I must be missing something minor that I have not yet found: Result of imports of Drupal 6 CCK nodes is just plain-jane nodes.

Could it be that my empty, "minimal profile" D7 destination is too minimal? I went ahead and added entity to no evident improvement.. Do I need cck 7.x..-dev which talks about content_migrate?

Thanks!

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Title: D6 cck nodes import as D7 nodes but no "content type" or fields, what gives? » Create content types/fields
Component: Documentation » Code
Category: support » feature

No, migrate_d2d migrates node data, but does not create content types and fields. I have it in mind to add this capability as part of #1826132: Support new Migrate wizard framework, it's a significant enough enhancement that's it's worth tracking here in its own issue.

texas-bronius’s picture

texas-bronius commented

Thanks for the clarification, Mike. I've posted this tidbit on the handbook to help anyone else who seeks the holy grail. I agree this is a large enough task to track its own issue, but I wonder whether it could be developed independently of #1826132: Support new Migrate wizard framework, presuming the UI work branch is focused primarily on UI? #lovegit

As I work through my own internal flow, I will be happy to contribute back what I can where I can. Thanks again for this great module pair!

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Closed (duplicate)

Closing in favor of the original issue: #1545128: Migration of structure