Putting this here, assigning to myself.

I'll use this to collect up relevant issues, and draft the docs.

If there are some issues that are particularly relevant, please leave them here.

And, if this is already in progress, please point me at that effort, and I'm glad to pitch in there.

Comments

bonobo’s picture

bonobo commented

#366364: [meta] Data migration from D6 contrib CCK fields to D7 Field API

bonobo’s picture

bonobo commented

#781088: Updating CCK Fields and Data from D6 to D7

bonobo’s picture

bonobo commented

#690478: Maintainer needed for D7 versions of nodereference / userreference

karens’s picture

karens commented

http://drupal.org/node/728792 - Updating CCK Field Modules from D6 to D7

karens’s picture

karens commented

http://drupalcode.org/viewvc/drupal/drupal/modules/field/field.api.php?r...

bonobo’s picture

bonobo commented

#824812: Future of fieldgroup - call for volunteers

bonobo’s picture

bonobo commented

#690140: Status of CCK3 and plans for D7

bonobo’s picture

bonobo commented

An incomplete list of topics that need to be documented:

* Upgrade process for CCK fields that have been moved from D6 CCK to core D7
* Upgrade process for CCK fields that were part of D6 CCK and remain in D7 CCK (nodereference, userreference)
* Upgrade process for CCK fields that were part of CCK in D6 and are separate projects in D7 (field permissions, fieldgroup)
* Upgrade process for CCK fields that were contrib in D6 and are now core in D7 (Filefield, Imagefield, etc)
* Upgrade process for CCK fields that were contrib in D6 and remain contrib in D6 (emfield, etc)
* Differences b/w upgrading b/w D6 CCK 2 and D6 CCK 3

Any feedback on what is missing from this list, and/or better ways to structure this, are greatly appreciated. From reading through the issues, it seems like the above list addresses the majority of the use cases we'll see on upgrades, but let's identify anything that should also be included in the above list.

bonobo’s picture

bonobo commented

Another possible wrinkle could involve upgrading CCK fields that have been created by Features in D6. I'm flagging this as something that needs to be tested specifically because of this comment.

Possibly, this will be a non-issue, but putting it here as another area in need of testing and documentation.

bonobo’s picture

bonobo commented

#940076: Upgrade to D7 of Image Fields and other fields fails

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

FWIW, I'd love to embed instructions for any special upgrade steps for CCK into http://drupal.org/project/upgrade_status -- the new Upgrade Assist module is even able to instruct users to perform pre-upgrade tasks; i.e., in preparation for the upgrade, if anything like that is required.

bonobo’s picture

bonobo commented

Field Group Module: http://drupal.org/project/field_group

bonobo’s picture

bonobo commented

@sun - I'd love to see this documentation (once it takes shape) in Update Status.

bonobo’s picture

bonobo commented

Been buried with work. Just updating this that this is still on my radar.

alanburke’s picture

alanburke commented

Subscribe

EvanDonovan’s picture

EvanDonovan commented

Related issue: #984444: Page on modules now in core in D7 needs reorganization, table of contents. The OP complained that there was no reference to CCK fields needing a separate upgrade path, and wanted that added to UPGRADE.txt.

jenyum’s picture

jenyum commented

subscribing

porg’s picture

porg commented
Status: Active » Fixed

Meanwhile there is the handbook page: #1144136: Migrating D6 Content Construction Kit (CCK) to D7 Fields

Status: Fixed » Closed (fixed)

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