| Summary: | System preference 'insecure' shows wrong value after update to v3.10 | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Fred P <fred.pierre> |
| Component: | System Administration | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | gmcharlt, ztajoli |
| Version: | 3.10 | ||
| Hardware: | All | ||
| OS: | All | ||
| 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
Fred P
2013-02-06 22:25:31 UTC
In discussing this with other Koha administrators, this might be a legacy data issue. As early adopters of Koha we sometimes see issues with legacy data. If it is simple to add a fix to the update script, then it might help other users like us I'll try to figure out the coding, but something to the effect of: Check insecure setting. If systempreferences.insecure is "NO" change to zero '0' |