Bug 21495: Regression in hold override functionality
authorKyle M Hall <kyle@bywatersolutions.com>
Thu, 15 Nov 2018 13:35:33 +0000 (08:35 -0500)
committerNick Clemens <nick@bywatersolutions.com>
Mon, 28 Jan 2019 18:52:13 +0000 (18:52 +0000)
The changes caused by the patches for bug 11512 have broken existing
workflows for many libraries and are widely considered to be a bad move.
We should revert this behavior.

Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Signed-off-by: Rhonda Kuiper <kuiper@roundrocktexas.gov>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/circulation.pref
reserve/request.pl

index 32448b6..2d80bdd 100644 (file)
@@ -582,7 +582,7 @@ Circulation:
               choices:
                   yes: Allow
                   no: "Don't allow"
-            - staff to force addition of holds even if the patron already has the maximum number of holds allowed.
+            - staff to override hold policies when placing holds.
         -
             - pref: AllowHoldsOnDamagedItems
               choices:
index 2534fe2..91b6ffd 100755 (executable)
@@ -490,7 +490,7 @@ foreach my $biblionumber (@biblionumbers) {
 
                     push( @available_itemtypes, $item->{itype} );
                 }
-                elsif ( $can_item_be_reserved->{status} eq 'tooManyReserves' && C4::Context->preference('AllowHoldPolicyOverride') ) {
+                elsif ( C4::Context->preference('AllowHoldPolicyOverride') ) {
                     # If AllowHoldPolicyOverride is set, it should override EVERY restriction, not just branch item rules
                     $item->{override} = 1;
                     $num_override++;