https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27160
--- Comment #6 from David Cook <[email protected]> --- (In reply to Jonathan Druart from comment #4) > In which situation ReservesMaxPickUpDelay got removed entirely from the DB? A library had applied Bug 8367 to a customized production instance. The patches for that bug removed ReservesMaxPickUpDelay. They then exported their database and tried to load it into a new non-customized Koha 19.11.x instance, and that's where they encountered the issue. I will admit that it's an extreme edge case. -- 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/
