October 2023 - Koha-bugs - lists.koha-community.org

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

[Bug 34091] New: Typo in help for cleanupdatabase.pl: --log-modules needs to be --log-module
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34091 Bug ID: 34091 Summary: Typo in help for cleanupdatabase.pl: --log-modules needs to be --log-module Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Found testing in 22.11, but I believe also present in current versions. The help reads: --log-modules Specify which action log modules to trim. Repeatable. But the parameter is actually --log-module -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 34644] New: Add text to sysprefs indicate that MarcFieldsToOrder is not used if MarcItemFieldsToOrder is populated
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34644 Bug ID: 34644 Summary: Add text to sysprefs indicate that MarcFieldsToOrder is not used if MarcItemFieldsToOrder is populated Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the code for addorderiso2709.pl we only use the fields form MFTO if MIFTO is not populated. This is not clear when setting things up -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 35073] New: Serials batch edit deletes unchanged additional fields data
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35073 Bug ID: 35073 Summary: Serials batch edit deletes unchanged additional fields data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: julian.maurice(a)biblibre.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, oleonard(a)myacpl.org Depends on: 18426 To reproduce, k-t-d: Preparation - Additional fields: 1) Add a new 'additional field', visit: /cgi-bin/koha/admin/additional-fields.pl 2) Click 'subscription' and '+ New field'. Enter a 'name' and hit 'save'. Serials: 1) Add a new serial, visit: /cgi-bin/koha/serials/subscription-add.pl 2) Put a biblionumber in the 'record' field, i.e. '112'. Press 'next' and click 'ok' on the alert box 3) Fill all the required fields and click 'test prediction' 4) Input something in the additional field created previously. 5) Click 'save subscription'. Notice the additional field is as expected. 6) Repeat steps 1-5 to create a second serial. Batch edit: 1) Visit serials and hit the 'Search' button: /cgi-bin/koha/serials/serials-home.pl 2) Click the 2 checkboxes for the 2 serials we created previously and click the new link that pops up 'edit selected serials'. 3) Click 'Save' without changing anything. 4) Go back to either of the serials, notice the value for the additional field is gone. Visit: /cgi-bin/koha/serials/subscription-detail.pl?subscriptionid=1 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18426 [Bug 18426] Subscriptions batch editing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 32312] New: Complete database column descriptions for serials module in guided reports
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32312 Bug ID: 32312 Summary: Complete database column descriptions for serials module in guided reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 29695 There are entries missing for the statistics table. How to test: * Add a new guided report * Select module serials * Verify that statistics is missing some descriptions, only showing the database value Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29695 [Bug 29695] Centralize columns' descriptions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 35111] New: Background jobs worker crashes on SIGPIPE when database connection lost
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35111 Bug ID: 35111 Summary: Background jobs worker crashes on SIGPIPE when database connection lost Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Typically, if Koha loses a connection to the database, it will automatically reconnect. We expect the background jobs worker to do the same thing. However, I've noticed that instead of reconnecting it crashes with an error like this in the worker-error.log: 20231018 07:44:06 instance-koha-worker-long_tasks: client (pid 3949888) killed by signal 13, respawning Signal 13 is a SIGPIPE and you will encounter that when you're trying to write to a socket that is no longer connected. Starman is based on Net::Server::PreFork which - like a lot of daemon software - ignores SIGPIPE. So if you restart the database and Starman loses its persistent connections, it will reconnect and ignore the SIGPIPE error. If you restart the database or you have a database connection timeout[1], the background jobs worker won't ignore the SIGPIPE. It'll die on it, and it will leave a background job in a stuck state. [1] Oct 19 02:24:02 awesome-host mariadbd[959]: 2023-10-19 2:24:02 6432 [Warning] Aborted connection 6432 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 34735] New: Current/disabled links in breadcrumbs are styled differently when in ERM module
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34735 Bug ID: 34735 Summary: Current/disabled links in breadcrumbs are styled differently when in ERM module Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: lucas(a)bywatersolutions.com CC: jonathan.druart+koha(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 If you look at the breadcrumb describing the current page you are on it is typically a light grey. In the ERM module those same breadcrumbs are black. -- You are receiving this mail because: You are watching all bug changes.

1 28