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

[Bug 35903] New: In cataloguing authority plugin using autocomplete must set operator exact
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35903 Bug ID: 35903 Summary: In cataloguing authority plugin using autocomplete must set operator exact Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When cataloguing and using authority plugin, there is auto-completion on inputs and default operator is "contains". When using auto-completion and selecting a result it would be logical to set operator "exact" and submit form. So the usually unique result appears. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 40888] New: and/or/not drop-downs are missing in the Advanced Search form
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40888 Bug ID: 40888 Summary: and/or/not drop-downs are missing in the Advanced Search form Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Created attachment 186984 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=186984&action=e… Advanced search missing and/or drop-downs In the Advanced Search form, if "More options" is selected, each search field should have a drop-down to select between "and", "or", and "not" for that field. However, in 25.05 and main, that drop-down only appears in the first line. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 14962] Temp Shelving Location
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 Marie <marie.hedbom(a)musikverket.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marie.hedbom(a)musikverket.se -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41158] New: Field 001 replaced when importing records while using autoControlNumber system preference
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41158 Bug ID: 41158 Summary: Field 001 replaced when importing records while using autoControlNumber system preference Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Field 001 is replaced with records local biblionumber when importing records while using autoControlNumber system preference. This happens when using Z39.50 search/import and importing staged records. The manual tells about the system preference like this: "If set to ‘generated as biblionumber’, the control number will be filled with the biblionumber once the record is saved. This will not affect existing records that already have a value in 001. The existing value will be preserved." Replacing the 001 is not right because 001 should correspond to the value stored in field 003. The value in the field 001 is given by the cataloging agency marked in 003. Second problem is that if the 001 is replaced and the record has child records / component records, the connection between the host record and component record is lost. ShowComponentRecords system preference enables the linking component parts. >From the manual: "Components to be displayed are found using the host record’s control number (001) in the child record’s 773$w subfield" How to reproduce the problem with staging: 1. Activate autoControlNumber system preference 2. Find or create a bibliographic record which field 001 is not the records biblionumber. 3. Export the record using the Save button at the Normal view 4. Go to Cataloging -> Stage record for import -> Find the file you just saved 5. Stage the file with a rule to find matches (for example ISBN). If you do not have record matching rules, please make one in Administration -> Record matching rules. Choose to replace the record if match is found. 6. View the batch and check from the Diff column's link that 001 looks the same at this point. 7. Import the batch into the catalog. 8. Go to the record you just updated (or replaced) and click the MARC preview 9. Notice that the 001 field is replaced with records biblionumber How to reproduce by using Z39.50 (this is not a straight forward replacing like it seems to be in staging): 1. Activate autoControlNumber system preference 2. Find or create a bibliographic record which field 001 is not the records biblionumber. 3. Choose under the Edit button "Replace record via Z39.50/SRU" 4. Search for the title from a database that has the same title and choose to import it 5. You will be transferd to the record's editing page 6. Notice that field 001 is empty 7. If the cataloger does not notice the empty field, it will be filled with biblionumber upon saving the record. You can also try both ways while the autoControlNumber is not activated to notice the difference. If the autoControlNumber system preference is deactivated, the 001 stays the same in staging and in Z39.50 the 001 field is not emptied. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 41858] New: Patron messaging preferences: Interlibrary loan ready-notification is not sent to the patron as a print
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41858 Bug ID: 41858 Summary: Patron messaging preferences: Interlibrary loan ready-notification is not sent to the patron as a print Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: piia.semenoff(a)ouka.fi QA Contact: testopia(a)bugs.koha-community.org Patrons are not notified that their interlibrary loan is ready if SMS or email are not selected in the interlibrary loan messaging preferences. When you send the notice to a patron in the ILL requests, the message is not sent and you get a notification in a yellow box: The requested notice was NOT queued for delivery by email, SMS When this happens notification should go to a patron as a print instead. Hold filled-notifications go to a patron as a print even if patron hasn't selected SMS or email. Could Interlibrary loan ready -notification work the same way? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 41856] New: Grammar?
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41856 Bug ID: 41856 Summary: Grammar? Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I've stumbled on this while translating: Koha/Database/DataInconsistency.pm:349 The Framework *{frameworkcode}* is using the authorised value's category *{av_category}*, but the following {kohafield} do not have a value defined ({itemnumber => value }): {output} I wonder if it should be "does not have", but also if {kohafield} makes sense when it's replaced with the value. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 38192] New: DT - State not restored correctly on suggestion tables
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38192 Bug ID: 38192 Summary: DT - State not restored correctly on suggestion tables Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33426 There is one table per tab, the id of the table is table_N. Say you have: Pending (#table_1), Accepted (#table_2), Rejected (#table_3) The state will be stored in localStorage with the following key: DataTables_table_1_/cgi-bin/koha/suggestion/suggestion.pl DataTables_table_2_/cgi-bin/koha/suggestion/suggestion.pl DataTables_table_3_/cgi-bin/koha/suggestion/suggestion.pl If you move all the suggestions from Accepted to Rejected, a shift will give: Pending (#table_1), Rejected (#table_2) And the previous state from the "Accepted" tab will be used for "Rejected" Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33426 [Bug 33426] Add client storage of user-selected DataTables configuration to suggestion.tt -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 37530] New: Enhance the confirm cashup modal in the Point of sale module
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37530 Bug ID: 37530 Summary: Enhance the confirm cashup modal in the Point of sale module Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com When doing a cashup on the registers.pl page in the POS module, it would be helpful to be able to have specific information about the previous time period's sales before actually recording the cashup. Currently, when you perform the cashup the only information you get is how much money you should be removing from the register and how much of a float to leave. Although the table on the cash summary page gives some information, the modal gives no information about how much money you should have in cash, credit cards or checks. No information about refunds. No information about the actual debit types that were sold. This is critical information for us because we handle sales for three entities - the library, Friends of the Library and Library Foundation. There is a 'cashup summary' link in the 'last cashup' column which gives a nice breakdown of this type of information but that's for the last cashup you performed not the one you are about to do. In fact, when we were learning POS we kept expecting this info to match the sales we were about to cashup. A report (based on the current 'cashup summary' report ) of the transactions since the last cashup, along with the current information you get when clicking on the 'Record cashup' button would be helpful. The information could be presented on screen and allow printing prior to actually confirming the cashup. Another reason an enhanced 'Record cashup' modal would be helpful is that we have had to create customized reports to get this detailed information. If it could be presented during the cashup process we could print the information for our own records and send it to our Finance Dept. with our daily deposit. I've added a screenshot to offer more clarification. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 41855] New: Clarify and reorganize the user menu (usermenu.inc)
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41855 Bug ID: 41855 Summary: Clarify and reorganize the user menu (usermenu.inc) Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: matthias.berland(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org Is it possible to rearrange the user menu in the OPAC (usermenu.inc) with sub-menus/dropdowns? Especially when the library enables a lot of features and additional plug-ins, I find the menu heavy with information and not very user friendly. - Some elements of the lists are repetitive : Search history, Checkout history, Holds history, Recalls history. - Some elements have similar descriptions and/or are not clear : Privacy / Consents. - Elements benefit from logical subdivisions: placing actions the patrons need more frequently at the top, and rare actions at the bottom. Regarding accessibility, it would also benefit screen-reader users who can navigate from elements to sub-elements of the list to find directly what they are looking for instead of going through each element of the list every time. I think it could benefit all users who struggle with computers. An example of what I am thinking about : Summary Library card Charges Document requests and suggestions -----Interlibrary loan requests -----Curbside pickups -----Purchase suggestions Lists and tags -----Lists -----Tags -----Routing lists History -----Search history -----Checkout history -----Holds history -----Recalls history Settings -----Ask for discharge -----Change password -----Personal details -----Consents -> Personal data consents -----Messaging -> Messaging preferences -----Alert subscriptions -----Privacy -> History preferences and privacy -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 41853] New: OAuth2 Failed to warm up, name or service not known
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41853 Bug ID: 41853 Summary: OAuth2 Failed to warm up, name or service not known Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Every now and then we find the following error in plack-api-error.log [ERROR] [OAuth2] Failed to warm up https://mpass-proxy.csc.fi/.well-known/openid-configuration: Can't connect: Name or service not known It does not seem to be related to a request to /api/v1/ as we cannot find any requests from around that timestamp. At this point I don't know what exactly executes the warming up process and why the DNS resolution fails when otherwise OIDC authentication works just fine. Is it related to Koha, our Koha server, the DNS server we are using or the OIDC target server? Anyway in case someone else is experiencing the same issue, I thought it'd be useful to create a Bug for this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0