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

[Bug 38832] New: Dead code in catalogue/search.pl
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '25

15 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38832 Bug ID: 38832 Summary: Dead code in catalogue/search.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 38744] New: Tests in Koha/Biblio.t are not rolling back
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '25

15 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38744 Bug ID: 38744 Summary: Tests in Koha/Biblio.t are not rolling back Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 38944] New: Add Test::NoWarnings to tests without warnings
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '25

15 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38944 Bug ID: 38944 Summary: Add Test::NoWarnings to tests without warnings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 25515 To prevent new warnings for test files that do not generate warnings we should use Test::NoWarnings. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25515 [Bug 25515] [OMNIBUS] Remove warnings and errors from tests output -- You are receiving this mail because: You are watching all bug changes.

1 89

[Bug 38767] New: Statuses in the holdings table should be divs not spans
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '25

15 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38767 Bug ID: 38767 Summary: Statuses in the holdings table should be divs not spans Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the holdings table there is a the status column, there can sometimes be multiple statuses per item. When there is the are displayed in <span>, being inline makes each status run together. They need to be block level <div> to be more readable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 38761] New: Backend plugins that are disabled remain visible
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '25

15 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38761 Bug ID: 38761 Summary: Backend plugins that are disabled remain visible Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 19605 Blocks: 35604 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19605 [Bug 19605] ILL backends should be pluggable through regular Koha plugins https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35604 [Bug 35604] ILL - Allow for automatic backend selection -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 33575] New: Add table settings to hold_table on /reserve/request.pl
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33575 Bug ID: 33575 Summary: Add table settings to hold_table on /reserve/request.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries who have lots of holds on a single bib would like to be able to sort/search/filter that table. We should make it a dataTable with table settings. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 36846] New: Collected and change variables are set to 0.00 when printing from POS Transaction history
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36846 Bug ID: 36846 Summary: Collected and change variables are set to 0.00 when printing from POS Transaction history Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org TO recreate: 1. Configure your Koha to enable the point of sale system (i.e. enable syspref, set up a register, set up an item to sell). 2. Complete a transaction in the POS system. 3. Go to Cash summary for { THIS BRANCH } 4. Click on the line with a link that includes your register name. ( /cgi-bin/koha/pos/register.pl?registerid=X ) 5. Click 'Print receipt'. 6. Tendered ( collected ) and Change ( change ) are 0.00 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 38521] New: Add classes to reports homepage
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38521 Bug ID: 38521 Summary: Add classes to reports homepage Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface 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 /cgi-bin/koha/reports/reports-home.pl is quite classless, which makes it hard to point at with jQuery and CSS. I'd like to add some classes. It's incredibly hard not to fill this bug filing with dumb "class" puns. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 36115] New: Improve documentation for Return-Path (branches.branchreturnpath)
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36115 Bug ID: 36115 Summary: Improve documentation for Return-Path (branches.branchreturnpath) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org I am not sure if the code or the documentation is the problem here, but let's start with the documentation. For reference, the manual says this today: Email: the email address field is not required, but it should be filled for every library in your system - Note: Be sure to enter a library email address to make sure that notices are sent to and from the right address - Note: If no email address is entered here, the address in the KohaAdminEmailAddress system preference will be used to send notices from this library Reply-To: you can enter a different ‘Reply-To’ email address. This is the email address that all replies will go to. - Note: If no email address is entered here, the address in the ReplytoDefault system preference will be used to receive replies to this library Return-Path: you can enter a different ‘Return-Path’ email address. This is the email address that all bounced messages will go to. - Note: If no email address is entered here, the address in the ReturnpathDefault system preference will be used to receive bounced messages from this library. https://koha-community.org/manual/latest/en/html/administration.html#adding… Mu scenario is as follows: We host Koha for a number of libraries that want to send messages to their patrons by email. For some libraries we can't send email through their SMTP for different reasons. So we set up a noreply address with a domain that we control, so that we can use that as the sender of the emails, and we can do our best to set up SPF, DKIM etc for it, so it won't be seen as spam by services such as Gmail. Based on the description above, I set it up like this: Email = noreply Reply-To = real library email Return-Path = real library email But it turns out that when postfix was processing the email, and passing it on to our SMTP server, it was seeing the "real library email" from the Return-Path setting as the "from" address, not the "noreply" address that we wanted it to see. So the question is: - Is the code wrong in using the Return-Path address as the "from" address? - Or is the documentation wrong in saying that the Return-Path is just for bounced messages? See also: Bug 28729 - Return-path header not set in emails -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 36273] New: ILL - Refactor $op in ill-requests.pl
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36273 Bug ID: 36273 Summary: ILL - Refactor $op in ill-requests.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: pedro.amorim(a)ptfs-europe.com Depends on: 36241, 36243, 36245, 36249 With bug 34478, presenting a form page should be a GET request without 'cud-' in the op URL parameter. Additionally, a form that creates, updates or deletes some object should be a POST with the 'cud-' prefix. ill-requests.pl did not do this distinction originally, and still doesn't. It instead works around 'cud-' in the $op to preserve existing functionality. It should be refactored to better distinguish between a GET $op and a POST $op. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36241 [Bug 36241] ILL Batches are broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36243 [Bug 36243] ILL "Edit request" action is broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36245 [Bug 36245] ILL - Custom backend form action is broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36249 [Bug 36249] ILL - "Request from partners" action is broken -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9