Project60 / Project60/org.project60.banking
delete permission
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 22
- Forks
- 45
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 7
Description
To delete a payment in CiviBanking, you need the 'administer CiviCRM' permission.
Here is the line of code for it: line 61
It's a very broad permission. Is there any objection to using the existing 'CiviContribute: delete in CiviContribute' permission instead? That would be more specific.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at CRM/Banking/Page/Payments.php line 61 and review the current delete permission alongside the existing CiviContribute permission named in the issue. Confirm the intended authorization behavior with project maintainers; done means the delete action uses the agreed narrower permission and its access behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, payments
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100