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

[Bug 42538] New: Patron account expiry message preference is shown and editable when creating new patron in category for which expiry notice is enforced
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42538 Bug ID: 42538 Summary: Patron account expiry message preference is shown and editable when creating new patron in category for which expiry notice is enforced Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 30301 To recreate: - edit a patron category to set 'Enforce patron account expiry notice' to Yes - create a new patron in that category - confirm that the expiry notice messaging preference is visible and editable in the patron creation screen - save your patron - confirm once the patron is created you can no longer see the account expiry notice in the messaging preferences while viewing or editing your patron If the intent here is to prevent any changes to this preference for patrons in the category, we should not be able to change the preference at creation. As suggested in Bug 40646, we could show the preference, have it enabled, and prevent changes. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30301 [Bug 30301] Add an option to specify the patron expiration notices as mandatory by patron category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

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

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #49 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Hello, As Mathieu said, I need to clarify a particular behaviour : Before this patch, when we perform an action to attach an item, if all items of a hold biblio were moved, the hold remained linked to the biblio; however, if that biblio was deleted, the hold would disappear. This fix changes the behaviour by moving the hold to the destination record provided that the last item has been moved. As this patch has now been signed off, I’d like to clarify the change in behaviour. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

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

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #198318|0 |1 is obsolete| | Attachment #198319|0 |1 is obsolete| | Attachment #198320|0 |1 is obsolete| | Attachment #198321|0 |1 is obsolete| | Attachment #198322|0 |1 is obsolete| | Attachment #198323|0 |1 is obsolete| | Attachment #198324|0 |1 is obsolete| | --- Comment #48 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 198664 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198664&action=e… Bug 6532: Way to move items to another record in batches This patch adds a new "Move items in a batch" feature, allowing to move multiple items from one bibliographic record to another in a single operation. Test plan: 1. Apply the patch and restart_all. 2. Open a record with at least 2 items (record A). Open or create a second record (record B). 3. On record A: Edit -> "Move items in a batch". Select 1 item, enter record B's biblionumber, submit. => Job finishes. The item appears on record B, not on record A. 4. Repeat with "Delete source bibliographic records if no items remain" checked and move the last item of record A. => Job finishes. Record A is deleted. 5. Place a biblio-level hold on a record with 2 items (record C). Go to Edit -> "Move items in a batch". => A warning icon appears on each item explaining that biblio-level holds will follow if no items remain. 6. Move only 1 item of record C to record B. => The biblio-level hold stays on record C (still has 1 item). 7. Move the last item of record C to record B. => Job report warns that the biblio-level hold has been automatically transferred to record B. => Confirm: record B now has the hold, record C has none. 8. You can test also with hold at item level. Hold simply follows the item on the new record linked. 9. Try entering a non-existent biblionumber as destination. => Error shown before the job is enqueued. Sponsored-by: Université Côte d'Azur Current status: Signed Off -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[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 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