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

[Bug 35702] New: Reduce DB calls when performing authorities merge
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35702 Bug ID: 35702 Summary: Reduce DB calls when performing authorities merge Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We are individually fetching each biblio, we can do this in a single call We also fetch the frameworkcode from the DB for each biblio - we can just use the field from the object we have already fetched -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 35086] New: Koha::SearchEngine::Elasticsearch::Indexer->update_index needs to commit in batches
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35086 Bug ID: 35086 Summary: Koha::SearchEngine::Elasticsearch::Indexer->update_ind ex needs to commit in batches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com As we have moved tasks into the background we have updated code to send a single background request for indexing - so if a library modifies several thousand biblios we send the full list for reindexing. update_index needs to ensure the size of the requests does not exceed the limits of ES or take up too many resources. We should provide a configurable (syspref? kconf switch?) limit for each indexing request -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 34999] New: REST API: Typo error instead of message
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34999 Bug ID: 34999 Summary: REST API: Typo error instead of message Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 25835] New: Include Overdue Report (under Circulation Module) as a Staff Permission
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25835 Bug ID: 25835 Summary: Include Overdue Report (under Circulation Module) as a Staff Permission Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, when setting up permission for staff, the report for Overdue reports portion of the Circulation module, is only partially included in staff permission. There is a permission that allows staff to run the Overdue report )Execute overdue items report (overdues_report)) - but this does prohibit the Overdue report from displaying on circulation page, but the Overdue with Fines does display. It would more helpful, if this permission included both reports or add another permission to allow libraries to include/exclude this other report. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 32551] New: API requests don't carry language related information
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32551 Bug ID: 32551 Summary: API requests don't carry language related information Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: tomascohen(a)gmail.com During our ILL development we noticed that there are issues with translations and the API. Using the C4::Languages::getlanguage method from the API controller is not working because the cookies is not passed and the environment variables are lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 35696] New: Transit status not properly updated for items advanced in Stock Rotation tool
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35696 Bug ID: 35696 Summary: Transit status not properly updated for items advanced in Stock Rotation tool Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 160507 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=160507&action=e… Transit status of stock rotation items 23.05.06 While using the stock rotation tool in the Cataloging module, when items in rotas are advanced to the next stage, the status is not updating properly. In a proper status update for advancing items, the status reads "Transit pending from XX branch to YY branch since mm/dd/yyyy" which displays in 22.11.10. In 23.05.06, the status updates to show "Transit is pending from XX branch to YY branch since Available". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 35629] New: Redundant code in includes/patron-search.inc
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35629 Bug ID: 35629 Summary: Redundant code in includes/patron-search.inc Change sponsored?: --- Product: Koha Version: master 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart+koha(a)gmail.com, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, tomascohen(a)gmail.com Do a find for [% CASE 'name-address' %] you'll notice there are 2 identical entries with the difference being me.othernames in "data". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 34575] New: Patron search results: Customise the fields displayed in Name column
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34575 Bug ID: 34575 Summary: Patron search results: Customise the fields displayed in Name column 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: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Since the staff interface redesign, the search patron results table is prone to breaking the width of the screen, causing a horizontal scrollbar to display. The Name column displays the following content: Patron name Patron address Email address The column is flexible, because the filter is a search. As there are spaces in the name/address content, the column can be a very small width on smaller monitors. But the email address is often very long - and this causes the Name column to be very wide. On our system, two of our own council email address domains are 30 characters in length - that's before you've added the prefix, so email addresses can easily be 50+ characters, making for a very wide column. Is it possible to create a setting where we can choose not to include the email address in the search results? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 28012] New: Error on Saving new numbering pattern
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28012 Bug ID: 28012 Summary: Error on Saving new numbering pattern 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: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I got an error after klicking on the Save button for saving a new numbering pattern. 1. go to the serials module 2. click on manage numbering patterns in the left hand navigation 3. add a pattern 4. Fill in the fields 5. Filling in the Numbering formula field leads to an error after saving. Leaving the numbering formula field blank, no error occurs, but the new pattern won't be saved it seems First lines of error trace: C4::Serials::Numberpattern::AddSubscriptionNumberpattern(): DBI Exception: DBD::mysql::st execute failed: Incorrect integer value: '' for column `koha_christian8`.`subscription_numberpatterns`.`displayorder` at row 1 [for Statement "INSERT INTO subscription_numberpatterns(label,description,numberingmethod,displayorder,label1,label2,label3,add1,add2,add3,every1,every2,every3,setto1,setto2,setto3,whenmorethan1,whenmorethan2,whenmorethan3,numbering1,numbering2,numbering3) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)" with ParamValues: 0="blablub", 1="blablubdescription", 2="{X}, H. {Y} {Z} ", 3="", 4="Jahr", 5="Jahrgang", 6="Heft", 7="1", 8="1", 9="1", 10="12", 11="6", 12="1", 13="1", 14="1", 15="1", 16="9999", 17="9999", 18="6", 19="", 20="", 21=""] at /kohadevbox/koha/serials/subscription-numberpatterns.pl line 62 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 31297] New: Cannot add new subscription patterns from edit subscription page
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31297 Bug ID: 31297 Summary: Cannot add new subscription patterns from edit subscription page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new subscription pattern from the edit subscription page, nothing happens when clicking on the bug. But we can see the following error from the API request: XHRGEThttp://localhost:8081/cgi-bin/koha/serials/create-numberpattern.pl?patternname=Test season with month&numberingmethod={X} {Y} {Z}&label1=Season&label2=Year&label3=Month&add1=1&add2=1&add3=1&every1=1&every2=4&every3=4&setto1=0&setto2=1&setto3=0&numbering1=season&numbering3=monthname&whenmorethan1=3&whenmorethan2=99999&whenmorethan3=11&locale=spa [HTTP/1.1 500 Internal Server Error 27ms] C4::Serials::Numberpattern::AddSubscriptionNumberpattern(): DBI Exception: DBD::mysql::st execute failed: Field 'description' doesn't have a default value at /kohadevbox/koha/serials/create-numberpattern.pl line 58 description is a field in the database, that can only be filled from the administration page for numbering patterns, but not from this screen. This has always been the case. Could this by a strict SQL error? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25