[Koha-bugs] [Bug 32702] Item statuses that block holds should be checked in CanItemBeReserved
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Fri Oct 13 21:32:03 CEST 2023
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32702
Nick Clemens <nick at bywatersolutions.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.koha-community
| |.org/bugzilla3/show_bug.cgi
| |?id=35053
--- Comment #10 from Nick Clemens <nick at bywatersolutions.com> ---
(In reply to Andrew Fuerste-Henry from comment #7)
> (In reply to Nick Clemens from comment #4)
> With these patches applied, I was able to create holds via API for all of
> these items, despite their statuses. I did get blocked from placing holds
> beyond the holds-per-record limit in the circ rules, but otherwise
> everything was permitted.
See bug 35053 - if you only pas the item_id to the API it should work correctly
>
> Also, after the patches, in the staff client the lost and withdrawn items
> are showing new wording in the first column of the item selection table when
> placing a hold.
Added values to the template to handle new values
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list