Karen R McArthur wrote:
I have applied the "site_hide_list_options.patch" in order to limit
owner access to the list configurations via the web interface - however,
a side effect of this is that our mailman admin cannot access those
options either. (true, I can export the config, modify the text file
and re-apply the config to the list, but that is very labor intensive...)
You could just run bin/config_list with an input file consisting of
only the setting(s) for the attribute(s) you want to change.
How can I limit the list owners - yet still allow the mailman admin
access to ALL the options via the web?
Assuming you mean the patch at
<
http://sourceforge.net/tracker/index.php?funcÞtail&aid64457&group_id3&atid00103>,
you could try the following modification to the MailList.py part of
the patch. Warning! - untested. The modification is the addition of
two lines immediately following
if value:
Index: trunk/Mailman/MailList.py
==================================================================--- trunk/Mailman/MailList.py (revision 16)
+++ trunk/Mailman/MailList.py (working copy)
@@ -426,6 +426,20 @@
if hasattr(gui, 'GetConfigInfo'):
value = gui.GetConfigInfo(self, category, subcat)
if value:
+ if self.CheckCookie(mm_cfg.AuthSiteAdmin):
+ return value
+ title = None
+ for item in value[1:]:
+ if not isinstance(item, TupleType):
+ if title is not None:
+ value.remove(title)
+ title = item
+ if not isinstance(item, TupleType) or
len(item) < 5:
+ continue
+ if item[0] in mm_cfg.SITE_HIDE_LIST_OPTIONS:
+ value.remove(item)
+ else:
+ title = None
return value
--
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
