My inclination is that the current model for Configure extension isn't sustainable (manually tracking addition of configuration variables and trying to present a UI for overriding them).
We should start considering migrating most config settings to a queriable configuration database; this can allow new extensions etc to specify their own admin control panel settings requirements, like what we're seeing with the new user preferences. Attention needs to be placed on ability to cleanly specify group defaults (eg, all wiktionaries get this bit, all Wikibooks get that one), and have a couple different permission levels so eg local admins might be able to make some config changes while others are reserved to system administrators. I'll toss up a few spec ideas on the tech blog & wiki... -- brion vibber (brion @ wikimedia.org) El May 4, 2009, a las 7:46, Aryeh Gregor <Simetrical [email protected]> escribió: > On Mon, May 4, 2009 at 10:36 AM, Ilmari Karonen <[email protected]> > wrote: >> Hmm... maybe we could make that setting (and the other upload-related >> ones) part of the install process, and include the checks there. >> Or we >> could go with my earlier idea and just include prominent notices >> saying >> "After modifying LocalSettings.php, go to Special:CheckConfig to make >> sure you've made no mistakes.") > > Or maybe we could encourage people to use Special:Configure, which can > automatically ensure sanity at configuration time. And should be > easier to use, anyway. > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
