Hi Chad,
I agree it would be better to have this option as a default, however it's a
question if it should be hardcoded in mediawiki, or if it should be an
extension, which is preinstalled in mediawiki download package and can be
disabled anytime if users wouldn't like it.
I mean, if it was hardcoded, would it be possible to turn it off / use the
current way of config management which is more friendly for large mediawiki
installations and has better security than gui?
On Tue, Feb 7, 2012 at 4:24 PM, Chad <innocentkiller(a)gmail.com> wrote:
On Tue, Feb 7, 2012 at 9:59 AM, Petr Bena
<benapetr(a)gmail.com> wrote:
I think it would be best if it was possible to
hook the function for
config
load or overwrite whole class for config so that
it's possible to create
an
extension which could change whole storage for
configuration.
The work I plan on doing plans to support multiple backends so you
can put it in CSV files if you really feel bold.
In that case we wouldn't need to change
anything, the standard version
would use a file, and tweaked version would have a gui.
Flip that around, we'd like to have a config gui shipped by default. As
long as you use a backend that utilizes something human-readable,
there's no reason you couldn't also edit the file by hand.
-Chad
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l