Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev/core#3908 Fix permissions for SubscriptionHistory in SearchKit #24719

Merged
merged 1 commit into from
Oct 15, 2022

Conversation

wmortada
Copy link
Contributor

@wmortada wmortada commented Oct 12, 2022

Overview

Users without 'administer CiviCRM' permission are unable to view data from the SubscriptionHistory entity in SearchKit.

See https://lab.civicrm.org/dev/core/-/issues/3908

Before

User unable to view data.

After

User able to view data.

@civibot
Copy link

civibot bot commented Oct 12, 2022

(Standard links)

@civibot civibot bot added the master label Oct 12, 2022
@wmortada wmortada force-pushed the subscriptionhistorypermission branch from 3137af0 to b8f3878 Compare October 12, 2022 11:22
@wmortada wmortada changed the title [WIP] dev/core#3908 Fix permissions for SubscriptionHistory in SearchKit dev/core#3908 Fix permissions for SubscriptionHistory in SearchKit Oct 12, 2022
@wmortada
Copy link
Contributor Author

@colemanw Ready for review

@wmortada wmortada force-pushed the subscriptionhistorypermission branch 2 times, most recently from 237bbca to c76ec9f Compare October 12, 2022 12:35
@wmortada wmortada force-pushed the subscriptionhistorypermission branch from c76ec9f to 00cadd8 Compare October 12, 2022 18:11
@colemanw
Copy link
Member

All looks good and tests are passing 👍

@colemanw colemanw merged commit 3a36f7e into civicrm:master Oct 15, 2022
@wmortada wmortada deleted the subscriptionhistorypermission branch October 15, 2022 18:38
@wmortada
Copy link
Contributor Author

Thanks @colemanw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants