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

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

[Bug 34784] New: Add ability to populate empty item callnumbers for a record based on the itemcallnumber syspref
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '25

18 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34784 Bug ID: 34784 Summary: Add ability to populate empty item callnumbers for a record based on the itemcallnumber syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries would like to auto-populate item callnumbers for items on a record based on the system preference "itemcallnumber". Only items with empty callnumbers would affected. This would add a button "Populate empty item callnumbers" on catalogue/detail.pl, as well as a "Populate callnumber" button for each line in the holdings table to set the callnumber for that specific item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 29743] New: Importing bad MARC can cause internal server errors in Koha
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29743 Bug ID: 29743 Summary: Importing bad MARC can cause internal server errors in Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org MARC data can be imported into Koha that may be invalid and can cause internal server errors when someone attempts to view that records. We should validate MARC data before it is imported into the database to prevent this issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34063] New: items.paidfor haunting beyond the grave
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '25

16 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34063 Bug ID: 34063 Summary: items.paidfor haunting beyond the grave Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Depends on: 26268 Bug 26268 only drops the column items.paidfor if the column is empty. If there is a value, a warning message is displayed, but the database upgrade completes successfully. So you may end up with 47 columns in your items table in Koha 22.11 while the deleteditems table only has 46 columns. This will cause scripts like /cgi-bin/koha/reports/issues_stats.pl to bust with a 500 error since it can't do a * union on those two tables with a different number of columns. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26268 [Bug 26268] Remove items.paid for once and for all -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 34481] New: Add IncludeSeeAlsoFromInSearches like IncludeSeeFromInSearches
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '25

16 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34481 Bug ID: 34481 Summary: Add IncludeSeeAlsoFromInSearches like IncludeSeeFromInSearches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Like IncludeSeeFromInSearches adds see from heading in search (4xx), add a system preference IncludeSeeAlsoFromInSearches to add see also from heading (5xx). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 18745] New: Serial claims: save supplier info on serial-level
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '25

16 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18745 Bug ID: 18745 Summary: Serial claims: save supplier info on serial-level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Serials Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 29167] New: Patron Search - Data Export
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '25

13 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29167 Bug ID: 29167 Summary: Patron Search - Data Export Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 125714 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=125714&action=e… Default number does not export all data A partner library noticed that when exporting data from a patron search (Address) that the export only exports what is showing in the search results. Previously when they exported it would export all data without having to select the "All" from the quantity dropdown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4