Features integration

This is an interesting problem. content types that are exported with multistep configurations do export the settings for multistep, but don't use those settings once the feature is enabled on a new instance. It appears that this is because those settings are stored separately in drupal variables and not as part of the content type definition. The Multistep module is not sensitive to features and as such does not add those variables for tracking and does not check to see if the content type is already implementing those values.

I guess there are a few possible longer term solutions to this. 1) instead of calling variable_get(), multistep could be modified to use cck's configuration system to store and load the config values, then only look at those keys when implemented. 2) multistep could simply look at the content type first to see if the keys are already defined and use those if they are. or 3) multistep could implement a features hook and add those drupal variables to any feature that is exporting a content type that is multistep enabled.

All of that being said, In the short term all you need to do is use strongarm and manually export the individual multistep_xxx variables that are associated with the content type you've configured, and multistep functionality will work as expected

-Chris