|
I find what seems to be two different approaches for creating fields
for a custom content type via a module. One is from drewish, where
the field is first added via cck manually, then dumped with
var_export(content_fields()) and then added to the content type in
the install via content_field_instance_create(). The other is in
rfay's Example module, where Randy creates a table for the module in
the install and inserts fields into it that are what cck would
insert. I'm wondering if the latter removes the need for me to do all the node processing from my module. Also, my content type has one field (other than title and body) which is an image filefield with unlimited instances, and I'm thinking that that same method would have the field being handled by filefield and that the method in Example would require that I manage the _fid, _list and _data db content, etc., so if there's a reason why this would be a better way to do it, or why the first method wouldn't be, I'm missing it. Jeff --
|
Ayen Designs
- [development] D6 Programmatic creation of a custom content typ... jeff
