January 2022 - Koha-bugs - lists.koha-community.org

[Bug 25879] New: Border for guarantor is larger than the container
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '22

23 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25879 Bug ID: 25879 Summary: Border for guarantor is larger than the container Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 106311 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106311&action=e… Screenshot showing the guarantor section of the patron add form I noticed that the soft blue border that surrounds a guarantor's information in the patron form is slightly larger than the containing box. To reproduce: 1- Add a patron 2- In guarantor information, search for and add a guarantor 3- Notice that the border surrounding the guarantor is larger than the box for guarantor information -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 20384] New: Elastic rebuild script improvements - options for indexing
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20384 Bug ID: 20384 Summary: Elastic rebuild script improvements - options for indexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire.hernandez(a)biblibre.com I would be glad to use the rebuild script with some more options like: -n 100 index 100 first records -n "100,2" index 2 records after 100th (101 and 102) --from XXX index biblio with biblionumber >= XXX --to YYY index biblio with biblionumber <= YYY bonus: -i gives elastic install information: syspref, numbers of biblios/auth indexed, name of indice used etc. There is maybe an other way to name the options. Advice or opinion or objection on how to do this ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 28747] New: Clarify wording on RestrictionBlockRenewing syspref
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28747 Bug ID: 28747 Summary: Clarify wording on RestrictionBlockRenewing syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When RestrictionBlockRenewing is set to Allow, it only allows renewal via the intranet. The wording on the syspref does not make this clear. It says: If a patron is restricted, (allow/block) renewing of items. We should amend it to: If a patron is restricted, (allow/block) renewing of items from the staff interface. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 28430] New: Typo: ... that are not alreay in your...
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28430 Bug ID: 28430 Summary: Typo: ... that are not alreay in your... Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Keywords: Academy, Manual Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org ../../source/tools.rst:3096 (Manual for 20.11) Ignore incoming record: choose this if you don't want to import records that are not alreay in your catalogue (for example, if you're only replacing existing records and don't want to add anything) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 28153] New: Add 'Hold reminder' messaging preference
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28153 Bug ID: 28153 Summary: Add 'Hold reminder' messaging preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org 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. You are the assignee for the bug.

1 30

[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 21494] New: No checkin notice created for offline circulation checkins
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21494 Bug ID: 21494 Summary: No checkin notice created for offline circulation checkins Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the KOCT plugin for offline circulation, checkout notices are created correctly, but checkin notices are no longer created. To test: - Check out an item via KOCT - Send to Koha and process it there - Verify that the checkout is on the account and a checkout notice has been generated - Check in the item via KOCT - Send to Koha and process it there - Verify that the item is no longer on the account but NO checkin notice has been generated This is quite a problem for libraries using the offline circulation plugin as they rely on the emails to inform the patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 25977] New: Koha Offline Circulation tool to handle trigger for sending necessary notices after successful .koc upload
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25977 Bug ID: 25977 Summary: Koha Offline Circulation tool to handle trigger for sending necessary notices after successful .koc upload Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The Koha Offline Circulation tool(s) does not trigger Notices after a successful .koc file upload. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[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 29893] New: ElasticSearch Config UI deletes mappings
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29893 Bug ID: 29893 Summary: ElasticSearch Config UI deletes mappings Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at When using the Elasticsearch UI /cgi-bin/koha/admin/searchengine/elasticsearch/mappings.pl to edit search mappings one can quite easily delete a lot of mappings by mistake. To reproduce: * go to /cgi-bin/koha/admin/searchengine/elasticsearch/mappings.pl * click on the "Authorities" Tab * You should see ~ "67 entries" * enter "Heading-Main" into the search field, you now see ~8 entries ("filtered from 67 entries" * Click "save" Button * Go again to the "Autorities" Tab * You now see ~ "8 entries" * All the other entries have been deleted! What obviously happens is that all entries that where filtered due to the search are not submitted to the backend on save. The backend now interprets the missing entries as entries that shall be deleted. And happily deleted them! This totally breaks the search index (after the next index run, or when adding single items), as (eg in the auth-index) "authtype" is no longer indexed. I currently don't have a 21.11 or later version at hand, so maybe this has already been fixed? To fix this bug we would either have to un-hide the filtered entries before submitting the form; change the backend to not deleted missing entries (which means that the delete-action would have to be implemented a bit different); something else? I guess that the first fix is easier, and would also make sense with regard to how that form works. Greetings, domm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40