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

[Bug 40052] New: there should be a Zebra restart button in system admin in About Koha when it says it is not running
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40052 Bug ID: 40052 Summary: there should be a Zebra restart button in system admin in About Koha when it says it is not running Change sponsored?: --- Product: Koha Version: 22.05 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: dwight(a)wwwalker.com.au QA Contact: testopia(a)bugs.koha-community.org When OPAC "search the catalog" was not returning any search results, I logged in at the staff interface, I looked in About Koha and it said Zebra was not running. Currently I had to Google the command to find how to restart Koha Zebra when it was not running and no OPAC searches were working. I should be able to press a button near that status called "Restart Zebra" and it should do it for me instead of me fiddling for hours to restart Zebra by hunting through documentation to find the correct command and doing it as root at the command prompt on my Linux server. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40207] New: Bad redirection after Batch item deletion
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40207 Bug ID: 40207 Summary: Bad redirection after Batch item deletion Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 183398 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=183398&action=e… Example of the bug After deleting a batch of items, I clicked on the "Batch item deletion" button, at the top of the page, and am directed to the "Batch item MODIFICATION" page (Example URL : https://dev.koha.ca/cgi-bin/koha/tools/batchMod.pl) I should instead be redirected to the "Batch item DELETION" page (Example URL : https://dev.koha.ca/cgi-bin/koha/tools/batchMod.pl?del=1) The redirect URL should be changed for : https://dev.koha.ca/cgi-bin/koha/tools/batchMod.pl?del=1 See the attached video for the example. Tested in version 24.05 and 25.05. Test plan : 1. Go to the cataloging module. 2. Click on "Batch item deletion" button 3. Copy a barcode into the "Barcode list" box. 4. Click on "Continue" button 5. Click on "Delete selected items" button 6. Click on "Batch item deletion" button at the top of the page 7. Notice that you have been redirected to "Batch item modification" and not "Batch item deletion". I also tested the button for "Batch RECORD deletion" and it redirects us to the correct page : "Batch record deletion" (https://dev-intranet.koha.collecto.ca/cgi-bin/koha/tools/batch_delete_recor…) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 30650] New: Convert the Curbside Pickup plugin to Koha core
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 Bug ID: 30650 Summary: Convert the Curbside Pickup plugin to Koha core Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: new feature Priority: P5 - low Component: Circulation Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The plugin is great and people would like to see it part of Koha. https://github.com/bywatersolutions/koha-plugin-curbside-pickup -- You are receiving this mail because: You are watching all bug changes.

1 203

[Bug 40195] New: Make option to configure additional fields as date
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40195 Bug ID: 40195 Summary: Make option to configure additional fields as date Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu Bug 32610 added the option to patron attributes to indicate that a field is a date, resulting in the date widget to be displayed and the date to be validated as a date on entry. It would be great if additional fields could also be configured as dates. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 37180] New: Merge 'additional_fields' and 'borrower_attributes' features together
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37180 Bug ID: 37180 Summary: Merge 'additional_fields' and 'borrower_attributes' features together 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The generalised additional fields and the more specific borrower attributes features overlap in a lot of ways. We should consider merging them to DRY out the codebase and allow us to enhance both area's once rather than having to replicate code each time we want to enhance their functionality. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 34947] New: Koha Manual search does not bring user to the relevant place in the page
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34947 Bug ID: 34947 Summary: Koha Manual search does not bring user to the relevant place in the page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When clicking on a result in the Koha Manual search, the user lands at the top of the page rather than where the keyword appears. This is very unhelpful. Users are having to either do a "search within page" after clicking on the result; or run their search from a separate search engine in order to get to the relevant section in the Manual page. To replicate the issue: 1) Go to the Koha Manual, e.g. https://koha-community.org/manual/latest/en/html/index.html 2) In the search box, enter "on shelf holds". 3) Click on either of the first three results (Administration, Cataloging, Circulation). 4) Observe that you always land at the top of the page rather than where the search keywords first appear. Is there anything that can be done to improve this, please? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37454] New: MARC Framework test error message needs more explanation
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37454 Bug ID: 37454 Summary: MARC Framework test error message needs more explanation 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: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Ran the MARC bibliographic framework test on a site with 11 frameworks and the test returned all OK except for one. I received an error for the biblio and biblionumber test with: "The biblio.biblionumber and biblioitems.biblioitemnumber fields be mapped to a MARC subfield," I interpreted this to mean the 999$c and 999$d are not mapped. But the Koha to MARC mapping does show the fields are mapped. Checking the frameworks, the 999$c and 999$d are set to ignore. I have checked other sites where this error does not appear and the 999$c and 999$d are configured exactly the same. Some additional clarity or explanation is needed to understand this message. It does not appear the message is actually referring to the 999$c or 999$d, but something else. Because the message is non-specific and providing an incorrect reference, it is very difficult to comb through each framework, tag, and subfield to find the actual error. The error message also does not seem to be an obvious blocker. There are sites operating, without apparent data problems, with this error. Related to bug 18576 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37568] New: Explain category types in the manual
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37568 Bug ID: 37568 Summary: Explain category types in the manual Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the manual section on patron categories, the section on category types ("Adult", "Child", "Staff"... etc.) is unclear on what the category types actually do. It would be good to document what selecting a specific category type actually does for the patrons created using this category type. Manual page: https://koha-community.org/manual/latest/en/html/administration.html#patron… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 37696] New: Improve perldoc for SIP server
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37696 Bug ID: 37696 Summary: Improve perldoc for SIP server Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The perldoc for C4/SIP/SIPServer.pm gives off a style warning as per bug 37087#13 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36344] New: Add schema changes summary to release notes
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36344 Bug ID: 36344 Summary: Add schema changes summary to release notes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org The community release notes have summaries at the end for new and deleted system preferences and new authorised values and letter codes but none for schema changes. A list of new/deleted tables and one for new/renamed/deleted columns in tables would be useful. For example, issues.renewals became issues.renewals_count in 21.11 but this change was buried in bug 30275 (and reports broke as we missed mention of the change). And the schema change in bug 26057 altered the meaning of ‘missing in transit’ as we had defined it in our MIT reports (so they broke too). Schema changes are now included in our ‘upgrade pain-points’ and we will look very closely at them. A summary of the changes would be very useful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2