Changes between Version 4 and Version 5 of TracDev/PluginDevelopment/ExtensionPoints/trac.perm.IPermissionPolicy

Timestamp:

Jul 28, 2014, 7:56:21 PM (10 years ago)

Author:

Peter Suter

Comment:

Link another mailing list discussion / example

TracDev/PluginDevelopment/ExtensionPoints/trac.perm.IPermissionPolicy

@@ -22 +22 @@
 See [#DebugPolicy], [#PublicWikiPolicy], [#SecurityTicketsPolicy]
 
- * [http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/393/focus=401 Mailing list post] with an example IPermissionPolicy implementation that blocks access to ticket 666. Here an updated version:
+ * [Trac-Dev:393/focus=401 Mailing list post] with an example IPermissionPolicy implementation that blocks access to ticket 666. Here an updated version:
 {{{
 #!python
@@ -38 +38 @@
 }}}
 
- * Another [http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/393/focus=402 mailing list post] with an example IPermissionPolicy implementation based on [h:TagsPlugin]. (Adding a tag 'john:view' on a wiki page or ticket would allow the user 'john' to WIKI_VIEW or TICKET_VIEW that resource. Adding a tag 'john:-view' would disallow it.) Here an updated version:
+ * Another [Trac-Dev:393/focus=402 mailing list post] with an example IPermissionPolicy implementation based on [h:TagsPlugin]. (Adding a tag 'john:view' on a wiki page or ticket would allow the user 'john' to WIKI_VIEW or TICKET_VIEW that resource. Adding a tag 'john:-view' would disallow it.) Here an updated version:
 {{{
 #!python
@@ -70 +70 @@
                 return False
 }}}
+
+
+ * Another [Trac-ML:36200/focus=36220 discussion] involves a special policy checking ticket resolution and recursive permissions tests.
 
 == Available Implementations ==