Changes between Version 8 and Version 9 of S3/S3AAA/RecordApproval
- Timestamp:
- 02/01/13 09:50:37 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
S3/S3AAA/RecordApproval
v8 v9 107 107 '''Note:''' For security reasons, both ''approve'' and ''reject'' via CRUD are only possible as POST requests which include the respective form keys from the ''review'' of a record. 108 108 == Callbacks == 109 110 109 For both, resource.approve() and resource.reject(), there are hooks which will be called for each record that gets approved/rejected: 111 112 110 {{{ 113 111 s3db.configure(tablename, onapprove=function) … … 116 114 117 115 The hook function must table {{{(table, row)}}} as parameter, and doesn't return anything. 116 117 == Imports == 118 Imported data is assumed to be approved by the default approver. 119 120 If you wish to import unapproved data then you need to set the attribute {{{@approved=false}}}