Changes between Version 57 and Version 58 of S3/S3AAA/OrgAuth

Timestamp:

06/13/14 12:02:33 (10 years ago)

Author:

MattS

Comment:

syntax highlighting

S3/S3AAA/OrgAuth

@@ -11 +11 @@
 Person entity types implement the pr_pentity super-entity:
 
-{{{
+{{{#!python
         table = define_table(tablename,
                              super_link("pe_id", "pr_pentity"),
@@ -23 +23 @@
 To retrieve the person entity ID (pe_id) of any instance record, you can use:
 
-{{{
+{{{#!python
     pe_id = s3db.pr_get_pe_id(tablename, record_id)
 }}}
@@ -47 +47 @@
 Where the realm entity can be determined from the record itself, you may wish it to be updated along with changes in the record. In this case, you can set the '''update_realm''' setting for the table to {{{True}}}:
 
-{{{
+{{{#!python
     s3db.configure(tablename,
                    update_realm=True)
@@ -54 +54 @@
 Realm entity updates will propagate to all components listed under the '''realm_components''' setting:
 
-{{{
+{{{#!python
     s3db.configure(tablename,
                    update_realm=True,
@@ -64 +64 @@
 ==== 1. 'Global 'auth.realm_entity''' function: ====
 It is possible to set a global method for the realm_entity hook in the config.py of the respective template:
-{{{
+{{{#!python
 settings.auth.realm_entity = function
 }}}
@@ -71 +71 @@
 If the function returns {{{0}}}, then set_record_owner will fall back to the table-specific realm_entity setting.
 ==== 2. Table '''realm_entity''' function: ====
-{{{
+{{{#!python
 s3db.configure(tablename,
                realm_entity = function_or_lambda)
@@ -113 +113 @@
 To check which realms a role of the current user applies for, you can access:
 
-{{{
+{{{#!python
     realms = current.auth.user.realms[role]
 }}}