September 2025 - Koha-bugs - lists.koha-community.org

[Bug 40275] New: Add Koha::Patrons->find_by_identifier()
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40275 Bug ID: 40275 Summary: Add Koha::Patrons->find_by_identifier() Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As suggested by Frido in some other context, I file this bug to introduce the mentioned sub. I resurrected the idea after tracking down some warnings in SIP, and identifying bug 36575 introduced them by calling `->find` without passing a primary key. This kind of errors/warns: ``` [2025/06/30 13:03:23] [24253] [ERROR] [undef]@[undef]: DBIx::Class::ResultSource::_minimal_valueset_satisfying_constraint(): Unable to satisfy requested constraint 'primary', missing values for column(s): 'borrowernumber' at /kohadevbox/koha/Koha/Objects.pm line 98 C4::SIP::Trapper::__ANON__ /kohadevbox/koha/C4/SIP/Trapper.pm (70) ``` Instead of solving it locally, I propose to introduce a sane and tested method, and reuse it anywhere this pattern is being used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 28761] New: Item status shows incorrectly on opac-course-details.pl
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28761 Bug ID: 28761 Summary: Item status shows incorrectly on opac-course-details.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - create a course in course reserves, add an item to it. - confirm your item shows Available for its status on opac-course-details.pl - give your item a notforloan status - reload opac-course-details.pl, confirm its still "available" - give your item a restricted user status - reload opac-course-details.pl, confirm its still "available" - give your item a lost, damaged, or withdrawn status - reload opac-course-details.pl, these statuses *are* reflected Filing a separate bug for the staff client. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 38804] New: erm : JSTOR usage data not harvestable via SUSHI
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38804 Bug ID: 38804 Summary: erm : JSTOR usage data not harvestable via SUSHI Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Trying to harvest JSTOR usage data via SUSHI returns an error in Koha job : "SUSHI returned: Warning - Report Queued for Processing 1011" This behavior is documented in Counter registry (https://registry.countermetrics.org/platform/335608df-e4d2-46ad-bd89-fb3683…) for JSTOR "The same report cannot be requested more than 5 times per day. JSTOR uses reporting queuing so if data is not yet available, clients will need to re-request the report at a later date." and in JSTOR site : https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUN… "Please wait at least one (1) hour between report requests to allow time for report files to be generated." I suppose other data provider may have the same policy. For Koha to be able to harvest them, it should be necessary to add an option to relaunch the harvesting process after a parametrable delay -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 30533] New: Add exact search option for patrons
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30533 Bug ID: 30533 Summary: Add exact search option for patrons 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A patron search for names like "JOHN JOHNSON" ends up getting parsed something like "WHERE surname like "%JOHN%" OR firstname like "%JOHN%" OR surname like "%JOHNSON%" OR firstname like "%JOHNSON%"" and finds a really unhelpfully large pile of patrons. Bug 17500 suggests implementing Elastic for patron searching, which would be great. In the meantime, we could give a little help for searches like this by giving an exact search option -- so the query would parse more or less the same but without the wildcards. That's also a problematic search for many situations, but would work better here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 31504] New: ElasticSearch No indexing new records after upgrade
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31504 Bug ID: 31504 Summary: ElasticSearch No indexing new records after upgrade Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es After upgrading koha 21.11 to 22.05 ElasticSearch is not able to index new records. At webadmin we can see the warning 'Index 'koha_xxxxxx' needs to be recreated.' Executing 'Reset mapping' button doesn't fix the error... when trying to full reindex with option -d or -r it doesn't work admin@___21:~$ sudo koha-elasticsearch --rebuild -d ___ sudo: unable to resolve host ___21: Name or service not known sudo: unable to resolve host ___21: Name or service not known Use of uninitialized value $reason in concatenation (.) or string at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 283. Exception 'Koha::Exception' thrown 'Unable to update mappings for index "koha_____biblios". Reason was: "". Index needs to be recreated and reindexed' Something went wrong rebuilding indexes for ___ Removing the index directly at ElasticSearch doesn't works * ElasticSearch is not localhost -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 31200] New: Block payment of late fees when document not return
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '26

08 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31200 Bug ID: 31200 Summary: Block payment of late fees when document not return Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: julie.emond(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, A library would like to be able to block any payment of late fees if materials are not returned to the library. As this could have undesirable effects it should be possible to make changes in the system preference and not be blocked for everyone. Does anyone know a way to enforce this preference? Another possibility would be to display a pop-up during payment so that the person who wants to collect knows that the document has not been returned. After the libraby chooses if it want accept of not the payment. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 40082] New: PatronDuplicateMatchingAddFields isn't respected in the OPAC or the API
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '26

06 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40082 Bug ID: 40082 Summary: PatronDuplicateMatchingAddFields isn't respected in the OPAC or the API Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There is a syspref for checking new patrons for duplicates that is only implemented in the staff interface - it should also be respected when adding a patron via the API or the OPAC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 40104] New: Patron circ message attention should also note ILLs ready for checkout
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '26

06 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40104 Bug ID: 40104 Summary: Patron circ message attention should also note ILLs ready for checkout Change sponsored?: --- Product: Koha Version: Main Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P1 - high Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com If a library is using the ILL module + CirculateILL, items that are ready for checkout should have a notification in patron circ message attention box a la Holds waiting for pickup so that front-line staff can let them know an item is available to check out. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 19745] New: Add Edit button for all the boards in circulation and fines rules
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '26

06 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19745 Bug ID: 19745 Summary: Add Edit button for all the boards in circulation and fines rules 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: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be usefull to have an "edit" button for all the boards in the circulation and fines rules. At this moment, the four last boards don't have an edit button and its not pratical. For those boards, we have to delet a rule to add a new one and now edit the rule. It would be great if there was a button all the same. Especially for a question of standardization with the rules of the first block. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 39651] New: Lock iType Column for Better Editing Circ Rules Table
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '26

06 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39651 Bug ID: 39651 Summary: Lock iType Column for Better Editing Circ Rules Table Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jjayne(a)luzernelibraries.org QA Contact: testopia(a)bugs.koha-community.org Suggestion to lock the itype column (circulation and fine rules) in place to better administer changes across the table. Maybe also have the editing line land just under the row being edited instead of all the way at the bottom? If this is repetitive or available in a newer version, my apologies. I couldn't find an existing bug that addressed this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11