July 2026 - Koha-bugs - lists.koha-community.org

[Bug 43041] Uncaught exceptions and DBI errors are not timestamped in plack-error.log
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43041 Kyle M Hall (khall) <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43041] Uncaught exceptions and DBI errors are not timestamped in plack-error.log
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43041 --- Comment #1 from Kyle M Hall (khall) <kyle(a)bywatersolutions.com> --- Created attachment 201818 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=201818&action=e… Bug 43041: Uncaught exceptions and DBI errors are not timestamped in plack-error.log Bug 16357 added timestamps to Plack warnings by sending them through Log4perl with the LogWarn middleware. Only warnings take that path. Uncaught exceptions, DBI errors, and anything a script prints to STDERR ( technically nothering does that, but reports/catalogue_stats.pl has some debug code that could in theory ) are written to the psgi.errors stream, so they end up in plack-error.log with no timestamp. This makes it hard to tell when an error happened, or to find all the errors for a given day. This patch adds a tied psgi.errors filehandle that sends those writes through Log4perl, so they are logged with a timestamp in plack-<interface>-error.log alongside the warnings. Test Plan: 1) Add a line that dies to the top of a staff script such as mainpage.pl: die "Bug XXXXX test"; 2) Restart plack 3) Load the staff home page 4) Note the exception is written to plack-error.log with no timestamp 6) Apply this patch 7) Restart plack again 8) Reload the staff home page 9) Note the exception is now written to plack-intranet-error.log with a timestamp, and no longer written to plack-error.log! 10) Change the die to a warn 11) Retart plack again 12) Reload the staff home page 13) Verify the warns still come through as they did pre-patch -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40619] New: Remove OverDrive star ratings from OPAC JS
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40619 Bug ID: 40619 Summary: Remove OverDrive star ratings from OPAC JS Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org OverDrive no longer supplies star ratings via their API: https://developer.overdrive.com/blog/16-may-2025-coming-soon-adding-content… We can remove the code in opac-overdrive-search.tt which used to show those star ratings. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 35776] New: Wrong circulation rule displayed when parent itemtypes are used
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35776 Bug ID: 35776 Summary: Wrong circulation rule displayed when parent itemtypes are used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Follow the plans on bug 30324 - note the rule displayed is always the default rule. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28639] New: Embed see-from headings (from authorities) into bibliographic records at OAI repository level
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28639 Bug ID: 28639 Summary: Embed see-from headings (from authorities) into bibliographic records at OAI repository level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: julien.sicot(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org Hi, It could be interesting to enrich the bibliographic records exposed in OAI with see-from headings, this would allow users who use koha with a discovery tool to be able to manage, normalize and index some authorities data ? This is something that could be done directly in C4::Biblio::GetMarcBiblio following the same method used for embedding items. We could use an optional parameter like embed_items (embed_seefromheading) and a function similar to C4::Biblio::EmbedItemsInMarcBiblio by reusing what was made for zebra with EmbedSeeFromHeadings (bug #7417). Thanks for feedback, Best Julien Sicot Systems Librarian, Université Rennes 2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 18139] New: 'Too many checked out' can confuse librarians
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18139 Bug ID: 18139 Summary: 'Too many checked out' can confuse librarians Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The too many checked out message can be very confusing for librarians when the limit specified is more or less than the number of checkouts the patron already has. We should make it clear to the librarian that this is only counting certain types of checkouts by giving them the issuing rule criteria used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 37202] New: Add a booking reminder notice to let patrons know they have an upcoming booking
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37202 Bug ID: 37202 Summary: Add a booking reminder notice to let patrons know they have an upcoming booking Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Blocks: 36666 Patrons may book items a long time in advance, they may need reminding that said booking exists and will need to be picked up. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36666 [Bug 36666] Bookings needs some slips and notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 43054] New: circulation-home.pl page layout is inconsistent with IntranetCirculationHomeHTML
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43054 Bug ID: 43054 Summary: circulation-home.pl page layout is inconsistent with IntranetCirculationHomeHTML Initiative type: --- Sponsorship --- status: 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- When using IntranetCirculationHomeHTML, it is difficult to match the layout of the page without unwrapping a section of html. At some point this page changed, and I have had to rely on jQuery to adjust some things so I could continue the layout already in use. This is the jQuery I have to use currently: if($('#circ_circulation-home').length) { $('#intranet-circulation-home-html div.col-md-12').contents().unwrap(); } Was it intentional to do this, or is this something that can be permanently removed? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 43048] Prevent users from completely removing fields from cataloging frameworks that break Koha
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43048 --- Comment #1 from Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> --- I also noticed that if a user deletes 952$9 from their cataloging framework, it's not possible to reset the Koha link to itemnumber from the staff interface. You have to go in the db and set it manually, which is not ideal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 43060] New: Link suggestion in basket to item record
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '26

11 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43060 Bug ID: 43060 Summary: Link suggestion in basket to item record Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lhilleary(a)wrl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The Link Suggestion function was recently added as a part of our Koha upgrade in May, but we wanted to see if this could be adjusted a bit with an enhancement. Right now, the function works to link a suggestion at the bib level only. However, we also get suggestions for specific volumes (in a graphic series). Our graphic series volumes are on a single bib record. So, we are pulling in the bib level record into the basket and specifying the volume in $t in the order line so the vendor knows which volume is being ordered. But because it was actually the bib level that was pulled into the basket, linking a suggestion is adding it to the bib level and not the item level. Could the Link Suggestion function then be expanded to allow for a selection of adding to the bib or item level? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0