https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26129
--- Comment #7 from Tomás Cohen Arazi <[email protected]> --- The idea is that we have many places in which we define global configurations (sysprefs) and then override it somewhere, locally (e.g. min password length on category config). In that case, if we wanted to have a screen for managing this with a tree like structure, maybe handling all password-related configs globally or per-library or per-category, a-la circulation rules, we would benefit from this simple design and it would set a clear path forward. On bug 19889 we clearly added many configurations, in different places, and while it has the flexibility that is required, and we can give pointers to the end-user, it is clear that having a single page to manage all related things, was pointed out by the requestor as something valuable. And this generic approach on the DB might be the best way to store this. Even if we don't migrate all sysprefs into this. That said, I moved forward with an smtp_servers table and won't be back to this unless there's some interest. It felt like the right thing to do, though. -- 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/
