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

[Bug 15566] Update API to allow to reserve first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15566 Emily Lamancusa (emlam) <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42407] New: Test failure when HoldsLog enabled: t/db_dependent/Koha/Patrons.t
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42407 Bug ID: 42407 Summary: Test failure when HoldsLog enabled: t/db_dependent/Koha/Patrons.t Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - confirm HoldsLog is set to Don't Log - prove t/db_dependent/Koha/Patrons.t - it passes! - set HoldsLog to Log - prove t/db_dependent/Koha/Patrons.t - it fails :( kohadev-koha@kohadevbox:koha(main)$ prove t/db_dependent/Koha/Patrons.t t/db_dependent/Koha/Patrons.t .. 21/50 # Looks like you planned 6 tests but ran 2. # Failed test 'holds and old_holds' # at t/db_dependent/Koha/Patrons.t line 1310. encountered object '2026-04-18T19:39:47', but neither allow_blessed, convert_blessed nor allow_tags settings are enabled (or TO_JSON/FREEZE method missing) at /usr/share/perl5/JSON.pm line 173. # Looks like your test exited with 11 just after 23. t/db_dependent/Koha/Patrons.t .. Dubious, test returned 11 (wstat 2816, 0xb00) Failed 28/50 subtests Test Summary Report ------------------- t/db_dependent/Koha/Patrons.t (Wstat: 2816 (exited 11) Tests: 23 Failed: 1) Failed test: 22 Non-zero exit status: 11 Parse errors: Bad plan. You planned 50 tests but ran 23. Files=1, Tests=23, 7 wallclock secs ( 0.01 usr 0.00 sys + 2.85 cusr 0.60 csys = 3.46 CPU) Result: FAIL -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13823] Item search should include note fields
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13823 Cassidy <cassidy.miller(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwsdonna(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13823] Item search should include note fields
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13823 Cassidy <cassidy.miller(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cassidy.miller@bywatersolut | |ions.com --- Comment #6 from Cassidy <cassidy.miller(a)bywatersolutions.com> --- This is still valid, and it would be really helpful. Library currently asking for it. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 ayoung <ayoung(a)oslri.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ayoung(a)oslri.net -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23003] New: Accessibility improvements
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 Bug ID: 23003 Summary: Accessibility improvements Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- >From the french mailing list: The Ministry of Culture published a study detailing the accessibility of different OPAC in France. There are some areas that we could improve. Koha gets a quite good score, but a 'C' is given for: 1. the "skip links" - https://www.wikiwand.com/en/Skip_link 2. No search autocomplete 3. Button to place a hold on Also they pointed out that Tanaguru gives Koha a score of 65%, we could certainly improve it. https://www.tanaguru.com/en/open-source-tools-tanaguru/ Important note: The tests have been done using the following catalogue: http://cat-bib.nimes.fr/ (Koha 17.11.13) http://www.culture.gouv.fr/Thematiques/Livre-et-Lecture/Actualites/Barometr… http://www.culture.gouv.fr/content/download/213998/2245555/version/2/file/B… -- You are receiving this mail because: You are watching all bug changes.

1 58

[Bug 33886] New: Flatpickr calendar - year controls for date of birth on memberentry.pl are not intuitive
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33886 Bug ID: 33886 Summary: Flatpickr calendar - year controls for date of birth on memberentry.pl are not intuitive Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I appreciate a lot of work has gone into swapping from the now-obsolete datepicker to flatpickr. However, when entering a date of birth on the joining form (memberentry.pl), on both the staff intranet and the public OPAC, flatpickr is not intuitive for users. For the staff, having a form cause frustrations when you're welcoming new patrons is not ideal - but at least we can train the staff on flatpickr's quirks. For new patrons trying to join on the OPAC, it's impossible to explain how to use it to them. We are concerned that patrons may choose not to join because of difficulty with the date of birth field. Full explanation: Koha previously used datepicker. It was possible to enter dates using just the keyboard (typing in), or just the mouse (using the datepicker calendar). With flatpickr, you can use the keyboard (typing in) - but if you attempt to use flatpickr as mouse-only, it's extremely long-winded. Flatpickr appears to be designed for mouse+keyboard together, which is unusual - and unexpected for the end user - in a calendar. With datepicker, the mouse workflow was: - Click to open datepicker. Then work from left to right, top to bottom: - Use the dropdown menu to select month. - Use the dropdown menu to select year. - Click on the date to select the date. These steps were all handled by the mouse alone. Using flatpickr, the mouse workflow is: - Click to open flatpickr Note that you cannot work from left to right. This is because flatpickr initialises with today's date. If you have a patron who is born in October but the current month is June, then October doesn't show in the month dropdown (as it's a date in the future). This means you have to start with the year, which is counterintuitive, as it's working right to left. - There is a box to type the year into - meaning that it's not mouse-only. Many average computer users might not even realise that this box can be typed into. Depending on how you use a mouse/keyboard (particularly Tenkey users), typing in can mean lifting your hand from the mouse to use the keyboard and going back again. - The year controls do not display until mouseover, so it's not immediately apparent to all users how the year can be manipulated - especially as this is juxtaposed with the permanently visible month dropdown controls. - When hovering over the year, the arrow controls then appear - and if you're expecting mouse-only input, you may believe you need to use these, rather than typing the year. - The arrow controls only increment +/- 1 year. It's not possible to click and hold to jump +/- 10 years, for example. If you try to use flatpickr as mouse-only and your patron was born in the 1950s, you'll be clicking for a very long time. So the mouse-only workflow ends up being: - Click to open flatpickr - Have to remember to work from right to left - Hover over the year so the arrow controls show - Click 70 times to get back to 1953 - Go right to left to the month drop down to select the month - Then select the date If you choose to type in the year instead, it feels as if it's defeating the object of having a calendar, as you've already typed in 4 digits out of an 8 digit date. Frequent requests have been made to the developer on GitHub for a change to this workflow, but the developer prefers their existing implementation - so a change would need to be a plugin. To alleviate the friction with the year selection, is there a plugin that can be adopted/written/implemented? It doesn't have to be a dropdown plugin; in other calendars, there are different mouse-only methods of handling years, for example: https://element.eleme.cn/#/en-US/component/date-picker (this style is used in Windows). There's some discussion of this on StackOverflow: https://stackoverflow.com/questions/51425067/flatpickr-adding-dropdown-to-c… - including some solutions. And there's a recent (May 2023) dropdown plugin linked from that page: https://gist.github.com/ZachSaucier/ec6f58e49082c27eaae240786bc82997 Please could a plugin be considered? Or a different method of handling year inputs, at least where date of birth is a flatpickr field? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 26197] New: Using Rancor while cataloging doesn't appear to check for existing records
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26197 Bug ID: 26197 Summary: Using Rancor while cataloging doesn't appear to check for existing records 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Upon testing this, while cataloging a new record using the basic editor Koha will find a duplicate record existing in Koha but didn't find the same duplicate using the Advanced Editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 42402] New: Document OAI-PMH:HarvestEmailReport system preference
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42402 Bug ID: 42402 Summary: Document OAI-PMH:HarvestEmailReport system preference Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de Bug 25659 introduced a new system preference: OAI-PMH:HarvestEmailReport. A description of the system preference should be added to the Manual, on the Web services preferences page. It should refer to the Manual section for the OAI harvesting cronjob (and perhaps to the OAI repositories section too). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39860] New: Add a system preference to allow for addtional/custom MARC fields in the record display
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '26

16 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39860 Bug ID: 39860 Summary: Add a system preference to allow for addtional/custom MARC fields in the record display Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if we could define additional MARC fields in a system preference via Template Toolkit and then have them display on the results/detail pages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 140