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

[Bug 36391] New: There is no listing of the cron job : archive_purchase_suggestions 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=36391 Bug ID: 36391 Summary: There is no listing of the cron job : archive_purchase_suggestions in the manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There is no listing of the cron job: archive_purchase_suggestions in the current manual. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37851] New: Add ability to edit facet labels in Elastic Search Facet Order
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37851 Bug ID: 37851 Summary: Add ability to edit facet labels in Elastic Search Facet Order Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently the label that is displayed is a database table name. The display is the same in the OPAC and Staff Interface. It would be nice to edit the facet label so the library can customize and add user friendly language. It would also allow the library to have nicer formatting, like consistent capitalization. Translations could be a factor, but could be added later. Right now, labels like 'ln' or 'su-geo' don't make much sense to the average user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 36604] New: Document what statistics wizards actually count
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36604 Bug ID: 36604 Summary: Document what statistics wizards actually count Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I find the statistic wizards very opaque and it's not clear at all what they actually count. I often have questions about them from clients, especially when libraries are doing their end-of-year statistics. I try to read the SQL in the .pl as best as I can, but it would be great if we could describe what each option in each wizard does in the manual. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[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

[Bug 38632] New: holdings table - all columns shown when displaying the filters
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '25

19 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38632 Bug ID: 38632 Summary: holdings table - all columns shown when displaying the filters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 38485 If we click on "Show filters" all the columns are shown. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38485 [Bug 38485] Update column visibility on holdings table correctly -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 38683] New: Opac cover images are only shown on fist result page
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '25

19 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38683 Bug ID: 38683 Summary: Opac cover images are only shown on fist result page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org When using cover images on the opac there is a strange behavior when there are more than 1 result pages. On the first result page everything works like expected, but on the subsequent result pages the cover images are not shown. to reproduce: - set system preference OPACAmazonCoverImages to show - open opac an search for "and" - the html structure for each result row is like: <td class="selectcol"></td> <td class="numcol"></td> <td class="covercol"></td> <td class="bibliocol"></td> - then go to the second result page and check that the row structure differs now <td class="selectcol"></td> <td class="numcol"></td> <td class="bibliocol"></td> -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 30254] New: New overdue fine applied to incorrectly when using "Refund lost item charge and charge new overdue fine" option in circ rules
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '25

19 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30254 Bug ID: 30254 Summary: New overdue fine applied to incorrectly when using "Refund lost item charge and charge new overdue fine" option in circ rules Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 23091 I've only confirmed this on 21.05. I haven't been able to replicate on master. When using the lost item fee refund feature to charge a new overdue fee when a lost item is found, Koha can end up creating an overdue fine on a patron who never actually had an overdue item. To recreate: - set Lost item fee refund on return policy to "Refund lost item charge and charge new overdue fine" - have an itemtype / patron combo that charges an overdue fine - check item out to patron and then right back in again - confirm patron doesn't have a fine because the item was not late - set the item to Missing - wait until after the item's due date from your previous checkout - check the item out to a new patron - confirm your original patron now has a fine When the item is checked out and Koha clears its missing status, it looks back for the most recent checkout in old_issues and generates an overdue fine as if that item had been checked out the whole time. Even though this item wasn't lost by a patron and the first patron never had an overdue fine on it. Things get more confusing if the first patron is anonymizing their reading history, as then the fine ends up on the anonymous borrower. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 [Bug 23091] Add options to charge new or restore forgiven overdues when a lost item is returned -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 21935] New: Setup sip accounts through front end
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '25

18 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21935 Bug ID: 21935 Summary: Setup sip accounts through front end Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Currently, it is necessary to setup an account in Koha for a sip connection and then do some setup for the same account on the backend (I do not know all the details). It would be great if there were a way to setup sip accounts via the patron account, that would eliminate the need to monkey with stuff on the backend. Ideally, it would be nice to have an area to setup sip accounts that is separate from regular patron accounts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4