[development] The future of hook_node_info()

David Cohen drupal at dave-cohen.com
Fri May 22 03:56:42 UTC 2009

On Thu, 21 May 2009 17:26 +0200, "Daniel F. Kudwien"
<news at unleashedmind.com> wrote:
> There are many, many, many modules in contrib that could and would very
> happily use "nodes" as storage type and for processing (i.e. load,
> load_multiple, view, edit, insert, update, delete, *_multiple, + being
> fieldable).  

Drupal for Facebook (http://drupal.org/project/fb) does just this.  It
supports any number of Facebook Apps, and any number of Feed Templates. 
So for these two things it defines custom content types.  This beats
writing all the CRUD functionality all over again.  Also, additional
modules add features, and they use hook_form_alter and hook_nodeapi to
add properties to these content types.

> But they can't, because we still have a lot of magic
> happening
> around nodes:
> - Nodes appear on admin/content/node
> - Nodes appear in search results
> - Nodes appear on node/add
> - Aforementioned default access permissions
> - Possibly more.

None of these is a deal-breaker for my purposes.  They can even be
viewed as advantages.
I may be old-school, but I like the original content type API.  I'd hate
to see it go away.


More information about the development mailing list