April 2024 - Koha-bugs - lists.koha-community.org

[Bug 33459] New: Patrons need messaging preferences for other notices
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '25

04 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33459 Bug ID: 33459 Summary: Patrons need messaging preferences for other notices 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Patrons should be able to set how they want all other notices that are not currently included in their messaging preferences. There is no reason they or staff should not be able to set how they get their password resets, welcome message, expirations, suggestions, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35613] New: Migrate spec to OpenAPI v3
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35613 Bug ID: 35613 Summary: Migrate spec to OpenAPI v3 Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Things to do: - Convert our spec into OpenAPIv3 (probably using redocly) - Migrate array types ("type" and "null") into using the "nullable": true provided attribute - Verify no regressions found - Report potential issues to https://github.com/jhthorsen/mojolicious-plugin-openapi - Split the bundled spec into pieces as we have now. - The generated api.koha-community.org documentation needs to be at least the same in terms of information and usability. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 23780] New: Batch check out fails to inform or trap
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23780 Bug ID: 23780 Summary: Batch check out fails to inform or trap Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I have managed to catch failures in Batch check out on the following scenario: Patron has fines over the allowed limit. Item type only allows 5 check outs. When checking out 6 of this item type, Batch check out failed to: * Show any information that the patron had reached fine limit * Show that the patron was checking out too many of this item type If I checked out these 6 items without the fine, it gives the warning about too many items and asks me to confirm. If I check out 5 of these items with the fine, it does not explain why I need to confirm. It seems that Batch check out: * Is not displaying a reason for confirmation with the fine block. * Is not displaying a reason for confirmation when there are multiple blocks. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 30236] New: Layout of self registration confirmation page is broken
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30236 Bug ID: 30236 Summary: Layout of self registration confirmation page is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Created attachment 131406 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131406&action=e… Screenshot of confirmation step of self registration When testing bug 30214 I noticed that in Google Chrome self registration page you get to from the link in the verification message has a somewhat broken layout. The login form should be on the right, etc. (see attached screenshot) -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 31210] New: Add option to use different library name in OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31210 Bug ID: 31210 Summary: Add option to use different library name in OPAC and staff interface Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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, michaela.sieber(a)kit.edu At the moment the name of a library is used both in OPAC and staff displays. It would be nice if we could use different descriptions in staff and OPAC as some libraries would prefer to use an abbreviated internal version of the name in the staff interface. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28608] New: Creating a biblio record leads to item creation even if framework has no items field
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28608 Bug ID: 28608 Summary: Creating a biblio record leads to item creation even if framework has no items field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some framework for biblio records have no items field (952 in MARC21, 995 in UNIMARC). Records can not have items for example a serial article. In this case creating a record should not lead to item creation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 30816] New: Use of uninitialized value in numeric ge (>=) at /usr/share/koha/lib/C4/Serials.pm
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30816 Bug ID: 30816 Summary: Use of uninitialized value in numeric ge (>=) at /usr/share/koha/lib/C4/Serials.pm Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 25790 The code here is: for(my $i = 0; $i < $count; $i++) { if($calc{'X'}) { # check if we have to increase the new value. $newinnerloop1 += 1; if ($newinnerloop1 >= $pattern->{every1}) { $newinnerloop1 = 0; $newlastvalue1 += $pattern->{add1}; } # reset counter if needed. $newlastvalue1 = $pattern->{setto1} if ($newlastvalue1 > $pattern->{whenmorethan1}); } And above: $newinnerloop1 = $subscription->{innerloop1} || 0; I believe this is caused by subscription_numberpatterns.every1 being NULL. The default in the database is NULL, but I haven't tested if this can be set manually from the GUI yet. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25790 [Bug 25790] [OMNIBUS] warnings removal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 36684] New: Cancelling an item with uncertain prices leaves the basket marked as a problem
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36684 Bug ID: 36684 Summary: Cancelling an item with uncertain prices leaves the basket marked as a problem Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Issue: When a basket contains an item with an uncertain price, it is flagged as a 'problem.' Baskets cannot be finalized if they include items with uncertain prices. However, if you cancel an order for an item with an uncertain price, the basket still remains marked as a 'problem,' but it can be closed out. This situation might confuse some users who may wonder why their basket is labeled as a problem. This confusion arises because the active items do not display uncertain prices, and there is no way to ascertain whether canceled items were initially marked as uncertain before their cancellation. Suggested resolution: Prevent users from cancelling items with uncertain prices until the uncertain price is cleared/resolved. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 36287] New: Ability to view both the budget name and budget code in a basket
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36287 Bug ID: 36287 Summary: Ability to view both the budget name and budget code in a basket Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries have expressed interest in seeing both the budget name and code in the basket table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 34088] New: Schema upgrade should short circuit faster if no upgrade needs to be done
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '25

01 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34088 Bug ID: 34088 Summary: Schema upgrade should short circuit faster if no upgrade needs to be done Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, if there is no database upgrade to run, updatedatabase.pl can take over 1.1 seconds to run. If you chain together 60 runs of updatedatabase.pl via koha-upgrade-schema and "apt-get install koha-common", that takes well over 1 minute at best to check that nothing needs to be done. (In practice, I think it goes over 1 minute.) We should be short circuiting earlier because we have the code version at hand and it's easy to check the database version. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78