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

[Bug 28271] New: Add the ability to set a new lost status when a claim is resolved
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28271 Bug ID: 28271 Summary: Add the ability to set a new lost status when a claim is resolved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal 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 Depends on: 24279 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24279 [Bug 24279] Claims Returned does not work when set from moredetail.pl or additem.pl -- You are receiving this mail because: You are watching all bug changes.

1 40

[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 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 33793] New: Add method to define limited access to run reports
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33793 Bug ID: 33793 Summary: Add method to define limited access to run reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Currently a user with the execute_reports permission can run any report in the system. A library may wish for a given user to be able run some reports but not others. It would be great to have a mechanism for allowing limited reports access. Maybe something akin to the SubfieldsToAllowForRestrictedEditing preference? We could create ReportGroupsToAllowForRestrictedExecution, in which one selects groups of reports. We add a new execute_reports_restricted permission. A user with that permission can only run reports in the groups specified in the preference. Or maybe ditch the system preference and add a "restricted access" flag to each report? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 32610] New: Add ability to specify patron attribute as a date and apply flatpickr
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32610 Bug ID: 32610 Summary: Add ability to specify patron attribute as a date and apply flatpickr Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Sometimes libraries use patron extended attributes that are dates. It would be handy if we could specify that a particular attribute is a date and then have it become a flatpickr instance. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 94

[Bug 34301] New: Agreements_spec.ts is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '25

19 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34301 Bug ID: 34301 Summary: Agreements_spec.ts is failing randomly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 25551 koha_1 | Running: ERM/Agreements_spec.ts (1 of 6) koha_1 | [11894:0713/195038.469535:ERROR:cert_verify_proc_builtin.cc(681)] CertVerifyProcBuiltin for redirector.gvt1.com failed: koha_1 | ----- Certificate i=0 (OU=Cypress Proxy Server Certificate,O=Cypress Proxy CA,L=Internet,ST=Internet,C=Internet,CN=redirector.gvt1.com) ----- koha_1 | ERROR: No matching issuer found koha_1 | koha_1 | koha_1 | [11894:0713/195039.293777:ERROR:cert_verify_proc_builtin.cc(681)] CertVerifyProcBuiltin for r2---sn-4g5ednsd.gvt1.com failed: koha_1 | ----- Certificate i=0 (OU=Cypress Proxy Server Certificate,O=Cypress Proxy CA,L=Internet,ST=Internet,C=Internet,CN=r2---sn-4g5ednsd.gvt1.com) ----- koha_1 | ERROR: No matching issuer found koha_1 | koha_1 | koha_1 | Browserslist: caniuse-lite is outdated. Please run: koha_1 | npx browserslist@latest --update-db koha_1 | koha_1 | Why you should do it regularly: koha_1 | https://github.com/browserslist/browserslist#browsers-data-updating koha_1 | <?xml version="1.0" encoding="UTF-8"?> koha_1 | <testsuites name="Mocha Tests" time="38.2310" tests="5" failures="1"> koha_1 | <testsuite name="Root Suite" timestamp="2023-07-13T19:50:41" tests="0" file="t/cypress/integration/ERM/Agreements_spec.ts" time="0.0000" failures="0"> koha_1 | </testsuite> koha_1 | <testsuite name="Agreement CRUD operations" timestamp="2023-07-13T19:50:41" tests="5" time="38.2310" failures="1"> koha_1 | <testcase name="Agreement CRUD operations List agreements" time="11.1430" classname="List agreements"> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Add agreement" time="15.8900" classname="Add agreement"> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Edit agreement" time="0.0000" classname="Edit agreement"> koha_1 | <failure message="Timed out retrying after 5000ms: `cy.wait()` timed out waiting `5000ms` for the 1st request to the route: `get-single-agreement-search-result`. No request ever occurred. koha_1 | koha_1 | https://on.cypress.io/wait" type="CypressError"><![CDATA[CypressError: Timed out retrying after 5000ms: `cy.wait()` timed out waiting `5000ms` for the 1st request to the route: `get-single-agreement-search-result`. No request ever occurred. koha_1 | koha_1 | https://on.cypress.io/wait koha_1 | at cypressErr (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Object.errByPath (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at checkForXhr (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:… koha_1 | at tryCatcher (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Function.Promise.attempt.Promise.try (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at whenStable (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:… koha_1 | at tryCatcher (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Promise._settlePromiseFromHandler (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Promise._settlePromise (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Promise._settlePromise0 (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Promise._settlePromises (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at Promise._fulfill (http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:…) koha_1 | at http://kohadev-intra.mydnsname.org:8081/__cypress/runner/cypress_runner.js:… koha_1 | From Your Spec Code: koha_1 | at Context.eval (http://kohadev-intra.mydnsname.org:8081/__cypress/tests?p=t/cypress/integra…)></failure> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Show agreement" time="6.0050" classname="Show agreement"> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Delete agreement" time="5.1930" classname="Delete agreement"> koha_1 | </testcase> koha_1 | </testsuite> koha_1 | </testsuites> Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25551 [Bug 25551] [OMNIBUS] Some tests are failing randomly -- You are receiving this mail because: You are watching all bug changes.

1 5