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

[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 36486] New: Add tests for Koha::DateTime::Format::SQL
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36486 Bug ID: 36486 Summary: Add tests for Koha::DateTime::Format::SQL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 36432 Bug 36432 is missing some tests for Koha::DateTime::Format::SQL. Since it is already Passed QA, I will attach them in this new bug report. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36432 [Bug 36432] Remove circular dependency from Koha::Object -- You are receiving this mail because: You are watching all bug changes.

1 16

[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

[Bug 34823] New: Do not show item group drop-down if there are no item groups
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34823 Bug ID: 34823 Summary: Do not show item group drop-down if there are no item groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When EnableItemGroupHolds is activated, there is a "Request specific item group:" drop-down in the OPAC when placing a hold. However, this drop-down appears regardless of whether the record has item groups or not. I think this may be confusing for patrons. To replicate: 1. Enable EnableItemGroups and EnableItemGroupHolds 2. Go to the OPAC and log in as a patron 3. Go to any record that doesn't have grouped items and try to place a hold 4. Click on "Show more options" --> Note that there is an option to choose an item group with the only option being "Any item group" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 36347] New: Return claims table is loaded twice
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36347 Bug ID: 36347 Summary: Return claims table is loaded twice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The issue is caused by these lines in circulation.js: $("#finesholdsissues a[data-toggle='tab']").on("shown.bs.tab", function(e){ $(this).click(); }); When the user clicks on a hidden tab, 'shown.bs.tab' is triggered and then another click event is triggered. And because the table is loaded on tab click, it is loaded twice. Visually it can cause the rows to be duplicated (it is random, probably due to timing, network latency, ...) -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 36392] New: Only 20 vendors in ERM dropdown
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36392 Bug ID: 36392 Summary: Only 20 vendors in ERM dropdown Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: caroline.cyr-la-rose(a)inlibro.com CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com When there are more than 20 vendors in acquisitions, only 20 appear in the New agreement dropdown list. To recreate: 1. Enable the ERMModule system preference 2. In Acquisitions, create more than 20 vendors (see below for an sql insert that I used) 3. Go to E-resource management > Agreements > New agreement 4. Open the vendor dropdown --> It stops at Sierra (or the 20th vendor if you created your own) 5. Type "Tango" or "Zulu" (or one of the names of your 21st+ vendor) --> No results This is what I used to create all the vendors INSERT INTO aqbooksellers (name,active) VALUES ('Alpha','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Bravo','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Charlie','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Delta','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Echo','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Foxtrot','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Golf','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Hotel','1'); INSERT INTO aqbooksellers (name,active) VALUES ('India','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Juliet','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Kilo','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Lima','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Mike','1'); INSERT INTO aqbooksellers (name,active) VALUES ('November','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Oscar','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Papa','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Quebec','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Romeo','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Sierra','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Tango','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Uniform','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Victor','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Whiskey','1'); INSERT INTO aqbooksellers (name,active) VALUES ('X-Ray','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Yankee','1'); INSERT INTO aqbooksellers (name,active) VALUES ('Zulu','1'); Paul D. pointed me to the RESTdefaultPageSize system preference which does affect the dropdown. If I change the syspref to 50, I can see all the vendors in the dropdown. The problem with this is that I'm not sure what else this syspref affects. I have a client with 674 vendors, I don't want to put 1000 in the syspref and then somewhere else something takes forever to load because of this. I'm not sure what is happening here. I found bug 32474 and bug 32468 that seem to deal with this and that are marked as fixed, but I don't see the correct behaviour in ktd with master. I hope someone else can confirm or invalidate this... The client who pointed this out to me (the one with 674 vendors) is on 23.05.05, which already has the patches from bug 32468. -- You are receiving this mail because: You are watching all bug changes.

1 24