The API trigger onAfterUserApproval fires when a user is set to approved (green tick) in the CB User Manager, however it appears not to fire when set to unapproved (red X) also from CB User Manager. This seems odd, not least because the API passes a parameter $approved which indicates not-approved, approved or unapproved. Furthermore this behaviour seems to be inconsistent with the operation of onBeforeUserBlocking which fires both on block and unblock also from the CB User Manager and which passes a parameter $actionValue indicating a change to blocked or unblocked.
I wonder whether onAfterUserApproval could be altered to fire whenever approval is changed, rather than just on change to approved? It seems like such a change ought to be backwards compatible, so long as $approved is currently processed correctly by all users of the trigger. Alternatively, is there another way to get a trigger on change from approved to unapproved in the CB User Manager?
Julian
Post edited by: krileon, at: 2010/11/04 19:07