-
Notifications
You must be signed in to change notification settings - Fork 0
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
admin only fields as filters in list view not working #1470
Comments
@sahalali I'm not sure if this is for you or @AbhishekPAnil to estimate? |
cc @troughc Work needs to be done in both frontend and backend. When used as a filter : Estimate : 10H
|
Backend estimation: 8 Hrs |
@AbhishekPAnil @SyamBabu-M There are no back-end dependencies here. The param should be passed as concept-ids instead of concept in the organization listing page Check this for reference. |
Tested: PASSED |
Tested: everything is working. @SyamBabu-M can you check this? Expected behavior: guests cannot see Admin ONLY fields (for example, members of organizations data) in read only (or the edit form) pages. That field should not be visible to guests because it is an Admin only field. |
UPDATE: this bug is also in production, so it probably pre-existed to this issue. See this organization: https://cms.footlight.io/dashboard/6308ef4a7f771f00431d939a/organizations/6451600fe19f7200646d1fca |
Tested: PASSED |
Tested: PASSED |
Never mind @SyamBabu-M it seems to be working now. |
fix: made custom filters admin only. closes #1470
Admin only taxonomies can be set as filters. these filters appear in the List view and should only be visible to an Admin.
I tested this on Tout Culture with the member of taxonomies - there is one for organizations and one for people.
I was able to set it as a filter: however, it doesn't work (doesn't filter correctly); and, the filter is visible to me when I sign on as a guest.
Expected behaviour: Admin only filters work to filter according to the taxonomy and are only visible to Admins.
Steps:
The text was updated successfully, but these errors were encountered: