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

[Bug 31323] New: Edit item highlighting problem
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31323 Bug ID: 31323 Summary: Edit item highlighting problem Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To reproduce: 1 search the catalog 2 find a record with 1 item 3 click the edit button in the item table (to the right of Spine Label) 4 when I click "save changes" the item is still highlighted yellow It appears like the '.active' class is lingering. I think this might be caused by Bug 27526? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 39287] New: Improve "Show volume" search with a more specialized search index
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39287 Bug ID: 39287 Summary: Improve "Show volume" search with a more specialized search index Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, michaela.sieber(a)kit.edu Currently the rcn index used to search for volumes contains all $w subfields from 7xx and 8xx linking fields. In some cases this is too broad, even tho we are additionally limiting to monographs. Example: Search volumes will also find - records with a 775$w - other edition - records with a matching 780/785$w - preceeding or succeeding ... A specific index for searching volumes (rcn-volumes) should contain: - 773$w (we still need to limit to monographic, because these could also be analytcal links) - 800$w - 810$w - 811$w - 830$w Once the index is defined we can update the XSLT and the method for determining if the "Show volumes" link should be shown to use it and have a correct result list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 41303] New: "showRDAtag264" not displayed in staff client detail page and not fully in OPAC
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41303 Bug ID: 41303 Summary: "showRDAtag264" not displayed in staff client detail page and not fully in OPAC Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: anke.bruns(a)gwdg.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The subfields (typically a, b, c) of 264 are not preceded by any description like e.g. Place of Publication: Publisher: Publication Date: Or even a single description like Publication details: as seems to be the case if these are stored in 260 (see XSLT) In the OPAC they are preceded by "Publisher" but then no further specification as to place, date or publisher. I think the passage in the relevant Detail page XSLT overwritten  and the corresponding template showRDAtag264 are probably the thing to look at. How to fix this? (Maybe this is related to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37423 ). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36808] New: Slips should be a message transport type
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36808 Bug ID: 36808 Summary: Slips should be a message transport type Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently we create entirely new notices for SLIP type notices when really they're just a different medium and thus should be a message transport type. I propose adding a SLIP message transport type and where appropriate merging the current SLIP notices into their corresponding non-slip counterparts. A 'slip' is just a small form printer and likely to have similar summary detail as an SMS for example. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 41283] New: Use a better diff viewer library
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '25

11 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41283 Bug ID: 41283 Summary: Use a better diff viewer library Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org We use koha-tmpl/intranet-tmpl/lib/jsdiff/jsdiff.js from https://johnresig.com/projects/javascript-diff-algorithm/ for viewing diffs in the log viewer, patron merge, automatic updating of outdated reports, and MARC record diffs in batch imports. Unfortunately, it's a very elegant implementation of a not very robust diff algorithm. The simplest failure to see is that if you move a line from one spot in the thing being diffed to another spot, it won't detect any difference. So if someone changes if (wechecked) { dothething(); } to dothething(); if (wechecked) { } in IntranetUserJS, it will show an empty diff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 36809] New: DRY out notice and slip printing
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '25

11 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36809 Bug ID: 36809 Summary: DRY out notice and slip printing Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We have a plethora of slip and notice printing controllers and templates. This makes it difficult to improve the notices tools and not miss area's.. we should really move to one or two definitive scripts and templates for printing slips and notices and remove all the duplicate unmaintained code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 30343] New: Any failed delivery method in overduerules.pl produces a printed notice in attachment.txt
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '25

11 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30343 Bug ID: 30343 Summary: Any failed delivery method in overduerules.pl produces a printed notice in attachment.txt Change sponsored?: --- Product: Koha Version: 21.11 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 Previously we had only used the e-mail delivery method in overduerules.pl. This worked great. When a patron didn't have an e-mail address, a printed notice was added to the attachment.txt file for printed notices. Now we have phone and sms added as delivery methods. However, if ANY of these fail (no SMS number or no primary phone, or in the case of Twilio, if the same notice is sent via e-mail or sms, the phone status shows as deleted to prevent duplication) a printed notice is added to the attachment.txt file for printed notices. There should be option to determine if a printed notice is generated if ANY of the other methods fail, or if ALL of the methods fail. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 41244] New: Logging patron attributes logs two entries everytime a new patron account (with extended attribute values) is created
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '25

11 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41244 Bug ID: 41244 Summary: Logging patron attributes logs two entries everytime a new patron account (with extended attribute values) is created Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Created attachment 189528 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189528&action=e… Two action log entries when creatng a patron account When you create a new patron account (with extended attribute values included) - and the borrowersLog syspref enabled - two log entries are generated: - a Create action - a Modify action (See attached screenshot). This happens when you use the 'Import patron' tool or manually create a new patron in the staff client. Surely, only the create log entry should be generated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38615] New: Cancelling a waiting hold via SIP should include an option to move it to holds with cancellation requests
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '25

10 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38615 Bug ID: 38615 Summary: Cancelling a waiting hold via SIP should include an option to move it to holds with cancellation requests Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org You can cancel a hold via SIP, the hold is immediately canceled. There should be an option ( system preference ) to allow cancelled waiting holds from SIP to move to 'Holds with cancellation requests'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 40399] New: Add desk ID to statistics and pseudonymized_transactions
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '25

10 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40399 Bug ID: 40399 Summary: Add desk ID to statistics and pseudonymized_transactions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Desks provide a great way for libraries to gauge service point staffing, but that isn't tracked in statistics or pseudonymized transactions. Adding a desk ID to transactions in those tables would make that data meaningful and reportable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5