First off, I really like the simplicity of this module, it just does what I need it to.

I would like to see about making the settings variables storage (in the variable table) work better with the strongarm and features module. Let me run through a use case:

1. I create a site and want to capture the components using the features module. I have a content type, several views and panels, all exportable using features.

2. I use the strongarm module to make my variables exportable to my feature.

3. I would like to include the menutrails settings, but only for the node types I export into my feature. Currently menutrails has one entry in the variable table that is an array of all node types.

I propose making each node types menutrails setting it's own record in the variable table. An example of anopther module that does this is the pathauto module.

I also propose making all the settings on a per node basis. So instead of having one Menutrails Menu for all node types, I would like to be able to select the Menutrails Menu per node type. Possibly also the set breadcrumbs setting per node type.

I would be willing to generate a patch for this if anyone else is interested, I just don't want to put in the work if it won't get committed.

Comments

kenorb’s picture

kenorb CreditAttribution: kenorb commented

I think this is reasonable.

sigsby’s picture

sigsby CreditAttribution: sigsby commented
Status: Active » Closed (won't fix)

I posted this over a year ago and did not receive any feedback. I am no longer using this module and therefore have no interest in patching it. I'm closing this with won't fix.