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

[Bug 42656] New: File transport test responses can be unclear
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42656 Bug ID: 42656 Summary: File transport test responses can be unclear Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When testing a file transport, we change directory four times: once to undef once to incoming again to undef once to outgoing When these fail for the incoming/outgoing, the errors look like: Change directory passed Change directory failed Change directory passed Change directory failed Which is unclear at best. Also, when updating a transport, the status before tests complete is: Never used Which is confusing to users who have jobs (e.g. EDI) that use these transports regularly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 42451] New: "convert" op in guided_reports.pl is broken due to JS error
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42451 Bug ID: 42451 Summary: "convert" op in guided_reports.pl is broken due to JS error Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com "convert" op in guided_reports.pl is broken due to JS error: Uncaught TypeError: Cannot read properties of undefined (reading 'backdrop') It should also be converted into "cud-convert" anyway -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 42235] New: On OPAC messaging preferences page table header contains no text
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42235 Bug ID: 42235 Summary: On OPAC messaging preferences page table header contains no text Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org To recreate: 1. Log into the OPAC 2. Go to "Messaging" 3. The first column's th in the table contains no text. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 43240] New: Inaccurate check in message for lost items
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43240 Bug ID: 43240 Summary: Inaccurate check in message for lost items 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: alyssa.drake(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37985] New: Extend geo-search to support areas, not just points (MARC 034 subfields defg)
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37985 Bug ID: 37985 Summary: Extend geo-search to support areas, not just points (MARC 034 subfields defg) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tadeusz(a)sosnierz.com QA Contact: testopia(a)bugs.koha-community.org Bug 31652 ("Add geo-search") implements indexing geographic coordinates (034s,t) in Elasticsearch to enable searching for records referring to specific coordinates. Some records (or authorities) will refer to whole areas, which MARC encodes as north/south/east/westmost points. Since elasticsearch supports indexing shapes, not just points, it would be a nice improvement to be able to index this as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 37537] New: Add bounding box variant to geo-search
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37537 Bug ID: 37537 Summary: Add bounding box variant to geo-search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tadeusz(a)sosnierz.com QA Contact: testopia(a)bugs.koha-community.org Following up on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31652, it would be useful to be able to search for records falling within a (rectangular, axis-aligned) bounding box. The current solution allows looking up records within a specified distance from a given point. geo_bounding_box searches would allow for things like "given this map fragment, overlay all records that would be visible on it". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 37821] New: Embed geographic coordinates when indexing biblios linked to GEOGR_NAME authorities
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37821 Bug ID: 37821 Summary: Embed geographic coordinates when indexing biblios linked to GEOGR_NAME authorities Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tadeusz(a)sosnierz.com QA Contact: testopia(a)bugs.koha-community.org Items can be linked to GEOGR_NAME authorities, which in turn can have geographic coordinates stored in them. We have the functionality to search for items around geographic coordinates, but currently the indexer only indexes coordinates stored in 034 in the item itself, not in any authorities linked to it. Embeding the coordinates from the GEOGR_NAME authority should have a negligible impact on the size of the index, and should make geo-tagging of items a lot easier. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 36586] New: Self-checkouts will get CSRF errors if left inactive for 8 hours
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36586 Bug ID: 36586 Summary: Self-checkouts will get CSRF errors if left inactive for 8 hours Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, the CSRF token is only good for 8 hours. This means that a self-checkout terminal left inactive for 8 hours (e.g. overnight, over a holiday closure, etc) will create a wrong CSRF token error on the first activity attempt in the morning. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 82

[Bug 43242] New: Ability to exclude bibliographic records (from cart or from list) from search results
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43242 Bug ID: 43242 Summary: Ability to exclude bibliographic records (from cart or from list) from search results Initiative type: --- Sponsorship --- status: 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: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- It would be nice if there were an option to exclude bibliographic records from the cart or from a specific list, so that they do not appear in the search results. Example: We want to select certain records from several different searches -- for example, to collect them in cart. In each search, we get records that don’t interest us -- and each time, we have to "skip" them. If we could exclude them from the search results, we could add them to a list whose contents won’t appear in the results of the next search. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42528] New: metadata_record should always strip nonxml characters
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '26

06 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42528 Bug ID: 42528 Summary: metadata_record should always strip nonxml characters Initiative type: --- Sponsorship --- status: 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This was inspired by noticing that when importing a batch the indexing could fail for a batch of records where a single record had encoding issues. Koha::Biblio->metdata_record is used for retrieving records from the DB, and possibly filtering them. In the cases we are using this, it's better to give the user/caller a result than nothing The error on the record is logged, it can be seen when viewing the record in the staff interface, and can be found using the data inconsistencies tool. I think it makes sense for the default behavior to attempt to clean the record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12