http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11077
--- Comment #10 from M. Tompsett <[email protected]> --- (In reply to Jonathan Druart from comment #9) > I am not sure it is a good idea to suppress the warning caused by an > undefined syspref. This syspref should exist in the DB, else something wrong > happened when updating the DB. Logs must contain this alert. If something went wrong updating the DB, should that not be in the logs already? Suppressing while running in a bad state avoids flooding the logs more. Flooded logs don't get read. TL;DR is a new short form I've come to learn: Too Long; Didn't Read. This means the the less flooded log has a better chance of having someone catch the error and correct it. Just my thoughts. -- 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/
