[development] No module-defined node types?

Mark Fredrickson mark.m.fredrickson at gmail.com
Thu Jan 4 17:32:51 UTC 2007

Conversely, if your custom content module just wraps what should be a
field, you are going to make me cry.

Compare the usefulness of an event node type vs. being able to attach
event data to any node type (including, but not limited to, an
extremely simple CCK "event" node type defined by either an admin, an
install profile, or _someday_ a module).


On 1/4/07, Chris Johnson <cxjohnson at gmail.com> wrote:
> In a thread on hook_nodeapi, Jaza wrote:
> "With the new CCK-partially-in-core features, it's likely that before long,
> there will be no such thing as module-defined node types. There will
> only be user-defined node types."
> Either I grossly misunderstand things, or ... the hell you say?
> (American idiom for disbelief or roughly "no way!")
> CCK may be regarded as the greatest thing since sliced bread by users,
> site admins and even many developers, but I may not want to use CCK to
> define nodes when I've got some special data I want to use efficiently
> as content in a module I'm writing.  CCK is inefficient *by design* in
> order to purchase its flexibility.
> Drupal is a framework.  It shouldn't force content creation modules to
> use one and only one method.

More information about the development mailing list