X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/f484deabbcee65721b497fc1d2fb572b4df47988..a407c116260c218e426a1b70945204bd60e7b5b0:/doc/todo/online_configuration.mdwn

diff --git a/doc/todo/online_configuration.mdwn b/doc/todo/online_configuration.mdwn
index 2393b75af..02a8c6e5f 100644
--- a/doc/todo/online_configuration.mdwn
+++ b/doc/todo/online_configuration.mdwn
@@ -7,12 +7,6 @@ In theory, every setting could be configured there. In practice, some
 settings, like `srcdir` and `destdir` are ones you want to keep far away
 from editing via the web.
 
-Currently admin prefs are per-admin, and are stored in the userdb.
-That seems like a bad choice in the context of this idea. Instead, admin
-setup should be configured on a separate page than the regular user prefs
-page, and should be shared amoung all admins, and the ideal storage would be
-a ikiwiki setup file, which could be loaded in, and written back out.
-
 The underlying work has been done to privide metadata about all options via
 getsetup hooks, so it's just a matter of writing a web interface plugin.
 
@@ -22,10 +16,13 @@ The plugin could have these config options:
 	websetup_include => [qw{safe}],
 	# list of options to exclude from web setup
 	websetup_exclude => [qw{option_baz}],
+	# list of plugins that cannot be enabled/disabled via the web
+	# interface
+	websetup_force_plugins => [qw{git svn bzr mercurial monotone tla}]
 
 Leaning toward just making it write out to the same setup file, rather than
 writing to a subsidiary setup file. However, this would mean that any
 comments in the file would be lost, and that it couldn't be used if the
 setup file had weird stuff (perl code, etc).
 
-[[!tag wishlist]]
+[[!tag wishlist done]]