Fix checking permissions in api3 profile get #16848
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Fixes an apparent bug in api3 code where a boolean value needs to be inverted.
Technical Details
This is confusing so I'm gonna break it down here as much for myself as anyone reading this:
civicrm_api3_profile_get
takes a param calledcheck_permissions
.If true, permissions will be checked.
CRM_Core_BAO_UFGroup::getFields
takes a param called$skipPermission
.If true, permissions will not be checked.
$skipPermission
wasempty($params['check_permissions']) ? FALSE : TRUE
.That's a confusing way of saying
a = a
; the value stays the same.Comments
Whew! Brain hurts.