> I am trying to write a program that is very modular in > nature & one of the > features I need the user to be able to do is install/uninstall or > enable/disable the module though the interface.
I have, in the past, stored such information in a database. In projects that have need of such functionality I create a modules table and use that to store what information I need - normally that's a path to the module, the name of the config file for that module and any other relevant bits that the project as a whole needs to know about. Then when a page loads it can check for any appropriate modules in the process and deal with them accordingly. CYA, Dave -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
