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

[Bug 33166] New: Can't call method "notforloan" on an undefined value when placing a hold
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '25

06 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33166 Bug ID: 33166 Summary: Can't call method "notforloan" on an undefined value when placing a hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Steps to reproduce: 1. Create a biblio with no item type, and an item with no item type 2. Try to place a hold for this biblio You should get an "internal server error" message, and in the logs the following line: Can't call method "notforloan" on an undefined value at [...]/C4/Reserves.pm line 1446. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 22859] New: Copying an item that has location set as 'CART' sets the permanent location of the new item to 'CART'
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22859 Bug ID: 22859 Summary: Copying an item that has location set as 'CART' sets the permanent location of the new item to 'CART' Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- It should copy the original items.permanent_location rather than items.location. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 37674] New: Vendor page should change to a sortable vendor table
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37674 Bug ID: 37674 Summary: Vendor page should change to a sortable vendor table Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a library has a lot of vendors, say a few thousand, the vendor page load is extraordinarily slow. There is a lot of data being pulled into the page that is perhaps unnecessary. It would be worth considering changing this page to a table that lists the vendor name with action buttons for New, Edit, Receive. The vendor name could be a link to the vendor detail page that then displays the baskets. The table could include other bits of data deemed useful over time. If the table was sortable and searchable, it would be far more useful. If a library has this many vendors and associated baskets, the entire page is cumbersome. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 35561] New: Allow automatic item modification by age to match wildcards
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35561 Bug ID: 35561 Summary: Allow automatic item modification by age to match wildcards 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 add the ability for the automatic item modifications by age to include wildcards. For example one of the Condition options is to pull items from items.itemcallnumber. However, it only works with specific matches. This could add the ability to have: Age in days: 180 items.dateaccessioned Condition: items.itemcallnumber = LP FIC A% Substitute: items.permanent_location = LPFIC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39263] New: When an ILL request is closed the item and biblio record created for it should be deleted
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39263 Bug ID: 39263 Summary: When an ILL request is closed the item and biblio record created for it should be deleted 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 an ILL request is closed (I mean the document has been returned to the supplying library) the item and biblio record created for it should be deleted, either in real time (better I suppose) or with a script in cron They were only created to enable the document to be checked out to the patron. If we don't remove them, they will pollute the catalog. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 29275] New: issuehistory.pl is very slow when there are many historical issues
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29275 Bug ID: 29275 Summary: issuehistory.pl is very slow when there are many historical issues Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Example: We have a library with a biblio that has 39000ish issues in the history, this page cannot be loaded within the plack/apache timeouts, and users can DOS themselves trying to see it. This is admittedly a very extreme case, but even bibs with fewer issues in the history would probably benefit from this page having better performance. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 78

[Bug 25934] New: RequireStrongPassword should be more complex (password policy complexity)
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25934 Bug ID: 25934 Summary: RequireStrongPassword should be more complex (password policy complexity) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org At the moment, RequireStrongPassword uses a minimum password length (of only 3 characters or the sysperf minPasswordLength) and a static regular expression. Here are a number of improvements: 1. A minimum length of 10 characters that can't be lowered via minPasswordLength 2. Should contain 3 of the following 4 sets (lowercase, uppercase, numbers, special characters) 3. Not be the same as a previously set password 4. Should not include dictionary words or common passwords (This could be challenging to do comprehensively on low spec systems, although one variation of this could be to add a customizable list of passwords to exclude.) 5. Should not be equal to the username -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 39396] New: Select2 drop-downs in batch item modification are empty
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39396 Bug ID: 39396 Summary: Select2 drop-downs in batch item modification are empty Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When attempting to modify items with the Batch Item Modification Tool, all of the select2 drop-downs in the form are coming up empty, with no options to select. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 35717] New: Add an ordernumber column to suggestions
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35717 Bug ID: 35717 Summary: Add an ordernumber column to suggestions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This is bug 28844 reworked with the relationship defined in the reverse way. There can be multiple suggestions for the same title currently (the check for duplicate suggestions includes the suggestedby field in the search, so only a single patron is prevented from requesting the same book twice) While we can order only from a single suggestion, bug 19358 and 31632 seek to allow linking multiple suggestions to an order, I believe we need to define the relationship this way now, to allow for future changes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 51

[Bug 35712] New: Record issue_id in old_reserves for completed holds
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35712 Bug ID: 35712 Summary: Record issue_id in old_reserves for completed holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: nick(a)bywatersolutions.com There is not currently a direct data linkage between a filled hold in old_reserves and the checkout that filled it in (old_)issues. It'd be helpful if we could put the issue_id into the old_reserves table to make that explicit. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5