Quote Originally Posted by JmZ View Post
Hooks exist for you to implement such features.

You can make the update thing by hooking to the admin content, e.g. make an updateCheck page which loops through Core::load()->getModules() and checks each for an update method.

Example:.....
OK I know you can do that but it would be really cool if at least the install one was in by default. I remember with IPB 2.3 that you had to install a Plugin Manager first in order to be able to install and configure lots of modules. Most wouldn't work on their own. I know I could create a Plugin Manager like what the early IPB had to offer the install, uninstall, update options but I think it would be better if at least the install options were in by default.

Just do a config bit in the list modules that searches for the function eg configMyMod, as from that we can offer the other install/uninstall/update options/settings/whatever. It will only be 10-12 extra lines of code for you to have in the default script.

Let's be honest. At the moment list modules is sorta pointless. If you add the config link (if configMyMod function exists) it would give the whole area purpose and get rid of all those custom install files and other bloated crap that can come with modules.

OFFTOPIC:
Desperately disappointing that this is the only topic on KWWH in the last week (probably longer) that has interested me in any way.
Mr Happy Reviewed by Mr Happy on . Official: WCDDL - The DDL Script Here's a big summary thread for you guys, ill try keep it up-to-date. http://warezcoders.com/images/logo.jpg What is it? I don't need a huge description here. If you're reading this thread you likely already know what WCDDL is. WCDDL is a DDL script, created to act as a base to DDL sites which can easily be modified to your needs and runs efficiently with minimal 'bloat'. It is very secure and handles high traffic well, while keeping the database size reasonable. Who made it? Rating: 5