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

[Bug 38894] New: Longoverdue cron should follow HomeOrHoldingBranch as well as CircControl when using --library flag
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '25

19 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38894 Bug ID: 38894 Summary: Longoverdue cron should follow HomeOrHoldingBranch as well as CircControl when using --library flag Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 9596 Marking this Critical as it will lead to circ rules getting applied in unexpected ways. Bug 9596 taught the longoverdue cron to limit by library, following the CircControl system preference. Elsewhere in circulation (due dates, fines, etc), when CircControl is set to "the item's library," then it is further modified by HomeOrHoldingBranch, which determines whether we mean "the item's home" or "the item's holding." Currently, if CircControl is set to "the item's library," it is *always* interpretted as the item's homebranch. This will not work for many libraries. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 [Bug 9596] Allow longoverdue.pl to be configured per library on the command line -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 39025] New: Update patron account templates to use old_issue_id
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '25

19 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39025 Bug ID: 39025 Summary: Update patron account templates to use old_issue_id Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major 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: 22421 In Bug 22421 we created accountlines.old_issue_id to hold the issue_id of a finished issue in a way that folllows foreign key constraints. But in boraccount.tt and pay.tt we use issue_id to pull checkout information related to the fee. We need to update those templates to use old_issue_id where it exists. Currently any fee associated with a completed checkout will not show and due date, return date, etc. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22421 [Bug 22421] accountlines.issue_id is missing a foreign key constraint -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[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

[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 36600] New: Add ability to print an import report
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36600 Bug ID: 36600 Summary: Add ability to print an import report 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 It would be nice to have an option to print/export an import report. It could contain the information that appears on the screen and other useful types of information. For example bug 21272 reports a data error about mismatched library codes. Other data issues should be able to be retained and reported on as well. A report could include: Job ID File name Status Progress Type Start/End times The data in the table of number of records added, ignored, replaced matching rules used, framework assigned Data error messages - such as records rejected due to data issues (missing itypes, etc.) There are probably other things. It would be nice to be able to retain some of this data when trying to troubleshoot an import failure. Right now, some of the data is lost/buried once navigating away from the screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[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