OPAC: hold can be edited to have an activation date in the past
Bug #1888554 reported by
Galen Charlton
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Medium
|
Unassigned | ||
| 3.5 |
Won't Fix
|
Medium
|
Unassigned | ||
| 3.6 |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
When editing a hold in My Account in the public catalog, a patron can set an activation date that falls in the past, thereby creating a hold that will never reactivate.
This bug is essentially bug 985957 redux: the fix that was supplied for that bug was for the hold placement form only, not the hold editing form.
Evergreen 3.4+
Revision history for this message
| Galen Charlton (gmc) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → 3.5.1 |
| Changed in evergreen: | |
| milestone: | 3.5.1 → 3.5.2 |
| tags: | added: holds |
| Changed in evergreen: | |
| milestone: | 3.5.2 → 3.6.1 |
| Changed in evergreen: | |
| milestone: | 3.6.1 → 3.7-beta |
Revision history for this message
| Michele Morgan (mmorgan) wrote | #2 |
| Changed in evergreen: | |
| milestone: | 3.7-beta → none |
| tags: | added: opac |
| tags: |
added: circ-holds removed: holds |
To post a comment you must log in.
Targeting this to 3.4 or earlier is possible, but would like mean also backporting the fix for 985957.
By the way, the reason why the patch for 985957 doesn't fix the hold editing form that the hold validation Javascript is only active (and currently only works) for the place_hold form.