http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8484
Galen Charlton <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |In Discussion CC| |[email protected] --- Comment #22 from Galen Charlton <[email protected]> --- (In reply to Katrin Fischer from comment #21) > I agree that removing the option could cause problems. Why not change the > behaviour so the switch can overwrite the system preference? Or would that > cause problems? I'm pondering this. Since the new system preference defaults to ON, folks used to running longoverdue.pl without the --mark-returned switch (and not just used to it, but who explicitly do *not* want loans to be checked in when the item is marked lost) would be in for a surprise. And since this entails circulation and money, it would be the sort of surprise where a positive response to "you should have read the release notes first" is ... unlikely. To toss out an idea, maybe make the default value (on upgrade) of WhenLostReturnItems be NULL, then add some code to make the staff client header area display a complaint until the system preferences is set to a specific value? And maybe make longoverdue.pl continue to keep its old behavior if the system preference is NULL? This is would all be rather crufty, I know, but overdue and lost item processing is definitely an area where Read the Fine Release Notes doesn't fly. Also, it's not clear to me whether ON or OFF is the better default value for WhenLostReturnItems. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
