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 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 40867] New: Implement 2FA for the OPAC
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40867 Bug ID: 40867 Summary: Implement 2FA for the OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We have 2FA for the staff interface, it would be nice to have it for the OPAC too. It should probably be a separate options, so 2FA can be enabled/enforced separately for the staff interface and for the OPAC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #47 from Mathieu Saby <mathsabypro(a)gmail.com> --- There is still an issue that has come up in our discussions with Biblibre. I'll let Thibauld explain... -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Mathieu Saby <mathsabypro(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Comma delimited|UniversitÃ© CÃ´te d'Azur, |Université Côte d'Azur list of Sponsors|Université Côte d'Azur | -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 23456] New: Show 'date last seen' for items requested in Holds Queue
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23456 Bug ID: 23456 Summary: Show 'date last seen' for items requested in Holds Queue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 It would be very useful to view the contents of items.datelastseen in the Holds Queue. Ideally, this information would be presented in its own column so it could be sorted. Some fields from the items table are already called in the itemsloop, so it appears that the tables are already joined (e.g. items.barcode is already presented in the Holds Queue). This is something that our staff request repeatedly as it would help them to prioritise their searches in busy libraries (where the Holds Queue can run to hundreds of items). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11