http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267
Jonathan Druart <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |m --- Comment #3 from Jonathan Druart <[email protected]> --- (In reply to Galen Charlton from comment #2) > (In reply to Katrin Fischer from comment #1) > > Hi Joy, I am not sure if that was the purpose of the field. The way someone > > explained it to me in the past was, that it allows you to store a password > > for another application. > > Actually, Joy's right - the original intent was to support secondary logins. http://lists.koha-community.org/pipermail/koha-patches/2008-May/000988.html - password_allowed (if set, staff patron editor will allow a password to be associated with a value; this is mostly a hook for functionality to be implemented in the future. Does it mean we should keep it or the feature won't never be implemented and we can remove the 2 columns in DB? -- You are receiving this mail because: You are the assignee for the bug. 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/
