| Summary: | Enhancement: ability to deny some patrons password resets | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Chris Cormack <chris> |
| Component: | Patrons | Assignee: | MJ Ray (software.coop) <mjr> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Bugs List <koha-bugs> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | gmcharlt, tomascohen, veron |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://opac/cgi-bin/koha/opac-passwd.pl | ||
| See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10796 | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Chris Cormack
2010-05-21 01:05:36 UTC
I wonder if a pre-configured patron attribute would work in this case? Something like the SHOW_BCODE authorized value? Hm, I have started working on this, but will not be able to finish before the deadlines for 3.14. I am using a new column in categories, so tying it to the patron category. (bug 10796) |