From 80c9cf9676b49c07efcc2e00666c975846f83216 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 follow-up) - Rename _ShiftPriorityByDateAndPriority to _ShiftPriority Signed-off-by: Jonathan Druart Signed-off-by: Tomas Cohen Arazi (cherry picked from commit 0ca445fca8262ad3a0e2b44c7516417e81532c43) Signed-off-by: Lucas Gass (cherry picked from commit 648c3ad48a530510690ef34d2f918f56fe631a17) Signed-off-by: Arthur Suzuki --- C4/Reserves.pm | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/C4/Reserves.pm b/C4/Reserves.pm index d1e71772a6..5b14a651a2 100644 --- a/C4/Reserves.pm +++ b/C4/Reserves.pm @@ -226,7 +226,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; @@ -1929,9 +1929,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> @@ -1947,7 +1947,7 @@ the sub accounts for that too. =cut -sub _ShiftPriorityByDateAndPriority { +sub _ShiftPriority { my ( $biblio, $new_priority ) = @_; my $dbh = C4::Context->dbh; @@ -2215,7 +2215,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 -- 2.39.5