CCK_Create_Install module
I am looking for some feedback on a module I created recently.
http://drupal.org/project/cck_create_install
On several sites lately I have used cck and views, and usually end up using the cck node types as special node types with supporting modules. The problem is that the cck export module doesn't seem to work very well so it is difficult moving the created cck / taxonomy stuff from the production site to the live site.
CCK_Create_Install solves the problem by generating install code for the cck content type and all of the referenced taxonomy.
It has solved my problems, basically I am just looking for code review / suggestions.
In working with cck and taxonomy I have also run into several wish list for wich I have created patches where applicable like adding view filter support for the email module and hacks when I was pressed for time. Would any body be interested in a cck_taxonomy_checkboxes module/widget for cck_taxonomy_field or a taxonomy_profile / cck taxonomy_profile module?
Ical feed
how does this compare to the deploy module
ok, so without looking at the internals of either, how does the cck_create_install module compare with Greg's deploy module?
http://drupal.org/project/deploy
slides
http://heyrocker.com/drupal/content/drupalcamp-vancouver-staging-deploym...
I'm planning to look at both in the next week or so, so maybe I'll answer my own question.
A quick guess
Just from looking at the slides, it looks like the deploy module uses the content copy module. For me this didn't seem to work. Groups and Taxonomies where not copied. It also looks like deploy requires setting the start sequence from 1 to 1001.
My module just writes the install code for a cck content type and that is it. It does not copy all of the content, just the structure.
It also creates install code for all of the taxonomies reference by the cck node type.
The taxonomies are created using the taxonomy api. The vid's and tid's are created normally and stored to a hash.
When the CCK stuff is being built, this hash is used to update old vid's to the new ones.
The use case for cck_create_install is you want to create a module based on cck for felxibility. Writing all of the cck install code from scratch would be very time consuming.
It appears the the deploy module is more for complete deployment, settings, content, etc.