Changes between Version 18 and Version 19 of RowLevelPermissions

Timestamp:

Aug 6, 2006, 2:54:50 PM (18 years ago)

Author:

Chris Long

Comment:

--

RowLevelPermissions

@@ -90 +90 @@
 }}}
 
-To return the instance of a row level permission use the attribte "type". For example:
+To return the instance of a row level permission use the attribte "model". For example:
 {{{
 #!python
 ...
-object = row_level_permission.type
+object = row_level_permission.model
 ...
 }}}
-''Developer's note: This will most likely change as I'm not too sure "type" accurately describes what it represents. I will update this page when I make the change.''
+''Developer's note: This will most likely change as I'm not too sure "model" accurately describes what it represents. I will update this page when I make the change.''
 
 === Creating a Row Level Permission ===
@@ -128 +128 @@
 === Checking Permissions ===
 
-This will be integrated into the GenericAuthorization SoC project. More info to come.
+In the next week, GenericAuthorization and row level permissions will be merged. Therefore, I have shown two different methods of checking for permissions, one using the generic authorization and the currently implemented technique.
+
+The current method uses the has_perm method in the User model. Note: The object parameter is optional, this is to allow backwards compatibility.
+
+Example:
+{{{
+#!python
+...
+user.has_perm("can_mine", object=mineral)
+...
+}}}
+
+This will return either True or False depending on if the user has the correct permission. It will return false if the user has a negative row level permission on the object. 
+
+This will also check group row level permissions. If the user is in two groups, the first having a positive row level permission and the second having a negative row level permission, it will take the positive row level permission over the negative.
+
+'''Second method using GenericAuthorization will be written after the merger'''
+
 
 == Implementation Notes ==