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

[Bug 23911] New: Possibility to do more complex analysis of systempreference usage
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23911 Bug ID: 23911 Summary: Possibility to do more complex analysis of systempreference usage Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Hea Assignee: chris(a)bigballofwax.co.nz Reporter: joonas.kylmala(a)helsinki.fi QA Contact: jonathan.druart(a)bugs.koha-community.org It would be nice to be able to query how many libraries use a combination of different sysprefs like "AllowItemsOnHoldCheckout = 1 AND AllowItemsOnHoldCheckoutSCO = 1". This could be available either through an API or the UI. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 41175] New: visually alert at return for a reservation if item need to be transferred
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41175 Bug ID: 41175 Summary: visually alert at return for a reservation if item need to be transferred Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Created attachment 188985 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=188985&action=e… background colour pink if the reserve needs to be transferred, this is different to the usual yellow We would like to see a visibly different in the pop up window display for when a reservation needs to be transferred to another site and when it needs to be placed on the reservation shelf. We are seeing lots of human error with this at the moment and something like a rule that changes the colour background would really help. For example, I was able to do this quite easily with a hook on 'transfer to' being present. See attached. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #194 from Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> --- (In reply to Michaela Sieber from comment #193) > We tested several hours and I will provide more feedback this week but here > are the most relevant Bugs we found: > > 1.) Migration scenario > > have some overdue rule, then apply the patch and do updatabase and yarn buid > > Error 404 in staff interface > > Please see Pedros comment 192 > > In your testplan in comment 183 you write in > > Part 11: Data Integrity & Persistence > 5. Check the database circulation_rules table: > - Verify the overdue_X_has_rules rule kind is present > > Is this the missing piece for the migrated data ? > > > 2.) Adding a trigger for a combination that exists in circ rules > > it is not possible to configure an overdue trigger with a combination that > already exists as a circulation rule. > > Example to reproduce in ktd with test data: > > - Go to circ rules (/cgi-bin/koha/admin/smart-rules.pl) > - Set a rule for All Libraries / All patron categories / Itemtype Books > - Check via SQL: select * from circulation_rules > - Go to overdue rules (/cgi-bin/koha/admin/circulation_triggers ) > - Set a rule for All Libraries / All patron categories / All Itemtype > - Now try to edit the delay for the applied rule > with combination All Libraries / All patron categories / Itemtype Books > --> Message in blue box "Your changes could not be saved as this > circulation > trigger was updated elsewhere. Please see the updated trigger below." > It is not possible to save / submit > - Now edit the delay for the applied rule > with combination All Libraries / Patron category Homebound / Itemtype > Books > --> You can save without problems, if this combination does not exist in > the database table circulation_rules > > > 3.) Permissions Error if you are not an admin > > The Overlay rules are part of the tools and also the permission is part of > the tools section. That means that it was enough to give users the > edit_notice_status_triggers permission, it was not neccessary to give any > administration permission (parameters) . > Now you moved the overdue triggers to administration. > > If you now log in as a person with edit_notice_status_triggers permission > you can see the tools module and click on the menu for overdue triggers but > then you get the error message "Something went wrong: Error: Authorization > failure. Missing required permission(s)." > > > 4.) Edit an existing trigger does not pull delay from database > > Edit an existing trigger and check that the delay value is 0 , it is not > pulled from the database. This is confusing and dangerous because you see > the delay value just a few centimeters above in the table. > If you save the form, the value in the database is overwritten with 0. > > To reproduce: follow testplan in comment 183 Part 4.3 Thank you for the testing and feedback, much appreciated! Re - 1.) overdue_X_has_rules is a property indicating that some rule(s) exist for a given context/trigger number combination. The most recent version of the integration ensure it is created whenever any rule is created for a given context/trigger number combination. The staff clients relies on this to ascertain whether a rule set exists efficiently. I think the solution might be to have it added to each existing context/trigger number combination - would that be sensible? 2., 3., and 4.: I will do some debugging and put patches together for those, many thanks for reporting them! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41185] New: internal server error on all searches with REST API
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41185 Bug ID: 41185 Summary: internal server error on all searches with REST API Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: pavel(a)vertical-it.ru QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Created attachment 189070 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189070&action=e… patch My environment: Ubuntu Server 24.04 with latest updates Koha 25.05 from packages Basic authentication for REST API is enabled. I run examples from official documentation https://api.koha-community.org/#section/Filtering-responses curl -u username:password --request GET "http://hostname/api/v1/patrons/" --data-raw '{ "surname": "Acevedo", "firstname": "Henry" }' curl -u username:password --request GET "http://hostname/api/v1/patrons/" --data-raw '{ "surname": { "-like": "Ace%" }' curl -u username:password --request GET "http://hostname/api/v1/patrons/" --data-raw '{ "surname": [ "Acevedo", "Bernardo" ] }' curl -u username:password --request GET 'http://hostname/api/v1/patrons/' --header 'x-koha-embed: extended_attributes' --data-raw '{ "extended_attributes.code": "internet", "extended_attributes.attribute": "1" }' They all return this: {"error":"Something went wrong, check Koha logs for details.","error_code":"internal_server_error"} Error log: [ERROR] GET /api/v1/patrons/: unhandled exception (DBIx::Class::Exception)<<DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column '{ "extended_attributes.code": "internet", "extended_attributes.attribute": "1" }' in 'WHERE' at /usr/share/koha/lib/Koha/REST/Plugin/Objects.pm line 284>> I turn on MariaDB query log and see what causes the error: SELECT COUNT( * ) FROM `borrowers` `me` WHERE ( ( ( `firstname` = 'Henry' AND `surname` = 'Acevedo' ) AND `{ "surname": "Acevedo", "firstname": "Henry" }` LIKE '%%' ) ) I have developed a patch but this may require further investigation from Koha developers why this is occurring in the first place. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 41184] New: Some info from Housebound details should show in patron brief info
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '25

