[Koha-bugs] [Bug 35559] Can't change the pickup date of holds on the last day of expiration

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Feb 27 23:16:04 CET 2024


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35559

--- Comment #7 from Emily Lamancusa <emily.lamancusa at montgomerycountymd.gov> ---
It looks like this is a regression (or the indirect result of one), and I think
I've tracked down how we got here, but I'm not familiar enough with flatpickr
to submit an alternate patch. Hopefully this will be helpful to someone who is:

1. We had a bug in the past, where a flatpickr with futuredate wouldn't display
the previously input date (e.g. the expiration date on an expired hold) if that
date was in the past. We fixed that in Bug 29241 and its follow-up, Bug 29500.

2. Bug 30718 (Use flatpickr's altInput option everywhere) caused a regression,
and the date field on an expired hold (or any other futuredate field with a
preexisting date in the past) would show as blank again.

3. Bug 34634 fixed the regression by removing the input field and simply
displaying the date if the hold was expired. However, some library staff are
accustomed to extending holds on or after the expiration date is reached, so
this less than ideal for those workflows.

Also, the regression caused by bug 30718 (presumably) still exists for all
other futuredate inputs, besides the holds page. So it would be ideal if we can
fix that underlying regression and allow editing of the dates on expired holds.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list