This template is initiating the flatpickr instance from the template file, it should not.
Created attachment 126496 [details] [review] Bug 29270: Remove flatpickr instantiation from request.tt The JS code is only used when placing a hold for club BUT the date inputs are not displayed there. Test plan: Place holds for patrons and clubs and confirm that the two date inputs are working correctly
Created attachment 126680 [details] [review] Bug 29270: Remove flatpickr instantiation from request.tt The JS code is only used when placing a hold for club BUT the date inputs are not displayed there. Test plan: Place holds for patrons and clubs and confirm that the two date inputs are working correctly Signed-off-by: David Nind <david@davidnind.com>
Created attachment 126796 [details] [review] Bug 29270: Remove flatpickr instantiation from request.tt The JS code is only used when placing a hold for club BUT the date inputs are not displayed there. Test plan: Place holds for patrons and clubs and confirm that the two date inputs are working correctly Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Pushed to master for 21.11, thanks to everybody involved!
Created attachment 127706 [details] [review] Bug 29270: Expiration date must be in future
(In reply to Jonathan Druart from comment #5) > Created attachment 127706 [details] [review] [review] > Bug 29270: Expiration date must be in future Pushed to master.
Created attachment 127708 [details] [review] Bug 29270: start_for is actually date_to The attribute has been renamed in the meanwhile..
(In reply to Jonathan Druart from comment #7) > Created attachment 127708 [details] [review] [review] > Bug 29270: start_for is actually date_to > > The attribute has been renamed in the meanwhile.. Pushed to master.