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

[Bug 30554] New: Wrong display of authorities records in the Authority search plugin
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30554 Bug ID: 30554 Summary: Wrong display of authorities records in the Authority search plugin Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.breuillard(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Once the search is done with this plugin some of the authorities are wrong displayed because parts and links are missing. It is not the case if the search is made via authority mobile -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[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 31081] New: Improve display of 'Manage bundle' button
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '25

29 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31081 Bug ID: 31081 Summary: Improve display of 'Manage bundle' button Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 28854 When a potential bundle item (on a record with bib level = c), has no bundled items, the button shows as: Manage bundle (|). It might be nicer to make this (0|0) or better not to display this part, if there is nothing bundled yet. It might also be nice to add a tooltip explaining about what the first and second number mean. First number: items lost Second number: items total Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28854 [Bug 28854] Add ability to create bundles of items -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[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 30674] New: x-koha-override should use collectionFormat: csv
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30674 Bug ID: 30674 Summary: x-koha-override should use collectionFormat: csv 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: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Now that we use a fixed version of the stack, we should fix this. Bug 30663 already implements overrides like this and we should, for consistency, use it in the other occurences. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 28575] New: Add ability to choose if lost fee is refunded based on when lost fee was paid off
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28575 Bug ID: 28575 Summary: Add ability to choose if lost fee is refunded based on when lost fee was paid off Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In bug 20815 we added the NoRefundOnLostReturnedItemsAge system preference to block lost item refunds if the item was lost more than X daya ago. Many libraries would like a comparable system to block refund if the lost item fee has been paid in full more than X days ago. Further, even more libraries have asked for the ability to simply not refund paid lost items at all (they only want to refund/forgive lost fees that are not yet paid). Enabling this new syspref to block refunds on lost items paid off more than 0 days ago would support this behavior. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 31211] New: Check slips and notices for valid Template Toolkit and report errors
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31211 Bug ID: 31211 Summary: Check slips and notices for valid Template Toolkit and report errors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful for Koha to run a basic TT validation test and report back errors. That way if somebody misses an END tag or something of that nature, it will be easy to find and fix. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20