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

[Bug 35837] New: It would be useful to understand what plugins are being used in the wild.
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '26

22 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35837 Bug ID: 35837 Summary: It would be useful to understand what plugins are being used in the wild. Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org HEA hasn't seen much love of late.. it would be great to send back statistics on plugins used in an installation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 32106] New: Formatting issues - accounting details form when receiving items
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '26

22 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32106 Bug ID: 32106 Summary: Formatting issues - accounting details form when receiving items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 143163 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=143163&action=e… Screenshot - Receiving order form - formatting When receiving an order, there are some minor formatting issues for two fields on the accounting details form (see the attached screenshot): - Retail price: no space after value and the opening bracket; no space between comma and tax exclusive (or tax inclusive, depending on the vendor setting) - Budgeted cost: no space after value and the opening bracket This requires changes to koha-tmpl/intranet-tmpl/prog/en/modules/acqui/orderreceive.tt to fix. To replicate:* 1. Add an order to a basket for a vendor (Acquisitions > Manage orders > click search > select My Basket (for My Vendor) > Add to basket). 2. Close the basket (select 'Close basket' from the basket page). 3. Receive shipments for the vendor (Acquisitions > Manage orders > click search (shows My Basket for My Vendor) > Receive shipments > Enter an invoice number > Next). 4. Click receive for an item in My Basket. 5. Note the formatting issues on the accounting details form for these fields: - Retail price: no space after value and the opening bracket; no space between comma and tax exclusive (or tax inclusive) - Budgeted cost: no space after value and the opening bracket 6. On another tab, edit the vendor so that for 'list prices' and 'invoice prices' the 'include tax' option is selected. 7. Refresh the tab for receiving items. 8. Note the same formatting issues as in step 5. * Using koha-testing-docker (KTD) there is one vendor (My Vendor) with an empty basket (My Basket) already setup. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 32571] New: Use template wrapper to build tabbed components
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32571 Bug ID: 32571 Summary: Use template wrapper to build tabbed components Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, testopia(a)bugs.koha-community.org In preparation for an upgrade to Bootstrap 5 I propose that we try to abstract the way we build some components. This will help reduce the number of template changes required during the update. Using Template::Toolkit WRAPPERs we can create the structural components for tabs separately from the tab content: - Main tab container - Tab links container - Individual tab links - Tab panel container - Individual tab panels This can be done gradually before the Bootstrap upgrade without causing any disruption. -- You are receiving this mail because: You are watching all bug changes.

1 77

[Bug 29490] New: Preview for more notices
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29490 Bug ID: 29490 Summary: Preview for more notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to have the preview option available on more notices.. currently, it's limited to CHECKIN, CHECKOUT and HOLD_SLIP. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 25795] New: Add OAuth2 scopes to REST API
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25795 Bug ID: 25795 Summary: Add OAuth2 scopes to REST API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au It could be useful to add OAuth2 scopes for managing authorization for the REST API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 20402] New: Implement OAuth2 authentication for REST API
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20402 Bug ID: 20402 Summary: Implement OAuth2 authentication for REST API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: REST api Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com -- You are receiving this mail because: You are watching all bug changes.

1 94

[Bug 23204] New: Script for exporting Elasticsearch mappings to YAML
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23204 Bug ID: 23204 Summary: Script for exporting Elasticsearch mappings to YAML Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Target Milestone: --- Sometimes we need to report librarian's mapping changes in DB to the mappings.yaml. This can be long and tedious. So, here is a script that do the job. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 35138] New: Elastic search - add new facets
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35138 Bug ID: 35138 Summary: Elastic search - add new facets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: michaela.sieber(a)kit.edu We would like to create a new facet for a 9xx-MARC field As Nick mentioned in Bug 18235, Comment 7: -labels shouldn't be hardcoded - staff should be able to set them -we should add more options to what can be faceted- could be out of control but technically any field should be able to be used -ES has better handling for faceting (can provide subsets of existing/current results and allow to step in/out of facets) Problems / Challenges: 1. Translatability: if staff changes or add new labels, they will not be translated 2. same files for elastic and Zebra -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 74

[Bug 18235] New: Elastic search - Configurable facets
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18235 Bug ID: 18235 Summary: Elastic search - Configurable facets Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Searching Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14899, 17169, 18174 >From the Elastic mappings configuration page, the librarians should be able to manage facets (display/hide and order). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899 [Bug 14899] Mapping configuration page for Elastic search https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17169 [Bug 17169] Add facets for ccode to elasticsearch https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18174 [Bug 18174] Add the Koha::Object->update method -- You are receiving this mail because: You are watching all bug changes.

1 137

[Bug 28245] New: Language dropdown in advanced search should be sorted
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28245 Bug ID: 28245 Summary: Language dropdown in advanced search should be sorted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The Language dropdown in the advanced search should be sorted. It should be sorted according to the locale of the user. For instance, sorting by iso 629-2 codes favours English. Take for example "German". The code is "ger" and in English it's "German" but in French it's "Allemand", and in German it's "Deutsch". The alphabetical sort should be done to align with the expectations of the language of the user/interface. I'm not sure what to do about non-alphabetic languages like Chinese that don't do alphabetic sorting... Also, this is neat https://perldoc.perl.org/Unicode::Collate::Locale. A core module which adds support for locales. That said, sort for French is weird. The first is normal sort() and the second is Unicode::Collate::Locale sort. $VAR1 = [ 'a', 'e', 'ç', 'é', 'ï' ]; $VAR1 = [ 'a', 'ç', 'ï', 'é', 'e' ]; -- You are receiving this mail because: You are watching all bug changes.

1 2