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

[Bug 23296] New: Auto Renewal Notice does not use Library specific notices
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23296 Bug ID: 23296 Summary: Auto Renewal Notice does not use Library specific notices Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org All notices in Koha are created to be a default ALL libraries notice, however, with branch systems, there is also the ability to create a library specific notice that can be used instead. However, the notice AUTO_RENEWALS is not currently capable of being library specific - instead, the ALL Library Notice for AUTO_RENEWALS is the only one that Koha send. To adjust this, it would be recommended that a library specific notice like all the others in Koha can be created. Following circ control, would be the suggested way to go as with most notices in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 35573] New: Koha is no correctly warning of overridden items when placing a hold if AllowHoldPolicyOverride
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35573 Bug ID: 35573 Summary: Koha is no correctly warning of overridden items when placing a hold if AllowHoldPolicyOverride Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 If AllowHoldPolicyOverride is enabled we are not warning that items require override if there are valid pickup locations. Regressions caused by (me on) bug 30687 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 36269] New: ElasticSearch: publisher-location (pl) index should use 264a
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36269 Bug ID: 36269 Summary: ElasticSearch: publisher-location (pl) index should use 264a Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at Currently the index `pl` points to 008/15-17. It should (additionally/instead?) point to 260a and/or 264a. * Fix the default mappings in admin/searchengine/elasticsearch/mappings.yaml Notes from chat: cait: maybe having the index broader is not a bad thing, I am not sure if it's confusing or not cait: like put 260a (non-RDA), 264 (RDA) and 008 15-17 in it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 35129] New: REST API: _per_page=0 crashes on Illegal division by zero
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35129 Bug ID: 35129 Summary: REST API: _per_page=0 crashes on Illegal division by zero Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: tomascohen(a)gmail.com >From IRC: [14:08] <marcelr> Nice /api/v1/patrons?_page=1&_per_page=0 just returns me a 500 (ISE) [14:09] <marcelr> not tested yet :) [14:10] <marcelr> [ERROR] GET /api/v1/patrons: unhandled exception (Mojo::Exception)<<Illegal division by zero at /usr/share/koha/Koha/REST/Plugin/Pagination.pm line 106.>> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 35977] New: Display current date in Hold starts on date on opac-reserve
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35977 Bug ID: 35977 Summary: Display current date in Hold starts on date on opac-reserve Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirjam.vantieghem(a)etf.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is related to bug #15652. If you enable AllowHoldDateInFuture (and its OPAC variant), you get an additional "Hold starts on date". It is possible to select the current date from the datepicker in the OPAC. If no date is selected, the default is the current date. However, it is not clear to the patron that the current date is selected by default, as the field is empty if no date has been selected from the datepicker. This caused confusion among some of our patrons. Therefore we use a custom patch to have the current date shown in the field "Hold starts on date". What Marcel de Rooy wrote in the related bug, also applies here: "Although it does not really make any difference if you leave the startdate empty or put the current date in it, we concluded that it still makes a psychological difference." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 36341] New: "Hold starts on date" should be limited to future dates
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36341 Bug ID: 36341 Summary: "Hold starts on date" should be limited to future dates 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org For some reason we don't appear to limit the date selection yet available in the OPAC 'Hold starts on date'.. it should only allow future dates. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 30717] New: Date format doesn't change in additem for dateaccessioned
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30717 Bug ID: 30717 Summary: Date format doesn't change in additem for dateaccessioned Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mengu(a)devinim.com.tr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, After upgrade from 19.05 to 21.11.04 we got a problem with additem section. dateaccessioned area of additem doesn't seem correctly even we changed dateformat in systempreferences. I've removed the blank in the line var dateformat_pref = "[% Koha.Preference('dateformat') | html %]"; of calendar.inc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 36376] New: Display library limitations issue in patron's messages
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36376 Bug ID: 36376 Summary: Display library limitations issue in patron's messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 31422 added a warning message when library limitations issue in patron edition page. We should add this patron's messages in circ and details pages. Like age limitations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 36421] New: REST API 500 errors say to check the logs, but suppress errors that would be there
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36421 Bug ID: 36421 Summary: REST API 500 errors say to check the logs, but suppress errors that would be there Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com CC: tomascohen(a)gmail.com If a REST auth error happens that that is unblessed or uncaught, we should warn the value to the logs. Test Plan: 1) Install the curbside pickups plugin 2) create a patron with the userid 'puser' and the cardnumber 'pcard' 3) GET /api/v1/contrib/curbsidepickup/patrons/XXX/pickups using basic auth with the username 'pcard' where XXX is the patron borrowernumber 4) Note there is no error in the logs -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 36227] New: No warning if placing hold on item group with no items
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36227 Bug ID: 36227 Summary: No warning if placing hold on item group with no items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It is currently possible to place a group-level hold on an item group with no items in it, both from the staff client and OPAC. This results in a hold that is not fillable unless the item group is deleted or an item is added into it. A warning would be helpful so patrons aren't left with an unfillable hold. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23