Drupal Installation Profile Woes
Submitted by Darren on Sun, 17/08/2008 - 22:56.
Most of my work to date has been Drupal 5, but a new project I am involved in has required the switch to Drupal 6. On the whole I couldn't be happier - D6 is really nice in so many areas, and the switch has been pretty painless. Except - I'm now looking at Drupal installation profiles.
A couple of gotchas that I wasn't expecting...
- Don't include any modules that automatically create node types in their module.install file in your installation profile setup. The call to drupal_execute('node_type_form') will try and redirect to 'admin/something/...' which breaks the installation procedure.
- hook_profile_final is no longer available.
I'm still playing around with getting this Drupal installation profile working, and I'll be sure to post the working version when I do!
I'm having similar issues. See http://drupal.org/node/307129#comment-1044176 and http://drupal.org/node/128038#comment-1044119.
If you figure this out, I think a lots of folks will be happy ;-)
Thanks.
(Great feature: Notify me of follow-up comments posted here.)
I'm about to start another port from D5 to D6. This one is a biggie - over 22500 nodes, and lots of users.
I'm trying to avoid using drupal_execute because it's too slow. I'm using node_load() -> serialize() -> node_save() to move content around. There's only a few cases with some CCK fields this doesn't seem to work with.
I'm also making good use of the new batch processing functionality in D6 - a simple API to a really useful bit of functionality... no more script time outs!
Darren,
see http://drupal.org/node/310823 which might be helpful. It's great to get this stuff down to a clean process that respects the Drupal Way if you can ;-)
I hack some of this stuff w/ perl: see what Drupal does, then imitate. Not a great robust solution though, that's why I'm trying to figure out a clean method. I'm just trying to install the CCK types, not move gobs o' data.
Thanx.
Post new comment