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

[Bug 41863] New: Facets generated from Authorized values sometimes show empty labels
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41863 Bug ID: 41863 Summary: Facets generated from Authorized values sometimes show empty labels Initiative type: --- Sponsorship Sponsored status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org With facets generated from Authorized values, it may happen that the list of authorized values lacks an entry for a code used in a record. In this case, an empty entry will appear in the facet list, with the number of uses but without any label. It would be desirable to show at least the raw code, rather than an empty label. This makes it easier to see which code has no entry in the respective AV and to either add it or correct an erroneous code. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 41851] New: Add logging to EDI cron job
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41851 Bug ID: 41851 Summary: Add logging to EDI cron job Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Most crons now log their runs in the action logs - the edi cron does not -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 41859] New: Authority search autocomplete results not consistent with search results
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41859 Bug ID: 41859 Summary: Authority search autocomplete results not consistent with search results Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When cataloguing and using authority plugin, there is auto complete feature. But hints it produces are not consistent with search results made with the same operator. E.g. (with standard KTD test data set) typing 'reusability' in 'Search main heading'/'Search all headings'/'Search entire record' gives no hints but one result ("Computer software Reusability.") It does not seem logical. This is because standard search operator is set to 'contains' and the hardcoded operator for autocompletion is set to 'start'. At the same time, in Elasticsearch, the subdivisions are always included as part of indexed string. In Zebra, it also true (Heading and Match indices) except for 'Search entire record' which uses index 'Any'. The expected behavior would be to have it consistent. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 41778] New: Broken display of not for loan status on item detail page
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41778 Bug ID: 41778 Summary: Broken display of not for loan status on item detail page Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org On the item details page the section heading, which shows the barcode or item number, is supposed to also show the not for loan status if there is one. The way the template variables are defined the status cannot be shown. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 41760] New: Fix <tbody> and <tfoot> in several templates
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41760 Bug ID: 41760 Summary: Fix <tbody> and <tfoot> in several templates Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org There was a time when the W3C wanted us to put <tfoot> betwee, <thead> and <tbody>, but they have changed their minds. There are a few pages which still have the <tfoot> in that position which triggers a validator error. There are also several instances of <tfoot> in tables which lack a <tbody>, which I'm also fixing. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 41665] New: Only include Greybox in OPAC if IdRef is enabled
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41665 Bug ID: 41665 Summary: Only include Greybox in OPAC if IdRef is enabled Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Greybox is only used in the OPAC for the IdRef feature in the UNIMARC XSLT. So we should only include it in that context. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 41335] New: Toggling the hold options does not always work in opac-reserve
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41335 Bug ID: 41335 Summary: Toggling the hold options does not always work in opac-reserve Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Some combinations of OPACMandatoryHoldDates together with forced item level holds make the options collapsed while they should be expanded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 41073] New: Import users expiry date default does not apply
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41073 Bug ID: 41073 Summary: Import users expiry date default does not apply Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com You can no longer set an expiry date into the past. Test file: userid,cardnumber,branchcode,categorycode,surname "12345","65432","LONDON","STANDARD","Smith" 1. User should exist and have expiry date in future (say 2099-12-31) 2. Save above as file 3. Tools > Import users 4. Choose file saved in 2 5. Field to use for record matching: cardnumber 6. In default values set expiration date to a date in past (say 2025-10-19) using date picker 7. Select overwrite the existing one with this 8. Leave renew existing patrons as "use the expiration date in the file if present" 9. Run 10. Observe user expiry date is still 2099-12-31 NB/ Tested in 23.11.10 where the date was correctly set to the default value chosen -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 28884] New: ElasticSearch: Question mark in title search returns no results
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28884 Bug ID: 28884 Summary: ElasticSearch: Question mark in title search returns no results Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)equinoxinitiative.org When searching for a title with a question mark, Who's Afraid of Virginia Woolf? for example, Koha returns no results with ElasticSearch. Removing the question mark or escaping it retrieves results, as does enclosing the entire title with the question mark in quotes. Since ? is a wildcard for ElasticSearch, this may be expected behavior (I'm not sure that it is or isn't), but explaining to patrons that they need to change their search behavior can be a big ask for libraries. Not sure what the best option is. Perhaps a system preference to automatically escape ? and not treat it as a wildcard for those libraries who would prefer that? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 35237] New: Duplicate ids in markup of patron card layout edit form
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35237 Bug ID: 35237 Summary: Duplicate ids in markup of patron card layout edit form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy, accessibility Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Tools -> Patron card creator -> Edit layout: A few pairs of radio buttons have duplicate labels: <li> <label for="page_side">Page side: </label> <input type="radio" name="page_side" id="page_side" value="F">Front <input type="radio" name="page_side" id="page_side" value="B" checked="checked">Back </li> It would be better for the "Page side" label to have no "for" attribute and for "Front" and "Back" to be labels. -- You are receiving this mail because: You are watching all bug changes.

1 25