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

[Bug 42536] New: ERM Resource proxy should be displayed
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42536 Bug ID: 42536 Summary: ERM Resource proxy should be displayed Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk The proxy field of an ERM Resource record should be displayed in the record view under Resource settings (like Coverage dates) To reproduce: - Create an ERM Package - Create an ERM Title - Modify the title and link it to the package. Enter Start date and Proxy - Save - Display Title view - Click on Linked package in the table below Now you see the resource record in the view mode: cgi-bin/koha/erm/eholdings/local/resources/123 Verify, that proxy is not displayed, only the start date. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 42496] New: Holds to pull causes virtual keyboard to flicker when using filters on Android tablets
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42496 Bug ID: 42496 Summary: Holds to pull causes virtual keyboard to flicker when using filters on Android tablets Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The Holds to pull view causes Android devices' virtual keyboard to flicker many sequential times (sometimes more than 10) specifically when filtering by text field filters on Android tablets. The flickering happens when you activate a filter field. Tested on latest Firefox version on an Android tablet Running Koha 25.05. By flickering I mean the virtual keyboard getting brought up (popping up) and instantly going down in a repeated sequence. The number of times it happens seems to depend on what filter you press on and how much data is being viewed in the datatable. This is an accessibility issue that should be fixed asap since many libraries use holds to pull report on tablets for pulling holds "at location". I tried to hunt for similar bugs reported in other parts of Koha but couldn't find any. I've also verified that this issue exists on a 2022 model Google Pixel using Chrome with desktop mode/view and in mobile mode/view. Many other handheld Android devices have this issue too I assume and it doesn't seem to be browser specific or browser version specific. Haven't tested on an IPad. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 40340] New: Backslashes next to a subfield ($) breaks staging
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40340 Bug ID: 40340 Summary: Backslashes next to a subfield ($) breaks staging Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 183951 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=183951&action=e… Test MARC file If you have a backslash next to a subfield in the data, the staging will fail if you are using the tag as a record matching rule. Most commonly, matching on 245$a (title or title-cover). For instance, in the attached file, there is a backslash right before $h =245 00$aKnights of the black earth \$h[Book] If you have 245 as matching rule, the import batch will fail. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 42533] New: Double quotes can break stage_file.pl
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42533 Bug ID: 42533 Summary: Double quotes can break stage_file.pl Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Splitting off from Bug 40340: (In reply to Enica Davis from comment #1) > Additionally, if you include double quotes in 245$a, stage_file.pl will time > out. See the test MARC file #2 in the attachment. > > Furthermore, if the tag you are matching on contains something like > {dollar}, which is commonly found in 020$c, stage_file will time out. > > The error: > > [query_shard_exception] Failed to parse query [(title:""---And Ladies of the > Club" /")], with: > {"index":"koha_utstatelibdivtest_biblios","index_uuid": > "_AD3tsfnTpC9t4mncAArSw"}, called from sub > Search::Elasticsearch::Role::Client::Direct::__ANON__ at > /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 101. With > vars: {'body' => {'error' => {'phase' => 'query','grouped' => bless( do{\(my > $o = 1)}, 'JSON::PP::Boolean' ),'failed_shards' => [{'node' => > 'Q3tYO6wsTXKbYv20ptCAKw','index' => 'koha_utstatelibdivtest_biblios','shard' > => 0,'reason' => {'reason' => 'Failed to parse query [(title:""---And Ladies > of the Club" /")]','index_uuid' => '_AD3tsfnTpC9t4mncAArSw','type' => > 'query_shard_exception','caused_by' => {'caused_by' => {'reason' => > 'Encountered " "-" "- "" at line 1, column 10. > Was expecting one of: > <BAREOPER> ... > "(" ... > "*" ... > <QUOTED> ... > <TERM> ... > <PREFIXTERM> ... > <WILDTERM> ... > <REGEXPTERM> ... > "[" ... > "{" ... > <NUMBER> ... > <TERM> ... > "*" ... > ','type' => 'parse_exception'},'reason' => 'Cannot parse > \'(title:""---And Ladies of the Club" /")\': Encountered " "-" "- "" at line > 1, column 10. > Was expecting one of: > <BAREOPER> ... > "(" ... > "*" ... > <QUOTED> ... > <TERM> ... > <PREFIXTERM> ... > <WILDTERM> ... > <REGEXPTERM> ... > "[" ... > "{" ... > <NUMBER> ... > <TERM> ... > "*" ... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 5807] Add collection code to circulation rules
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5807 --- Comment #7 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Olli-Antti Kivilahti from comment #6) > (In reply to Christopher Davis from comment #3) > > (In reply to Lisette Scheer from comment #2) > > > > Hear here to what Lisette said. If an item looks like a book, acts like a > > book, and feels like a book, call it a book, not a "New Book" or a "History > > Center Material" because that is the only way we can control its circulation. > > > > Thank you. > > > > This is a big pain point for us too. Typically different locations in the > library have different circulation rules, such as "reference shelf", which > can contain all kinds of library materials, but need to be made available > for daily loans. Yeah I just had a librarian bring this up now. Really we need an overhaul of how the circulation and fines rules work. Probably would make sense to have them as rule sets (ie policies) and then attach them based on criteria (e.g. library, patron category, item type, collection code, etc). -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 42534] New: wrapper-staff-tool-plugin.inc interferes with js and includes in template files
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42534 Bug ID: 42534 Summary: wrapper-staff-tool-plugin.inc interferes with js and includes in template files 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Wrapper changes in Bug 42163 to support the vue changes made in Bug 41367 means you can't use a separate [% MACRO jsincludes BLOCK %] in plugins. Additionally if you're using any includes (such as datatables.inc) they no longer load because the wrapper [% MACRO jsincludes BLOCK %] overrides any inline [% MACRO jsincludes BLOCK %] You can use [% INCLUDE datatables.inc %] outside the wrapper, but most examples have it inside and I fear plugins using the wrapper will break on an update to 26.05. You can also put your <script> after the wrapper for loading it. We could try and make changes to the plugin structure/wrapper to make this work a little smoother. We could add common includes like datatable, calendar, select2, etc into the wrapper, but that seems like a long term maintenance issue. Another way could be to undo the vue change/figure out another way to load the admin menu or otherwise contain it so it's not overriding in page [% MACRO jsincludes BLOCK %] This would be the least disruptive for existing plugins, so is probably the way to go, but I'm not sure there's a good way to handle this. I'm very open to ideas about how to best handle this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 24172] New: Locale is ignored when saving season/month/day name in the database
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24172 Bug ID: 24172 Summary: Locale is ignored when saving season/month/day name in the database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials 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: colin.campbell(a)ptfs-europe.com Hi All, it seems the locale is completely ignored when creating numbering with season/month/day names. What I'm getting on master is that the season name is saved in English in the database, ignoring the locale completely, and depending on the page, the season name will be translated or not for display purposes in the staff interface language. (Steps 1-4 of the test plan are related to bug #20511, but I feel they are related since both have to do with locale being ignored.) Here's what I did : 0- Make sure you have at least one language other than English installed 1- With staff interface in English, create a subscription with a seasonal numbering pattern and frequency, with locale in your other language 2- Check the prediction pattern, note that the season names are in English not the locale language 3- Change the staff interface to other language, redo the prediction pattern test with locale in other language, note that the season names are in other language 4- Save the subscription 5- Receive an issue, note that the season name in the "Numbered" column on serials-edit.pl is in English 6- Save your issue 7- Switch interface in other language 8- Note that the season name on serials-collection is in other language 9- If you check the database, you will see the season name is in English, even though the subscription.locale is something else Navigating through different pages, here's what I noticed: - serials-collection.pl: display is translated - serials-edit.pl: name pulled directly from db - subscription-detail.pl: name pulled directly from db - detail.pl: name pulled directly from db - opac-detail.pl: name pulled directly from db I think the locale should be used when saving the season name in the db ensuring all displays are the same and in accordance with the option specified when creating the subscription. P.S. I'm not sure it has anything to do with it, but I noticed when choosing "French" as locale, the value saved in the db (subscription.locale) is "fre" and not "fr-FR" or "fr-CA". Would that have to do with Koha not being able to find the right translations? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 126

[Bug 17677] New: Move C4::Circulation code to the Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17677 Bug ID: 17677 Summary: Move C4::Circulation code to the Koha namespace Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 42530] New: Label template should allow any of the barcode types
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42530 Bug ID: 42530 Summary: Label template should allow any of the barcode types Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Only 6 of the 12 available barcode types available in /barcode-print.pl are available in the label layouts /label-edit-layout.pl We should allow the use of any printable barcode types in the labels. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36502] New: Independent branches should not prevent holds if canreservefromotherbranches is enabled
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36502 Bug ID: 36502 Summary: Independent branches should not prevent holds if canreservefromotherbranches is enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Libraries with IndependentBranches enabled would still like to place holds on items from other branches if they have canreservefromotherbranches enabled as well. -- You are receiving this mail because: You are watching all bug changes.

1 10