In cod_session_features.inc, cod creates a number of content types.

This includes the session content type. For all the types it assigns "features" as the module so that it owns the content types. But features does not seem to need to own the types. Why are these not created more like the core type which are owned by "node" and marked as custom.

I ask, because we want to make session a product but ubercart will not do that since it is not a custom type.

Looking at the code it looks like session could be marked as custom and owned by "node" since I see no special handling by features other than to implement hook_form() which simply calls the node_content_form() function. So I have to wonder, what am missing?

Thanks

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Question on how COD creates content types. » Make COD content types owned by node and "custom"
Category: support » feature

I think this is just the default behavior of the features module and nothing intentional.

Please provide a patch to do what you ask for - if it works in your testing (and others) it's likely to get committed.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (works as designed)

Works As Designed for now as 6.x-1.0 comes out and work focus shifts to 7.x-1.x where this isn't relevant, but if someone can provide a patch (or wants to sponsor the work) then please re-open the issue.