Changes between Version 24 and Version 25 of RowLevelPermissions

Timestamp:

Aug 19, 2006, 1:00:21 PM (19 years ago)

Author:

Chris Long

Comment:

--

RowLevelPermissions

@@ -129 +129 @@
 '''Second method using GenericAuthorization will be written after the merge. It will follow the documentation written on GenericAuthorization'''
 
+=== Checking Permissions in a Template ===
+
+In a template, you can use the tag if_has_perm to check for permissions. The tag has the following syntax: 
+{% load auth %}
+{% if_has_perm [not] (permission codename) [object] %}
+...
+{% else %}
+...
+{% end_if_has_perm %}
+The parameters in square brackets are optional and the normal brackets are required. The else statement is optional. The permission codename should be in the format: app_label.codename.
+
+=== Administration ===
+
+You can set up row level permissions to be created automatically by the admin interface when a user creates an object by using the options: grant_change_row_level_perm and grant_delete_row_level_perm. By default these are turned off. An example:
+{{{
+#!python
+...
+class Mineral(models.Model):
+...    
+    class Admin:
+        grant_change_row_level_perm=True
+        grant_delete_row_level_perm=True
+    
+    class Meta:
+        row_level_permissions = True
+...
+}}}
 
 == Implementation Notes ==