Bug 35307: Add a hidden input for expired holds

To test:
 1 - Place 3 holds on a bib, each for a different patron
 2 - IN the db, set the first hold to be expired:
    UPDATE reserves SET expirationdate='2023-01-01' WHERE reserve_id=1;
 3 - Refresh the holds page for the biblio
 4 - Note the first hold now says 'Expired' in the expiration date column
 5 - Set an expiration date for the last hold
 6 - Click 'Update holds'
 7 - Note the date is applied to the second hold
 8 - Delete the holds
 9 - Apply patch
10 - Repeat 1-6
11 - Confirm only the correct hold is updated

Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>
(cherry picked from commit ca5378cd94)
Signed-off-by: Frédéric Demians <f.demians@tamil.fr>
This commit is contained in:
Nick Clemens 2023-11-13 16:02:46 +00:00 committed by Frédéric Demians
parent b44fc4918e
commit 4fdfb7e490
1 changed files with 1 additions and 0 deletions

View File

@ -129,6 +129,7 @@
<input type="text" class="flatpickr" data-flatpickr-futuredate="true" value="[% hold.expirationdate | html %]" size="10" name="expirationdate" />
[% ELSE %]
<span class="expiredon"><label>Expired:</label> [% hold.expirationdate | $KohaDates %]</span>
<input type="hidden" value="[% hold.expirationdate | html %]" name="expirationdate" />
[% END %]
</td>
<td>