HOLD_ITEM_CHECKED_OUT displayed instead of a user oriented message

Bug #1012237 reported by Bob Wicksall
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Low
Unassigned
2.3
Fix Released
Undecided
Unassigned
2.4
Fix Released
Undecided
Unassigned

Bug Description

Evergreen 2.2 RC 1
Tpac

If a patron tries to place a hold on an item that they already have checked out they get the following message:

   Hold was not successfully placed
   Problem: HOLD_ITEM_CHECKED_OUT

All of the other messages seem to have been translated into something a little more friendly. Looks like this one was missed.

Revision history for this message
Michael Peters (mrpeters) wrote :

Perhaps we need to add a new ils_events.xml entry for HOLD_ITEM_CHECKED_OUT, similar to that of "ITEM_NOT_HOLDABLE"

        <event code='1220' textcode='ITEM_NOT_HOLDABLE'>
                <desc xml:lang="en-US">A copy with a remote circulating library (circ_lib) was encountered</desc>
        </event>

Simply stating the event code, followed by a user-friendly error message would seem to suffice.

    "Problem: HOLD_ITEM_CHECKED_OUT - The item you have attempted to hold is already checked out to you."

I'm not sure if there is additional work to be done beyond creating a new event code, however. Seems like a valid "bitesize" bug, though.

tags: added: error events ils message tpac
Changed in evergreen:
status: New → Confirmed
importance: Undecided → Low
Galen Charlton (gmc)
tags: added: bitesize
Revision history for this message
Garry Collum (gcollum) wrote :

Fix in user/gcollum/lp1012237_HOLD_ITEM_CHECKED_OUT_display

tags: added: pullrequest
Revision history for this message
Lebbeous Fogle-Weekley (lebbeous) wrote :

Thanks Garry! This is now in master, rel_2_4, and rel_2_3.

Changed in evergreen:
status: Confirmed → Fix Committed
milestone: none → 2.5.1
Ben Shum (bshum)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.