December 2024 - Koha-bugs - lists.koha-community.org

[Bug 23653] New: Plack stopped working - JSON validation timeout
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23653 Bug ID: 23653 Summary: Plack stopped working - JSON validation timeout Change sponsored?: --- Product: Koha Version: 19.05 Hardware: Other OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: rick_conrad(a)sil.org QA Contact: testopia(a)bugs.koha-community.org I had plack working fine before this morning, but now if I have plack enabled, Koha does not respond to web requests, and apache eventually shows me a 502. These are the entries from plack-error.log. I don't know what swagger.io is - seems there is such a website, but I can't `curl` it from the webserver, at least right now. plack-error.log ```` Error while loading /etc/koha/plack.psgi: Can't load application from file "/usr/share/koha/api/v1/app.pl": [JSON::Validator] GET http://swagger.io/v2/schema.json == Inactivity timeout at /usr/share/perl5/JSON/Validator.pm line 274. Compilation failed in require at (eval 389) line 1. Child process 3159 exited with status 255 ```` The only change I made this morning was changing the server's timezone, but I doubt that's related. I did put it back to UTC, but no improvement. Disabling plack works for me, but my site is a lot slower (and it wasn't real quick to begin with). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118

[Bug 28514] New: C4::Letters::getletter must be rewritten
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28514 Bug ID: 28514 Summary: C4::Letters::getletter must be rewritten Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 28487 The way we handle notice templates is confusing (see bug 27660, bug 26787, bug 28487). We should remove it and use Koha::Notice::Templates instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28487 [Bug 28487] Overdue_notices does not fall back to default language -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 28487] New: Overdue_notices does not fall back to default language
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28487 Bug ID: 28487 Summary: Overdue_notices does not fall back to default language Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org Previously overdue_notices use exclusively the default language but bug 26420 changed this to the opposite, which is to use exclusively the language chosen by the user. But if no translation have been provided for the chosen language, no message is sent. I would expect the behavior to be the same as in GetPreparedLetter: $letter = getletter( $module, $letter_code, $branchcode, $mtt, $lang ); unless ( $letter ) { $letter = getletter( $module, $letter_code, $branchcode, $mtt, 'default' ) or warn( "No $module $letter_code letter transported by " . $mtt ), return; } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 30198] New: Add privacy elements to reports
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30198 Bug ID: 30198 Summary: Add privacy elements to reports Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Any staff member who has access to run reports potentially has the ability to see data they are not typically permitted to view. It would be really helpful to be able to add limits to reports to restrict who has permission to view/run the reports. For instance, as a circulation clerk, I may need to run a report of patrons that have overdue items with holds on them, so I can contact the patron about returning the item. However, since I have the ability to view/run all reports, I potentially could access reports that have patron reading history, or financial info in them. Likewise, if I am in a consortium/multi-library setting, and do not have the permission to view patron data from other libraries, in the reports module I can run reports that contain patron data from any of the other libraries. I imagine something along the lines of funds access in acquisitions - owner, user, library, and being able to limit to any of those elements. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

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