>>>>> "OX" == Oliver Xymoron <firstname.lastname@example.org> writes:
OX> The MJ2 way to do it is probably to allow the site owner to upload
OX> modules to GLOBAL somewhere that are automatically 'use'd. Neat, but
OX> also kindof scary.
That would be just too insecure. I'll just have one file that Mj2 pulls in
when it starts up that can contain all of the local hacks, define new
config variables, add additional commands, etc. I see no way to make this
remotely maintainable and I can't possibly imagine how you could make it
both secure and useful at the same time.
The idea is to provide a standardized way for a site owner to add new
functionality without having to patch the heck out of the code (or even to