I have created migration code for upgrading fields from D6 > D7 at #781088: Updating CCK Fields and Data from D6 to D7. I have tried to do it generically enough that it will do a basic migration of all fields while allowing modules to implement hooks where they can tweak the process to do things like change the field type or widget type name. I want to open a discussion about how to coordinate an upgrade path from D6 node and user reference to the new code.

Comments

mradcliffe’s picture

mradcliffe
he/him
Primary language English
CreditAttribution: mradcliffe commented

It looks like content_migrate_select() will need to allow references to alter the $available_modules array so it's key is nodereference/userreference and not node_reference/user_reference.

Owen Barton’s picture

Owen Barton CreditAttribution: Owen Barton commented
Status: Active » Needs review

Just updating this ticket to note that work appears to be actively in progress in CVS HEAD (2.x-dev is behind) - the dev branches of both modules seem to be playing together pretty well. (I spent a little while earlier working on a patch as there was no update here and then noticed the same fix committed to CVS as I worked).

yched’s picture

yched CreditAttribution: yched commented

Development takes place in 7.x-2.x.

The patches for the migration hooks were erroneously committed to HEAD initially. I committed them back to the 7.x-2.x branch, and removed all code from HEAD for now, to avoid further confusion.

yched’s picture

yched CreditAttribution: yched commented
Status: Needs review » Fixed

Should be fixed now, BTW.

Status: Fixed » Closed (fixed)

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