CCK as an acronym has no value in D7 as both field API and field UI is (almost) in. Let's remove those references where appropriate:
grep -R 'CCK' *
(1) CHANGELOG.txt: Kit (CCK) module.
(2) modules/field/field.module: $output .= '<p>' . t('The Field API provides no user interface on its own. Use the Content Construction Kit (CCK) contrib module to manage custom fields via a web browser.') . '</p>';
(3) modules/field/field.module: * - used by Views integration in CCK D6
(4) modules/simpletest/tests/field_test.module: * for each form element. This is a change from earlier CCK versions
(2) seems definitely obsolete, the rest need closer review.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 552084.patch | 4.51 KB | jhodgdon |
Comments
Comment #1
jhodgdonThere are also two references to Content Construction Kit without the acronym:
modules/field/field.module line 40:
* custom data structures. The Content Construction Kit
* user-interface module uses this API for its major functionality.
node.install around line 303:
'custom' => array(
'description' => 'A boolean indicating whether this type is defined by a module (FALSE) or by a user via a module like the Content Construction Kit (TRUE).',
'type' => 'int',
Comment #2
yched commentedLOL at
'description' => 'A boolean indicating whether this type is defined by a module (FALSE) or by a user via a module like the Content Construction Kit (TRUE).',: CCK doesn't define node types since D5 - and we didn't have db schemas or column descriptions back then...Comment #3
jhodgdonHere is a patch to remove/alter these references.
Comment #4
pinoloThe patch applies and looks fine to me. After applying, the only reference to CCK is the presumably developer-generated comment in modules/field/field.module
Comment #5
yched commentedLooks fine to me too.
Comment #6
webchickCommitted to HEAD. Thanks!