Thinking of putting the module system back

I know what you mean but some types of modules maybe highly configurable.

It also depends on the application you are building. If you are not using a small non-multi language and only using one template you can cut the files down quite a bit.

I can advertise members as ecommerce experts.

Maybe you and Qphoria would be intreasted.

You can include me in your list, too.

Certainly include me. I got 3 kids to feed!

Daniel, thank you for your comments, they are muchly appreciated (although "thank you" seems to be an understatement). Certainly not the response I was expecting. And, yes, I would be very interested in what you propose.

Qphoria wrote:You are preaching to the choir man! The same thing has annoyed me in 0.x and I've not yet come up with a way of handling it. But perhaps you are on the right track!

The method I've chosen, as you would have seen (I'm assuming you've had a look), removes the need to have individual admin controllers for each module, and replaces them with a "generic" controller. The approach I have taken is only intended to control the modules on the front-end. Administrative modules, like Juergen's "Import/Export" module would have different requirements and are not within the scope of what I'm trying to achieve.

Daniel wrote:... but some types of modules maybe highly configurable.

Good point. Something I hadn't taken into consideration. In these circumstances, there would be a need for administrative components for the module. Maybe with an "Other Options" option (Yes/No) which, if "Yes" would display a link to a controller providing the additional options. I'll look into it.