Bug 34155: Hide 'Next available' at OPAC when item-level hold is forced
This was a regression caused by bug 24860
Test plan:
1. Set up circulation rules so that OPAC users can place holds only on
specific items ("OPAC item level holds" = "force")
2. Try to place a hold at OPAC. The "Next available item" option should
not appear.
3. Set "OPAC item level holds" to "allow"
4. Try to place a hold at OPAC. The "Next available item" option should
appear
Signed-off-by: Owen Leonard <oleonard@myacpl.org>
Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
(cherry picked from commit 9b1bd01a42
)
Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com>
This commit is contained in:
parent
741f331e7d
commit
9916e18534
1 changed files with 1 additions and 1 deletions
|
@ -340,7 +340,7 @@
|
|||
[% IF bibitemloo.itemholdable %]
|
||||
<!-- ITEM HOLDS -->
|
||||
<li class="lradio place_on_type" style="display:none;">
|
||||
[% UNLESS bibitemloo.forced_hold_level == 'item' || bibitemloo.forced_hold_level == 'item_group' %]
|
||||
[% UNLESS bibitemloo.forced_hold_level == 'item' || bibitemloo.forced_hold_level == 'item_group' || bibitemloo.force_hold %]
|
||||
<label class="radio inline" for="reqany_[% bibitemloo.biblionumber | html %]">Next available item</label>
|
||||
<input type="radio" name="reqtype_[% bibitemloo.biblionumber | html %]"
|
||||
id="reqany_[% bibitemloo.biblionumber | html %]"
|
||||
|
|
Loading…
Reference in a new issue