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

[Bug 40245] New: Support option to display firstname in memberresultst
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40245 Bug ID: 40245 Summary: Support option to display firstname in memberresultst Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: Chip.Halvorsen(a)WestlakeLibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Circulation staff would find it very useful to see firstname in addition to preferred_name in the patron search results table (memberresultst). Currently at 24.11+, only the preferred name is displayed. One way to handle this might be to add firstname as a line at between address and email address. SMITH, KAT 123 MAIN ST. ANYTOWN, STATE/PROVINCE POSTCODE Firstname: KATELYNN Email: X(a)Y.Z Or we might want to put the firstname in parenthesis. SMITH, KAT (Firstname: KATELYNN) 123 MAIN ST. ANYTOWN, STATE/PROVINCE POSTCODE Email: X(a)Y.Z Having the firstname appear somewhere would help disambiguate similar patron names in the search results. Even better would be logic that only displayed the Firstname when it differs from the Preferred_name. This should be made optional. Some libraries might not want firstname to appear here, to avoid accidentally deadnaming a patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 32887] New: OpacLibraryInfo needs to be pre-selected when OPAC info is added for a library
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32887 Bug ID: 32887 Summary: OpacLibraryInfo needs to be pre-selected when OPAC info is added for a library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To test: * Go to administration > libraries * Edit a library * Verify there is a link "Add HTML content" * Click it * On the HTML customizations form, verify that the location pull down is not correctly set to OpacLibraryInfo. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40516] New: Boolean filters are broken on datatables
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40516 Bug ID: 40516 Summary: Boolean filters are broken on datatables Change sponsored?: --- Product: Koha Version: Main 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: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Datatable filters that are boolean based are no longer displaying the falsy option and are filtering incorrectly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 39366] New: Combining PatronSelfRegistrationVerifyByEmail with OpacPublic off does not work
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39366 Bug ID: 39366 Summary: Combining PatronSelfRegistrationVerifyByEmail with OpacPublic off does not work 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Found this accidentally. When you receive a link to verify, the page will ask you to login but obviously you do not have that login yet.. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 20125] New: Add a cron script to claim late orders
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20125 Bug ID: 20125 Summary: Add a cron script to claim late orders 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: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org We need a script that automatically send order claims by mail to the booksellers. The script should take 3 important paramters: delay: Number of days from which an orders is considered as late claimed-for: Minimum number of days since the last claim max-claim: Maximum number of claims -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 30614] New: check-url-quick gives false error 404
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30614 Bug ID: 30614 Summary: check-url-quick gives false error 404 Change sponsored?: --- Product: Koha Version: 20.05 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: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, Many 404 errors come out after running the check-quick-url script while the urls are correct when checked manually. Apparently this is because the script uses HTTP HEAD instead of HTTP GET. HTTP HEAD returns only the headers of the urls and the header can return an error but the url is accessible when you do a GET. Is there a reason for this? My fellow analyst was pointing to line 104 of https://github.com/Koha-Community/Koha/blob/master/misc/cronjobs/check-url-… Thank you Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 40608] New: Password not changed if PASSWORD_CHANGE letter absent
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40608 Bug ID: 40608 Summary: Password not changed if PASSWORD_CHANGE letter absent Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When the `NotifyPasswordChange` setting is enabled but no letter for the 'email' transport is found, the current code returns before the password change is stored on the DB! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 39745] New: Wrong system preference 'language' in test suite
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39745 Bug ID: 39745 Summary: Wrong system preference 'language' in test suite Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 27490 renamed system preference language to StaffInterfaceLanguages. Needs to be done in test suite selenium tests. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 39720] New: Search for system preferences call errors
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39720 Bug ID: 39720 Summary: Search for system preferences call errors Change sponsored?: --- Product: Koha Version: Main 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Since Bug 38772 found a typo in system preference 'minPasswordPreference' call, we could try to grep any call to compare with system preferences file. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 28486] New: MARCItemFieldsToOrder values lost when using Add Order button
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '26

16 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28486 Bug ID: 28486 Summary: MARCItemFieldsToOrder values lost when using Add Order button Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When populating a basket via a staged MARC file and checking for duplicates, if a duplicate is found then one is expected to use the "Add Order" button on that title to manage that title individually and decide whether to use the existing bib or create a new one. Either choice pushes one to neworderempty.pl (rather than addorderiso2709.pl). Values from MARCItemFieldsToOrder are not applied on neworderempty.pl, which complicates the workflow and requires the user to manually enter those values. To recreate: 1 - export a bib from your collection 2 - edit that bib to add some item values formatted in accordance with your MARCItemFieldsToOrder syspref 3 - create a basket in Acq set to create items at ordering 4 - add to your basket from a new file, select your exported and edited bib 5 - on addorderiso2709.pl, confirm your MARCItemFieldsToOrder values show up 6 - click Add Order 7 - select wither Use Existing Record or Create New Record 8 - confirm that you end up on neworderempty.pl without your MARCItemFieldsToOrder values -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4