July 2017 - Koha-bugs - lists.koha-community.org

[Bug 18997] New: Everything listed as "not renewable"
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '17

02 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18997 Bug ID: 18997 Summary: Everything listed as "not renewable" Change sponsored?: --- Product: Koha Version: 17.05 Hardware: PC OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: wyneken(a)physik.uni-freiburg.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I'm running Koha version 17.05.01 on Debian 8.8. All of the items that are checked out are labeled as "Not renewable (0 of 0 renewals remaining)". I've tried changing the settings in "Circulation and fine rules" in several different ways but nothing makes any difference. While researching this problem I've noticed two other mentions of the same thing but neither of them with a real solution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 17249] New: Koha:: AuthorisedValues - Remove GetKohaAuthorisedValuesFromField
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '17

02 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17249 Bug ID: 17249 Summary: Koha::AuthorisedValues - Remove GetKohaAuthorisedValuesFromField Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 18929] New: Merging records mandate 003 and 040 fields though in framework its not mandatory
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '17

01 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18929 Bug ID: 18929 Summary: Merging records mandate 003 and 040 fields though in framework its not mandatory Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: mishravk79(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I am trying to merge two records but system gives alert 003 and 040 fields are missing though i have tried by making it non mandatory (003/040) from default as well as concern records customized framework. Koha 16.11.07 on debian 8. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 18367] New: Fix untranslatable string from Bug 18264
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '17

01 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18367 Bug ID: 18367 Summary: Fix untranslatable string from Bug 18264 Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Bug 18264 added the following line to the .pl file: +my $inumber = $itemnumber ? "(blank) (itemnumber:$itemnumber)" : ""; This blank is untranslatable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 18987] New: When browsing for a patron by last name the page processes indefinitely
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '17

01 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18987 Bug ID: 18987 Summary: When browsing for a patron by last name the page processes indefinitely Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: blocker Priority: P1 - high Component: Patrons Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When browsing for a patron by last name the patron result page processes indefinitely instead of displaying results. This is after browser cache has been cleared. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 18977] New: Rollback branch in t/db_dependent/SIP/Message.t
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '17

01 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18977 Bug ID: 18977 Summary: Rollback branch in t/db_dependent/SIP/Message.t Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Test t/db_dependent/SIP/Message.t generates a Branch via TestBuilder outside $schema->storage->txn_begin and it stays in database when test is over. Move generation inside transaction so that it gets rolled back. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 7172] Omnibus for Plack variable scoping problems
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '17

31 Jul '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7172 Bug 7172 depends on bug 16760, which changed state. Bug 16760 Summary: Circulation Statistics wizard not populating itemtype correctly https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16760 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7172] Omnibus for Plack variable scoping problems
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '17

31 Jul '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7172 Bug 7172 depends on bug 16760, which changed state. Bug 16760 Summary: Circulation Statistics wizard not populating itemtype correctly https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16760 What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 18953] New: Cannot use internal login after ldap failure
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '17

31 Jul '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18953 Bug ID: 18953 Summary: Cannot use internal login after ldap failure Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org When using LDAP (or cas or shiboleth), if the login fails using that method, the system doesn't check the internal user/pw anymore. It just fails the login. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 18424] New: Implement different password strength settings
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '17

31 Jul '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18424 Bug ID: 18424 Summary: Implement different password strength settings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Implement different password strenght settings as a followup to Bug 18298 - Enforce password complexity See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18298#c26 Maybe we could just have different strength settings? Instead of "RequireStrongPassword" we could name this PasswordStrength and then have the current and alphanumeric+digits as first two options. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5