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

[Bug 18316] New: Add weighting/relevancy options to ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18316 Bug ID: 18316 Summary: Add weighting/relevancy options to ElasticSearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 167

[Bug 16116] New: Change of issue publication date doesn't reflect on the next issue generated
by bugzilla-daemon＠bugs.koha-community.org 11 May '22

11 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16116 Bug ID: 16116 Summary: Change of issue publication date doesn't reflect on the next issue generated Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com I noticed in 3.20, but also in master, that you can't change the next issue publication date when editing a serial subscription anymore. And, that we lost a feature I liked when receiving a new issue. Before 3.20, when receiving a new issue, you could change the "Published on" date and Koha will adjust the subscription's next issue publication date for all the new issues to be received. Test plan : 1. In Cataloging > New with Z39.50, look for issn = 1536-6596 (National Geographic) into the LCC z39.60 server. Add the record. 2. Add a new subscription for National Geographic. Fill-in the form. - use the default values of the first page - for the second page : First issue publication date = 10/01/2016 Frequency = 1/month Subscription lenght = 12 issues Subscription start date = 01/01/2016 Numbering pattern = Number Begins with = 1 - Save 3. Receive the first issue. Change the status to "received". Note that the "Published on" date = 10/01/2016. This date goes to the "Date published" column in the serial collection page. 4. The second issue is generated. Edit serial to receive the issue. 5. Change the "Published on" date to 11/02/2016. Change the status to "received". Save. 6. "Date published" for the next issue generated is : 10/03/2016. Before 3.20, it would have been "11/03/2016". It was a shortcut to change the Next issue publication date from the subscription. 7. Edit the subscription. Change the "Next issue publication date" to : 11/03/2016. 8. Go back to the serial collection page. Date published for the last expected issue = 11/03/2016 9. Receive the issue. Change the status to "received". Save 10. The next issue generated is 10/04/2016. It should have been 11/04/2016. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 17724] New: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17724 Bug ID: 17724 Summary: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To test: - Make sure your 952$o (callnumber) is linked to a plugin such as cn_browser.pl in your frameworks - Create a subscription with "create item on receive" and a callnumber - Receive an issue - Verify that the callnumber is not copied into the item on receive - Remove the plugin from the framework - Verify that the callnumber now is copied into the item on receive -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 19470] New: Add information about item being in rotating collection on detail page
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '22

26 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19470 Bug ID: 19470 Summary: Add information about item being in rotating collection on detail page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 18606] New: Move rotating collections code to Koha::Object
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '22

26 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18606 Bug ID: 18606 Summary: Move rotating collections code to Koha::Object Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 182

[Bug 19886] New: Two Factor Authentication: Yubikey
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19886 Bug ID: 19886 Summary: Two Factor Authentication: Yubikey Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We need to add support for Two Factor Authentication, because password isn't enough against hackers or unathorised acess. Yubikey is USB hardware FIDO U2F Secure Static Passwords smart card (PIV) Yubico OTP Code Signing OpenPGP OATH-TOTP OATH-HOTP Challenge-Response https://www.yubico.com/product/yubikey-4-series/ Yubikey Perl support https://developers.yubico.com/yubico-perl-client/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 19887] New: Two Factor Authentication: Google Authenticator
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19887 Bug ID: 19887 Summary: Two Factor Authentication: Google Authenticator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Easy two-factor solution for users with smartphones. Google Authenticator and Perl: https://blog.darkpan.com/article/6/Perl-and-Google-Authenticator.html https://debian-administration.org/article/729/Implementing_two_factor_authe… https://github.com/j256/perl-two-factor-auth -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 17018] New: Split AdvancedSearchTypes for staff and OPAC
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '22

15 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17018 Bug ID: 17018 Summary: Split AdvancedSearchTypes for staff and OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if you could configure AdvancedSearchTypes differently for staff and opac advanced search. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 17720] New: CSRF token is not generated correctly
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '22

11 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17720 Bug ID: 17720 Summary: CSRF token is not generated correctly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: blocker 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 The CSRF token is not generated correctly if the DB password contain unicode characters. Indeed md5_base64 explodes with Wide character in subroutine entry at /usr/share/perl5/Digest/HMAC.pm line 63. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 17830] New: CSRF token is not generated correctly (bis)
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '22

11 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17830 Bug ID: 17830 Summary: CSRF token is not generated correctly (bis) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: blocker 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 The same error as bug 17720 can occur if the userid has unicode characters. Wide character in subroutine entry at /usr/share/perl5/Digest/HMAC.pm line 63. -- You are receiving this mail because: You are watching all bug changes.

1 15