Without installing and playing around with CCK it is hard to get an idea of what the module does or what it should be used for. Are there any demos or use cases for CCK? Why use CCK as opposed to flexinode? I know there is some major documentation regarding the developement, but I haven't seen much in laymen's terms that helps explain when or why CCK would be used as opposed to flexinode or the core content types.

Comments

kkaefer’s picture

kkaefer commented

CCK is about the same as flexinode. But flexinode's backend was pretty messed up and completely unstructured.

jonbob’s picture

jonbob commented
Status: Active » Fixed

In short, here are the differences:

- CCK is being proposed as an addition to the Drupal core software. It is a contributed module for now, though.
- CCK is architected, with a much greater degree of pre-planning. Flexinode was written as "one to throw away," but was adopted with greater vigor than I expected by the community. That always seems to happen with prototypes...
- CCK plays better with core Drupal concepts like the module system.
- CCK assigns semantic meaning to fields, and fields can appear in multiple content types if they mean the same thing.

That said,

- CCK currently has fewer field types ready to go than Flexinode does, simply due to its relative immaturity.
- There will be an upgrade path provided from Flexinode to CCK, at least for field types that have a 1-1 correspondence.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)