renewing items not checked out fails unintuitively
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Evergreen Version: 2.3.1 & 2.2.0
This issue was reported by one of our libraries:
======
In version 2.0 if you accidentally did a "Renew" on an item that had never been checked out, you would get an advisory message about that situation that explained why the renew failed.
In version 2.3 if you accidentally run an item that has not been checked out through the "Renew" function, you get an "Unhandled Error" FIXME message that only says "Renew Failed for itemid". (Screen print attached.)
This is a much less helpful result and doesn't give staff useful information about why there was a problem.
Can the old code be restored?
======
I have confirmed this on an Evergreen instance running 2.3.1 & 2.2.0
Debug output from the 2.3.1 version:
==============
Please open a helpdesk ticket and include the following text:
Fri Jan 04 2013 16:20:20 GMT-0500 (Eastern Standard Time)
Renew Failed for 10251189
[
{
"stacktrace"
"ilsevent"
"pid":"4483",
"desc":"Someone attempted to retrieve a user from the system and the user was not found",
"textcode"
"servertime":"Fri Jan 4 16:20:20 2013"
}
]
==============
Changed in evergreen: | |
status: | New → Triaged |
milestone: | none → 2.4.0-alpha |
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → none |
Changed in evergreen: | |
milestone: | none → 2.5.0-m1 |
Changed in evergreen: | |
milestone: | 2.5.0-m2 → 2.5.0-alpha1 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha1 → 2.5.0-alpha2 |
no longer affects: | evergreen/2.2 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha2 → 2.5.0-beta1 |
Changed in evergreen: | |
milestone: | 2.5.0-beta1 → 2.5.0-rc |
Changed in evergreen: | |
milestone: | 2.5.0-rc → none |
no longer affects: | evergreen/2.4 |
no longer affects: | evergreen/2.5 |
collab/ phasefx/ renew_ui_ fix @ working/ Evergreen. git
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/collab/ phasefx/ renew_ui_ fix
commit ca6d11b1305a57d b9254f21680a488 0750b40162
Author: Jason Etheridge <email address hidden>
Date: Wed Jan 9 15:14:27 2013 -0500
lp10962307 renewing items ACTOR_USER_ NOT_FOUND err
This fix simply stops the Skull & Crossbones error dialog from happening when a NOT_FOUND. It doesn't address the fact that CIRCULATION_ NOT_FOUND instead, which is more fathomable by
renewal call results in ACTOR_USER_
we used to get ACTION_
staff.
Signed-off-by: Jason Etheridge <email address hidden>