CiviCRM Community Forums (archive)

I recently hit a situation where there was a UI configured ACL and a hook ACL whereClause granting permissions to a person.

It seems the hook example doesn't cover this & assumes the ACL replaces the existing permission. This isn't hugely consistent with the way ACLs are applied - ie. you have permission to see no-one. Then you get to see anyone that any of your  ACLs gives you permission to see.


http://wiki.civicrm.org/confluence/display/CRMDOC43/hook_civicrm_aclWhereClause

I wound up using this logic
  if(!empty($where)){
    $originalWhere = $where;
  }
  $clause = 'contact_id IN (1,2,3)';
  $where = implode(' OR ', $clause);
  if($originalWhere){
    $where = "( $originalWhere OR $where )";
  }
I had expected that this wouldn't need to be repeated in every implementation - but perhaps the only gap is documenting the possible logic options (how to code for 'AND', 'OR' & 'Instead').