January 2026 - Koha-bugs - lists.koha-community.org

[Bug 39589] New: Search returns 'No results found' despite existing matching records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39589 Bug ID: 39589 Summary: Search returns 'No results found' despite existing matching records Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This issue occurs when the records on the first page of results are not displayed. The message "No results found" is shown, and it is not possible to access records on other pages. To test 1. Set the following system preferences: OPACnumSearchResults to 5 OpacHiddenItemsHidesRecord to Hide OpacHiddenItems to withdrawn: [1] 2. Create 6 bibliographic records with the following titles: "notice test 1" "notice test 2" "notice test 3" "notice test 4" "notice test 5" "notice test 6" 3. For the first 5 records, add an item with Withdrawn status. 4. For "notice test 6", add an item with Available status. 5. In the OPAC interface, search for "notice test". ---> The message "No results found!" appears, and "notice test 6" is not visible. -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 27690] New: Add search bar to OPAC for public lists
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27690 Bug ID: 27690 Summary: Add search bar to OPAC for public lists Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: e0464747(a)cmaisonneuve.qc.ca QA Contact: testopia(a)bugs.koha-community.org Created attachment 116780 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=116780&action=e… Wanted feature in opac-course-reserves.pl Hi, There is a search bar feature in the OPAC's course reserve page (opac-course-reserves.pl). It would be great if that same type of search bar could also be found in the public lists page (opac-shelves.pl?op=list&category=2). It should be helpful for any OPAC that has multiple pages of public lists to manage and go trough. I've added a screen shot of the desired search box. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 20512] New: Add a second sort possibility in a public list
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20512 Bug ID: 20512 Summary: Add a second sort possibility in a public list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, when you sort a public list by call number at the intranet, the documents how has a Lc and a DDC code are placed at the top of the list. to recreate this problem 1) creat a public list with records who have two classifications. 2) Add somes records with only one classification and who would rank before works with two classifications. 2) Sort thi new list by call number. You will notice that the records with tow classificaton codes are at the top of the list It would be greate if we can add the possibility too do a second sort by classification code. Thanks, Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27647] New: Allowing Lists to have a Hierarchical Structure
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27647 Bug ID: 27647 Summary: Allowing Lists to have a Hierarchical Structure Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Lists are very helpful and useful to staff and patrons. A library would like the ability to have a sort of hierarchy of lists. The ability to add lists to a group of lists (subgroups) and organize by this way. This idea comes from an academic looking to organize by subject, but I can also see this as a branch hierarchical structure or in a public library to do DVDs as a Major List = and then have monthly lists attached to this one major topic. I did see this bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20512 that would like to see the ability to sort bugs- which would be nice also. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 33092] New: Add ability to search within a list
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33092 Bug ID: 33092 Summary: Add ability to search within a list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be really helpful to be able to search within a list in both the OPAC and the staff interface. For instance, in both the staff interface, if you are viewing a public list with a lot of items on it, you do not have the ability to see if a specific item appears on the list. This is a needed functionality with larger lists. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 32081] New: Add OpacBrowseSearch functionality to lists
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32081 Bug ID: 32081 Summary: Add OpacBrowseSearch functionality to lists Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It should be a nice feature adding the functionality of browse within a list, as it is in result list, next record instead of browse back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26355] New: Tie account renewals to patron modification requests
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26355 Bug ID: 26355 Summary: Tie account renewals to patron modification requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Allow patrons renewal reminders to link to the patron modification requests, asking them to review their information and make any any necessary updates if necessary, but acknowledging that the information is up to date. Create a check-box stating that they have reviewed all their information, and it is accurate and up to date (if no changes are made). Perhaps this check-box only shows when their account is due for renewal. -- You are receiving this mail because: You are watching all bug changes.

1 255

[Bug 40960] New: Notifying holds should not print notice if no messaging preference is notified
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40960 Bug ID: 40960 Summary: Notifying holds should not print notice if no messaging preference is notified Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In overdue_notice.pl, holds_reminder.pl, no paper notice is sent to patron if no checkbox is checked. This should be the same for notifying holds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 22972] New: Proposal for enriching the bibliographic records with standard identifiers from authority data
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22972 Bug ID: 22972 Summary: Proposal for enriching the bibliographic records with standard identifiers from authority data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Thinking in terms of linked data, it would be of profit to have as much of standard identifiers in the bibliographic data produced by the library as possible. Libraries use authority data coming from official sources (like LoC, SUDOC, etc.) or enrich their locally created authority records with standard identifiers (e.g. viafId, ISNI, Wikipedia). This information is linked to the bibliographic record by the Koha-specific subfield $9 which is illegal in terms of MARC 21 and does not mean anything outside of the local Koha ecosystem. A record moved out of a local Koha catalogue (downloaded, exported) loses the linked-data connection to other objects (like authors, subjects etc.), which are then identified only by strings. To make this connection between bibliographic access point and objects identified by universal identifiers more permanent outside of the local environment, the standard MARC 21 $0 subfield could be used. (UNIMARC has to be examined - $3 subfield?) The required changes would include at least: C4::AuthoritiesMarc::merge function, the authority plugin, some new system preferences, optionally display templates and also a script to update the existing biblio records. New possible system preferences needed: - switch the feature on/off - source of the standard IDs (possibly different for different biblio fields?) (standard in MARC 21 authority: 024, but may be also 010/035) (a list) - how many ids should be copied (= how may $0 added): only the first found or all of them - if an extra link/icon should be generated in display (OPAC / librarian) Please, share your comments about this idea. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 41460] New: On Mysql on upgrade from 25.05 to 25.11 I got the error TEXT column 'value' can't have a default value
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41460 Bug ID: 41460 Summary: On Mysql on upgrade from 25.05 to 25.11 I got the error TEXT column 'value' can't have a default value Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org Mysql does not allow blob or text type columns to have a default. The systempreferences.value column is the only occurrence of this I found in the kohastructure.sql file. It seems Mysql will ignore the default null as long as the column allows null, so that's not an issue. Bug 40405 sets systempreferences.value to NOT NULL, but tries to also add a DEFAULT '', which causes Mysql to throw the above error. Proposed solution is to remove the DEFAULT '' part of the clause from the db_rev file. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27