You'll still need to have a LocalSettings.php for at least a few settings, such as those for $wgDBserver, $wgDBname, $wgDBuser, and $wgDBpass, plus whatever settings are needed by the scripts to read data from the db. Otherwise you'll have a chicken-and-egg problem of not knowing how to actually read your preferences out of the database. -Nick Ashar Voultoiz wrote:

JeLuF wrote: Lo JeLuF, Probably better to get one row per setting, that will allow us to sort settings per categories and define the type of data. Ex: category | setting | value | type --------------------------------------------- General | ScriptPath | | string General | UploadDir | /mnt/upload | string Tidy | UseTidy | 0 | boolean --------------------------------------------- Then we can get different administrations pages. For older versions, we probably just want to diff changes and saves them directly in the new log system. I will be out till october ... :( cheers, -- Ashar Voultoiz

I am very happy to see the progress you guys have made so far! Thank you very much for your good work! On Tue, 14 Sep 2004 19:46:36 +0200, Jens Frank <jeluf(a)gmx.de> wrote: -- Be good....

On Wed, Sep 15, 2004 at 03:08:00AM +0200, Erik Moeller wrote: The existing explanations, if they are good, are to verbose for the admin interface. I thought about having a help button per page or even per option. Per page would allow having an introduction providing some overall picture, e.g. for memcached, there has to be a discussion in the help explaining what memcached is for and who should use it and where to get it. This I wouldn't want to see as part of the site settings page itself, but in a help page. Regards, JeLuF