04 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41184 Bug ID: 41184 Summary: Some info from Housebound details should show in patron brief info Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jheltibridle(a)rcplib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com We currently have a patron attribute set up for our home delivery patrons that displays their delivery week in their brief info. We are working on implementing the housebound module, and see that each patron can have a delivery day and frequency. It would be useful if this information were displayed in the patron brief info or on their details page, rather than having to click into a separate tab. I don't think we need their other preferences from the housebound details to show on their main details page, but i could see other libraries finding this useful, so having it be customizable would be helpful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 41183] New: Housebound roles should allow patron category limits
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '25

04 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41183 Bug ID: 41183 Summary: Housebound roles should allow patron category limits Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jheltibridle(a)rcplib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com It would be helpful if you could define whether a patron category is allowed to have a housebound role, and hide the "Housebound Roles" section from the patron's details page if their category doesn't allow the role to be assigned. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 28752] New: Add 'sort fields' to Housebound module
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '25

04 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28752 Bug ID: 28752 Summary: Add 'sort fields' to Housebound module Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For the Housebound Module, it would be very helpful to have up to 4 'Sort fields' where libraries can save data specific to their program for each patron's housebound details. Currently you can enter delivery day, frequency, preferred materials, subjects, authors, referrals and notes. We would like 4 additional fields that we can set up with data specific to our program. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38398] New: Do not call barcodeencode on remove_from_bundle
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '25

04 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38398 Bug ID: 38398 Summary: Do not call barcodeencode on remove_from_bundle Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: martin.renvoize(a)ptfs-europe.com Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com The sub for removing an item from a bundle uses barcodedecode to remove leading and trailing whitespace from an itemnumber. This causes failures for libraries using plugins like the Barcode Prefixer that alter a value passed through barcodedecode. We should chomp that itemnumber or something instead. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 32961] New: Add ability to enable/disable Serials module
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '25

04 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32961 Bug ID: 32961 Summary: Add ability to enable/disable Serials module Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The Serials module can be hidden in the staff interface by using IntranetUserJS, but just like the following modules/features can be enabled/disabled or set to use/don't use, it would be nice to have this functionality in system preferences to turn on/off the Serials module as well. Existing features set in system preferences: ERMModule (Enable/Disable) CurbsidePickup (Enable/Disable) ILLModule (Enable/Disable) UseCourseReserves (Use/Don’t Use) EnablePointOfSale (Enable/Disable) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 36183] New: Add item barcodes to staff search results page
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '25

04 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36183 Bug ID: 36183 Summary: Add item barcodes to staff search results page 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Several libraries have requested that the item barcode be added to the staff results page. While I can see the benefit to this, I am unsure how to make it happen. Currently Koha "groups" items by there availability and then by holding branch, location, itype, and ccode. C4/Search.pm 1854 ( $item->{$hbranch} ? $item->{$hbranch} . '--' : q{} ) 1855 . ( $item->{location} ? $item->{location} : q{} ) 1856 . ( $item->{itype} ? $item->{itype} : q{} ) 1857 . ( $item->{ccode} ? $item->{ccode} : q{} ) I don't quite know how to "group" something like barcode which would be unique for every single item. Maybe it gets added in a separate display/column? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2