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

[Bug 35110] New: Authorities editor with JS error when only one tab
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35110 Bug ID: 35110 Summary: Authorities editor with JS error when only one tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Exactly like Bug 34251 for biblios : When using the an authorities framework with all fields in the same tab, there is thrown a JS error in selectTab( "#tab0XX_panel" ); This is because no nav tabs are build in authorities/authorities.tt as BIG_LOOP has a length(size) of 1 -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 29836] New: 2FA - provide a REST API challenge route
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29836 Bug ID: 29836 Summary: 2FA - provide a REST API challenge route Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Depends on: 28786 We need a challenge route that will take the TOTP and generate a token (JWT?) in case of success. This token will be passed in the header of the other requests. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28786 [Bug 28786] Two-factor authentication for staff client - TOTP -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31912] New: When enforcing 2FA we should alert the user
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31912 Bug ID: 31912 Summary: When enforcing 2FA we should alert the user 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org After bug 30588 the staff can set 2FA as forced - when this set we should notify the user of this setting both on: 1 - Their 2FA setup page in the staff interface/user account 2 - The login screen when sending them to setup 2FA -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 35601] New: Cannot go into Cataloging->Export when 2FA is enabled
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35601 Bug ID: 35601 Summary: Cannot go into Cataloging->Export when 2FA is enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com After enabling 2FA authentication for a user, they cannot go into /cgi-bin/koha/tools/export.pl anymore (Cataloging -> Export catalog). It prompts them to log-in again instantly, but putting in the email+password, and then 2FA code, it puts you back again into email+password prompt in an infinite loop, without any error. If I then go back to the main page, if I was at the 2FA stage, I have to enter my 2FA code again to see the staff interface. If I was at the email+password stage, I can then proceed without logging in again. This effectively makes catalog exporting page inaccessible. I find the whole requirement of logging in again to export catalog pretty annoying on that note, which we do fairly regularly. Is there by any chance some way to disable that (which would probably mitigate this bug too)? I couldn't find anything. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 22581] New: Include the Verovio library to show musical incipits
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22581 Bug ID: 22581 Summary: Include the Verovio library to show musical incipits Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Marc tag 031 includes the musical incipit (first compases of a melody) as code. Musical catalogs such as MUSCAT (http://muscat-project.org) use this information to display the incipit in musical code and to allow to search for incipits. Since it is possible to export MUSCAT data and import it in Koha, for music libraries it would be very helpful to display the incipit in the OPAC. MUSCAT uses an external libray, Verovio (https://www.verovio.org/) to do this. If the tag 031 is present, Verovio should be used to show the incipit in musical notation. -- You are receiving this mail because: You are watching all bug changes.

1 44

[Bug 31354] New: Clarify options for 'Change messaging preferences to default for this category?' popup
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31354 Bug ID: 31354 Summary: Clarify options for 'Change messaging preferences to default for this category?' popup Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The options for the 'Change messaging preferences to default for this category?' popup that appears when editing a patron's category are Cancel and OK, but I think No instead of Cancel and Yes instead of OK would be clearer. A library could reasonably think that Cancel refers to cancelling the change in category, and No would make it clearer that refers to the preferences only. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 35307] New: Expired holds are missing an input, so updating holds causes loss of data
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35307 Bug ID: 35307 Summary: Expired holds are missing an input, so updating holds causes loss of data Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In 23.05 when viewing a list of holds expired holds show as 'Expired: mm/dd/yyyy' The table is a form, and when submitted, these expired rows have no input - so the array of expiration dates fetched is out of sync and rows after an expired hold can have dates set incorrectly. To test: 1 - Place 3 holds on a bib, each for a different patron 2 - IN the db, set the first hold to be expired: UPDATE reserves SET expirationdate='2023-01-01' WHERE reserve_id=1; 3 - Refresh the holds page for the biblio 4 - Note the first hold now says 'Expired' in the expiration date column 5 - Set an expiration date for the last hold 6 - Click 'Update holds' 7 - Note the date is applied to the second hold -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 17798] New: Checking out an item on hold for another patron prints a slip but does not update hold
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17798 Bug ID: 17798 Summary: Checking out an item on hold for another patron prints a slip but does not update hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: Place a hold for patron A Do not confirm the hold Checkout that item to Patron B See the options including 'Don't checkout and print slip' Print the slip Check the item record The hold has not been confirmed and the item 'last seen' is not updated For consistency printing should confirm the hold as well and mark the item waiting or initiate a transfer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 34679] New: Description for RELTERMS authorized value category is wrong
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34679 Bug ID: 34679 Summary: Description for RELTERMS authorized value category is wrong Change sponsored?: --- Product: Koha Version: unspecified 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 Currently, the description for the RELTERMS authorized value category is "French terms of relations", which is not correct. This category is optionally fed with the marc21_relatorterms.yml file which is in English and translatable. I propose we change the description to "List of relator codes and terms". (As far as I can tell, there is no UNIMARC relator code list included in Koha.) -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 35009] New: [21.11] tools/scheduler.pl contains merge markers
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '24

15 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35009 Bug ID: 35009 Summary: [21.11] tools/scheduler.pl contains merge markers Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org # Failed test 'Files should not contain merge markers (./blib/INTRANET_CGI_DIR/tools/scheduler.pl, ./tools/scheduler.pl )' # at t/00-merge-conflict-markers.t line 52. # got: '2' # expected: '0' # Looks like you failed 1 test of 1. t/00-merge-conflict-markers.t ............... 1..1 not ok 1 - Files should not contain merge markers (./blib/INTRANET_CGI_DIR/tools/scheduler.pl, ./tools/scheduler.pl ) Only valid in 21.11 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16