Drupalcon notes: CCK to Fields - Getting There From Here

Flexinode was available from 2004-2007, versions 4.4-4.7. It introduced the idea of custom content types. Problem: it didn't work at all in Views. Was rewritten to scale better. CCK, the successor, lived from 2007-2010, in versions 4.7 to 6.x.

Early on, it was table-segregated by type of data: text, integer, etc. Didn't last long. Now: if the same field exists in multiple content types, it all goes in the same table.

Field data architecture: change settings or share a field after data was created could lead to potential data loss. They settled on using a per-field storage for all fields, so that data never moves.

Database optimization

Module upgrades

Data upgrades

  • May not be a normal upgrade. Likely an upgrade page listing all fields and upgrade status
  • Issue to track: http://drupal.org/node/366364
  • You can't upgrade to D7 partially. All the field modules have to go at once
  • The tables can live in your D6 tables - because we're copying from old tables to new.
  • No contrib modules are completely ready yet

New fieldable entities

New core fields

New field type: list

  • New 'list' field type in core
  • Boolean, numeric, or alpha keys
  • Allowed values as textarea with 'key | value' pairs
  • Allowed values from PHP in CCK

Translatable fields

User Profile fields

Nodereference

Userreference

Fieldgroup

  • Still in CCK. NON-functional.
  • Move to module: No immediate candidates

Content Permissions

Content Copy

Views, Devel Generate, Diff, Rules

  • All of these are still contrib, so integration is not in core.

Token

Token functionality is now in core but token integration is still in contrib.

Multigroup

all tags: