From f9c5782255ffc9fbb022e48bf1cbb07b1bd257e1 Mon Sep 17 00:00:00 2001 From: Kyle M Hall Date: Mon, 25 Aug 2014 10:17:28 -0400 Subject: [PATCH] Bug 12630 [QA Followup] - Rename _ShiftPriorityByDateAndPriority to _ShiftPriority --- C4/Reserves.pm | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/C4/Reserves.pm b/C4/Reserves.pm index 779f554..412166f 100644 --- a/C4/Reserves.pm +++ b/C4/Reserves.pm @@ -163,7 +163,7 @@ sub AddReserve { } if ( C4::Context->preference( 'AllowHoldDateInFuture' ) ) { # Make room in reserves for this before those of a later reserve date - $priority = _ShiftPriorityByDateAndPriority( $biblionumber, $priority ); + $priority = _ShiftPriority( $biblionumber, $priority ); } my $waitingdate; @@ -1956,9 +1956,9 @@ sub _koha_notify_reserve { } -=head2 _ShiftPriorityByDateAndPriority +=head2 _ShiftPriority - $new_priority = _ShiftPriorityByDateAndPriority( $biblionumber, $reservedate, $priority ); + $new_priority = _ShiftPriority( $biblionumber, $priority ); This increments the priority of all reserves after the one with either the lowest date after C<$reservedate> @@ -1974,7 +1974,7 @@ the sub accounts for that too. =cut -sub _ShiftPriorityByDateAndPriority { +sub _ShiftPriority { my ( $biblio, $new_priority ) = @_; my $dbh = C4::Context->dbh; @@ -2271,7 +2271,7 @@ priority is based on the set of holds whose start date falls before the parameter value. After calculation of this priority, it is recommended to call -_ShiftPriorityByDateAndPriority. Note that this is currently done in +_ShiftPriority. Note that this is currently done in AddReserves. =cut -- 1.7.2.5