Unnecessary user refresh after deletion can cause permission error
Bug #1244354 reported by
Angela Kilsdonk
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When a user is deleted in the staff client, the home library is set to the top of the consortium. After the delete action, the staff client tries to refresh the account. Within this refresh is a recalculation of standing penalties for the user, which requires the UPDATE_USER permission, if this permission is not set at the Consortium level, “permission denied” error will occur. This is confusing when the staff member performing the deletion does have permission to delete the patrons at the branch or system level.
Version 2.4.2
| Changed in evergreen: | |
| assignee: | nobody → Erica Rohlfs (erohlfs) |
| Changed in evergreen: | |
| assignee: | Erica Rohlfs (erohlfs) → Jason Etheridge (phasefx) |
Revision history for this message
| Jason Etheridge (phasefx) wrote | #2 |
| Changed in evergreen: | |
| status: | New → Fix Committed |
| assignee: | Jason Etheridge (phasefx) → nobody |
| Changed in evergreen: | |
| milestone: | none → 3.0-alpha |
| Changed in evergreen: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This fixes the issue.
http://