https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29074
Emmi Takkinen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff --- Comment #5 from Emmi Takkinen <[email protected]> --- (In reply to Emmi Takkinen from comment #4) > (In reply to Marius from comment #3) > > If I don't put the packet, with "DefaultHoldExpirationdate" on the set and > > with DefaultHoldExpirationdatePeriod blank, the reservation expiration date > > remains blank. > > This is odd, without using this patch if DefaultHoldExpirationdatePeriod is > blank, expiration date is set in database but it's not displayed in Koha. > > And even odder, this happens only if syspref dateformat is set as any other > than yyyy-mm-dd. This seems like an whole other bug to me. This happanes because expiration date input has attribute 'data-flatpickr-futuredate="true"'. When this is set, expiration dates set as today or in the past aren't displayed. Which can now happen if "DefaultHoldExpirationdate" is enabled and "DefaultHoldExpirationdatePeriod" is blank. Setting this bug back to "Needs Signoff". -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
