Changes between Version 2 and Version 3 of TracPermissionFilterPlugin

Timestamp:

Oct 29, 2011, 6:40:04 AM (13 years ago)

Author:

Sergio Talens-Oliag

Comment:

Added notes about adminmeta

TracPermissionFilterPlugin

@@ -27 +27 @@
     the next permission policy is checked.
 
+If the boolean option `adminmeta` is True the filters are ignored for users
+with TRAC_ADMIN permission.
 
 == Bugs/Feature Requests == 
@@ -66 +68 @@
 }}}
 
-And remember to put the filter the first on your project `permission_policies`:
+The use of the two lists (black and white) makes sense when using inheritance,
+to avoid repeating long lists (i. e., we can have a long whitelist and reduce it only
+in one project using the blacklist).
+
+The plugin has also an additional boolean option called `adminmeta`.
+If this option is set to True (the default) the filters don't affect the users with
+TRAC_ADMIN permission:
+
+{{{
+[permission-filer]
+adminmeta = true
+}}}
+
+If the variable is set to `False` filtering has odd effects on users with
+TRAC_ADMIN permission because we reject based on `action` name and
+TRAC_ADMIN is a meta permission that usually is not checked directly
+
+Lastly, remember to put the filter the first on your project `permission_policies`:
 
 {{{
@@ -72 +91 @@
 permission_policies = PermissionFilter, DefaultPermissionPolicy
 }}}
-
 
 == Recent Changes ==