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

[Bug 28410] New: Reduce memory footprint
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '25

10 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28410 Bug ID: 28410 Summary: Reduce memory footprint Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Mostly because of our circular dependencies we are facing memory issue. Like any simple scripts will have to load all the modules. We should focus on reducing the memory footprint. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 36721] New: Preload core libraries to speed up worker startup and reduce memory usage
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '25

10 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36721 Bug ID: 36721 Summary: Preload core libraries to speed up worker startup and reduce memory usage Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 If we preload core libraries using Starman's -M option, we can in theory speed up worker startup and reduce memory usage. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 39194] New: Add a cronjob to report record IDs that have failed to be indexed (Elasticsearch - ES)
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '25

10 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39194 Bug ID: 39194 Summary: Add a cronjob to report record IDs that have failed to be indexed (Elasticsearch - ES) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org If a record is catalogued but does not successfully get indexed by Elasticsearch, it is called 'missing'. A summary of this can be seen on the Koha About page, under the System information tab. A user may see something like this: Records are not indexed in Elasticsearch Warning 27 record(s) missing on a total of 1807413 in index koha_kohadev_biblios. However we can't see from this view which record(s) are missing from the indices. It would be great to have a list of the IDs that are in the Koha database, but not in the ES indices. Probably need this to be a cronjob as with large catalogues, a request like that would crash Koha. So would also want to report the time the script was run last to the page as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[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 30834] New: Trigger nightly reindex with a syspref
by bugzilla-daemon＠bugs.koha-community.org 07 Mar '25

07 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30834 Bug ID: 30834 Summary: Trigger nightly reindex with a syspref 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Reindexing (at least with Zebra) leads to search not working for some duration of time, depending on the size of the catalogue. So often you want to do reindexing at night, when use of Koha is low. But remembering to start the indexing process before you go to bed at night is error prone. We could have a syspref called something like "DoReindexInTheMiddleOfTheNight", and a cronjob that runs "in the middle of the night", and checks the syspref. - If it has been set to "on", a reindex is triggered and the syspref is reset to "off". - If it is set to "off", nothing happens. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[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