October 2020 - Koha-bugs - lists.koha-community.org

[Bug 21357] New: Filter elisions from index and search terms in Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21357 Bug ID: 21357 Summary: Filter elisions from index and search terms in Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: ere.maijala(a)helsinki.fi To make searching easier at least in French, it would be nice to have the default configuration handle elisions properly (e.g. l'avion). Coming up with a proposed patch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 104

[Bug 24841] New: REST API should check if patron is restricted/debarred
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24841 Bug ID: 24841 Summary: REST API should check if patron is restricted/debarred Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Bug 17247 "ILS-DI HoldTitle and HoldItem should check if patron is restricted" adds checks to see if the patron is restricted before a hold is placed. These checks are added to C4::ILSDI::Services::HoldItem() and C4::ILSDI::Services::HoldTitle(). As far as I can tell, the same checks are missing from the REST API, specifically for "POST /api/v1/holds". Koha::REST::V1::Holds::add() does call C4::Reserves::CanItemBeReserved() and C4::Reserves::CanBookBeReserved(), but as far as I can tell, those subs do not check if the patron in question is debarred. Am I missing something or is this a bug? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26038] New: Accessibility: 4.1.3 Status Messages
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26038 Bug ID: 26038 Summary: Accessibility: 4.1.3 Status Messages 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org Blocks: 23003 The intent of this Success Criterion is to make users aware of important changes in content that are not given focus, and to do so in a way that doesn't unnecessarily interrupt their work. The intended beneficiaries are blind and low vision users of assistive technologies with screen reader capabilities. An additional benefit is that assistive technologies for users with cognitive disabilities may achieve an alternative means of indicating (or even delaying or supressing) status messages, as preferred by the user. The scope of this Success Criterion is specific to changes in content that involve status messages. A status message is a defined term in WCAG. There are two main criteria that determine whether something meets the definition of a status message: https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 [Bug 23003] Accessibility improvements -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 18303] New: Release team omnibus
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18303 Bug ID: 18303 Summary: Release team omnibus Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: nengard(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 25071] New: Explain close budget vs make budget inactive
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25071 Bug ID: 25071 Summary: Explain close budget vs make budget inactive Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I noticed that if you try to close a budget with no unreceived orders, it doesn't work. You have to go edit the budget and make it inactive. I didn't test to see if you close a budget with unreceived orders, if it also makes it inactive or if you have to edit the budget to make it inactive after rolling over your unreceived orders. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 16559] New: [%% ... %%] should not be picked for translation
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '25

27 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16559 Bug ID: 16559 Summary: [%% ... %%] should not be picked for translation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Examples in Koha 16.05: %s [%% INCLUDE "openlibrary-readapi.inc" bib = { normalized_isbn => normalized_isbn, lccn => lccn, normalized_oclc => normalized_oclc } %%] %s [%% UNLESS hidden.defined('phone') && hidden.defined('phonepro') && hidden.defined('mobile') && hidden.defined('email') && hidden.defined('emailpro') && hidden.defined('fax') %%] In Pootle, a search for [%% has 40 results -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 19523] New: Koha:: Cache changes not passed to all plack workers with in-memory caching.
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '25

27 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19523 Bug ID: 19523 Summary: Koha::Cache changes not passed to all plack workers with in-memory caching. 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org REPRODUCE: - $KOHA_CONF shouldn't have any <memcached_* -definitions. This triggers in-memory cache usage. - plack workers is atleast 2 - Change some easily visible syspref, such as 'languages'. The syspref change applies only to the worker thread where the change was made. Other worker threads keep using the old syspref. - Observer that 50% of time the old syspref is used. Other times the new syspref is used. - Reduce plack workers to 1. Observe no issues with syspref change taking effect. Using memcached solves this problem. It is still useful to fix it for those who don't want to use memcached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 24865] New: Customize the Accountlines Description
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24865 Bug ID: 24865 Summary: Customize the Accountlines Description Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great if we could customize what information was added to the "Description of charges" field when a fine was made so data could be stored even when the item is deleted. For example if you would like to be able to store the home library code, title, and barcode even if the item was deleted, you could have it e entered automatically when the fine was created. This would be very helpful to us. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 23336] New: Add an API endpoint for issuing an item to a patron
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 Bug ID: 23336 Summary: Add an API endpoint for issuing an item to a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com The Checkouts API route RFC (https://wiki.koha-community.org/wiki/Checkouts_endpoint_RFC) proposes a POST on /checkouts, which makes sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 107

[Bug 25098] New: automatic item modification needs report function
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25098 Bug ID: 25098 Summary: automatic item modification needs report function Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The automatic item modification cronjob does not have an option for reporting the items that were modified. Can the cronjob log in action_logs, or as a report that's emailed, or into a logfile that can be downloaded? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13