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

[Bug 38381] New: Item/bib information isn't retained if an item linked to a manual invoice is deleted
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '25

08 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38381 Bug ID: 38381 Summary: Item/bib information isn't retained if an item linked to a manual invoice is deleted Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a manual invoice is charged to a patron's account with a link to an item using the Barcode field, and then the item (or both item and bib) is later deleted, the bib and item info disappears from the charge. This differs from lost charges, where if a lost item (or item and bib) is deleted, the title and barcode remain in the patron's transaction history. The behavior should match. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28551] New: Add ability to limit gather_print_notices by patron category
by bugzilla-daemon＠bugs.koha-community.org 07 Mar '25

07 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28551 Bug ID: 28551 Summary: Add ability to limit gather_print_notices by patron category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be great if gather_print_notices could be run with a list of patron categories to include/exclude. I'm imagining one new flag for an allowlist and another new flag for a deny list. The use case at hand is a library that wants to mail printed Hold Available notices to some but not all patrons. HOLD notices generate as print by default, so there's no way to simply turn them off for patrons in the category that should not receive them. A new flag in the gather_print cron would allow us to at least stop emailing them to the library along with the HOLD notices they do want. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39117] New: Terms and ocnditions of Use
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '25

06 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39117 Bug ID: 39117 Summary: Terms and ocnditions of Use Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: library(a)smoeast.com QA Contact: testopia(a)bugs.koha-community.org There is a feature for having it require you to agree to privacy policy, can this be made for terms and conditions of use because google requirres this when setting up log in with google on the OPAC -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 29859] New: Favor iterators over as_list
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '25

06 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29859 Bug ID: 29859 Summary: Favor iterators over as_list Change sponsored?: --- Product: Koha Version: unspecified 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: 29844 On bug 29844 we decided to remove wantarray from Koha::Objects->search. Reviewing the difference occurrences I found some unnecessary uses of ->as_list, where iterators should be used instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29844 [Bug 29844] Remove uses of wantarray in Koha::Objects -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 27618] New: Don't show dropdown if PatronSelfRegistrationLibraryList only has one library
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '25

06 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27618 Bug ID: 27618 Summary: Don't show dropdown if PatronSelfRegistrationLibraryList only has one library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Depends on: 16274 If PatronSelfRegistrationLibraryList only has one library code in it, that one library is still shown as a dropdown with one choice. It would be better if the code was in a "hidden" form input and the "Home library" was just shown as text, or not shown at all. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16274 [Bug 16274] Make the selfregistration branchcode selection configurable -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 38214] New: Audit use of TT url filter for uses that should be uri instead
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '25

06 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38214 Bug ID: 38214 Summary: Audit use of TT url filter for uses that should be uri instead Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Shame the two things look so much alike in so many fonts, when you have old eyes. The url filter is for filtering a full URL, when you don't want to escape : or // since starting a URL with http%3A%2F%2F won't work well. The uri filter is for filtering a URL parameter, where you want '/search?query=why%3F' rather than '/search?query=why?' which breaks your URL by having a second '?'. Using url when you should use uri means you are leaving &, @, /, ;, :, =, +, ? and $ unescaped when you shouldn't. In many cases, the wrong use of url is on things like biblionumber, where that doesn't result in any interesting behavior, but in other cases... you can create an authorized value category named This&That=Stuff, and when you try to add a value to it, you will add a value to the category This, and pass the parameter That with the value Stuff to the script. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 38719] New: ILL : display in the request the name of the partner library providing the document
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '25

06 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38719 Bug ID: 38719 Summary: ILL : display in the request the name of the partner library providing the document Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com When you request a document from a partner, the request status become "Requested from partners" and the partner email is displayed. The name of the partner should be displayed too -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36779] New: Automatic renewal column doesn't always populate correctly when editing
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '25

05 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36779 Bug ID: 36779 Summary: Automatic renewal column doesn't always populate correctly when editing Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If I'm editing a rule with Yes in the 'Automatic renewal' column and then select to edit a different rule that has No in the 'Automatic renewal' column without saving the first rule, Yes 'sticks'/remains populate for the second rule. To recreate: 1. Select Edit on a rule with Yes in 'Automatic renewal'. Note that Yes populates (as it should) in the editing line. 2. Without saving any changes to the rule selected above, click Edit on a rule with No in the 'Automatic renewal' column. Note that Yes still shows in the 'Automatic renewal' column, even though other values have populated from the second rule you selected to edit. If a library doesn't notice this, they could accidentally set rules for automatic renewal when making other unrelated edits. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 33361] New: Renewals prevented on items where there is an item level hold on another item on the record
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '25

05 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33361 Bug ID: 33361 Summary: Renewals prevented on items where there is an item level hold on another item on the record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: Ability to override holds is needed Find/create a record with 2 items Checkout item A to a patron Place an item level hold on B for another patron Item A cannot be renewed Override renewal to renew the item It gives you a new due date but doesn't actually update the item. This also happens with autorenewals being blocked when there is an item level hold on another item on the record. Lisette -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 28781] New: Elasticsearch facets may be inaccurate
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '25

05 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28781 Bug ID: 28781 Summary: Elasticsearch facets may be inaccurate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com To recreate: 1 - Set system preferences: SearchEngine: Elasticsearch FacetMaxCount: 20 displayFacetCount: Show 2 - Using koha testing docker default data search for '*' 3 - Note the author facets like Beckett, Samuel (5) Aristophanes (3) De Niese, Danielle (3) Euripides (3) Aristotle (2) 4 - Set FacetMaxCount:400 5 - Repeat search 6 - Note facets like: Beckett, Samuel (5) Stevens, W. Richard (5) Plato (4) Aristophanes (3) De Niese, Danielle (3) 7 - Some top terms are missing when FacetMaxCount is passed to ES as 'size' >From the docs: The size parameter can be set to define how many term buckets should be returned out of the overall terms list. By default, the node coordinating the search process will request each shard to provide its own top size term buckets and once all shards respond, it will reduce the results to the final list that will then be returned to the client. This means that if the number of unique terms is greater than size, the returned list is slightly off and not accurate (it could be that the term counts are slightly off and it could even be that a term that should have been in the top size buckets was not returned). https://www.elastic.co/guide/en/elasticsearch/reference/6.8/search-aggregat… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5