I think it would be helpful if the module was either in the CCK or Views fieldset (Views is probably best) on the module admin page.

thanks!

Comments

ndeschildre’s picture

Hmm, a little tricky here.
We have developed around 30 modules that we put all on the same fieldset, AEF. Much easier for us.
But your request is totally valid.
So I'm not sure what to do. Starting to make diffs between the code we use and the code we publish is not that good...

I'll keep this issue open.

David Lesieur’s picture

I'm with rhache with this. Most sites will only use a small subset of the AEF package. The acronym won't help site administrators find a module, and admins will probably wonder what it stands for (I, for instance, don't know what 'AEF' means). It is also unusual for a Drupal module to be packaged by "foundry".

Thanks for contributing this module though!

bonobo’s picture

RE: "So I'm not sure what to do. Starting to make diffs between the code we use and the code we publish is not that good..." -- this is also a completely valid point.

In this specific case, through, we're only talking about adjusting the .info file, though? Still less than ideal, but more contained as it's only one file.

This is also something that could be changed fairly easily by more technically proficient end users --

And with that said, I'm looking forward to doing some testing on some of these modules to see if there are places where they can support our general use case -- in particular, the Utilities/Embedded Edit/Views CCK Formatter/Nodeselect mix looks like something that will be immediately useful in a few places. Thanks for your work/time in releasing this out.