March 2023 - Koha-bugs - lists.koha-community.org

[Bug 18675] New: Translatability: Get rid of [ %% in translation for csv-profiles.tt
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '25

01 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18675 Bug ID: 18675 Summary: Translatability: Get rid of [%% in translation for csv-profiles.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial 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 Translation tool for file csv-profiles.tt picks following line: %s [%% IF csv_profile.encoding == encoding OR NOT csv_profile AND encoding == 'utf8' %%] This is due to a line break inside a template directive. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 26383] New: Koha::Patron->is_superlibrarian is not optimal
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '25

01 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26383 Bug ID: 26383 Summary: Koha::Patron->is_superlibrarian is not optimal Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 23634 It must not call $self->has_permission which does a DB request. C4::Context::IsSuperLibrarian is what must be done: $self->flags % 2 It could be good to replace the occurrence of IsSuperLibrarian at the same time, it's a bad pattern to have twice the same method to check for this superpower. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23634 [Bug 23634] Privilege escalation vulnerability for staff users with 'edit_borrowers' permission and 'OpacResetPassword' enabled -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 18711] New: No longer possible have a blank value for Classification Sources in the Administration Module
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '25

01 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18711 Bug ID: 18711 Summary: No longer possible have a blank value for Classification Sources in the Administration Module Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: karen(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Koha 3.22 it was possible to enter a blank value for Classification Sources in the Administration Module. In 16.11 it is no longer possible to enter a blank value. The expected behavior is that it would still be possible to enter a blank value. The SWITCH Library Consortium has requested the ability to keep the ability to add a blank value field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 32391] New: Reorganise the manual contents
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '25

01 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32391 Bug ID: 32391 Summary: Reorganise the manual contents 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The contents of the manual need reorganising/restructuring. Currently, the contents is a long list of modules/features/topics in a randomish order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 30526] New: The pagination in the REST API does not work if $c->objects->search is called multiple times.
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '25

29 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30526 Bug ID: 30526 Summary: The pagination in the REST API does not work if $c->objects->search is called multiple times. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se CC: tomascohen(a)gmail.com The REST-plugin Koha::REST::Plugin::Pagination defines two methods: dbic_merge_pagination and add_pagination_headers. The method add_pagination_headers use the helper subroutine _build_link. The last call in add_pagination_headers looks like this: push @links, _build_link( $c, { page => $pages, per_page => $per_page, rel => 'last', params => $args->{params} } ); Here is _build_link: sub _build_link { my ( $c, $args ) = @_; my $params = $args->{params}; $params->{_page} = $args->{page}; $params->{_per_page} = $args->{per_page}; Note that the original parameters _page and _per_page is overwritten here. This means that _page will be $pages. Subsequent calls to $c->objects->search will, thus, always return the last page. At least REST::V1::Holds::pickup_locations is affected by this (because a redundant call to $c->objects->search is made if AllowHoldPolicyOverride is activated). This causes the dropdown menu with pickup locations in the holds view to only contain the last page of libraries if there are more than 20 pickup libraries and AllowHoldPolicyOverride is activated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 29648] New: Replace NumSavedReports with table configuration setting
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29648 Bug ID: 29648 Summary: Replace NumSavedReports with table configuration setting 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Bug 29530 discussed, that the NumSavedReports would be better placed as an option in the table configuration settings. Using this as a pattern could also then help add this option to more tables. -- You are receiving this mail because: You are watching all bug changes.

1 266

[Bug 25938] New: Identify the renewal type in the renewal after_circ_action hook
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25938 Bug ID: 25938 Summary: Identify the renewal type in the renewal after_circ_action hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture 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 nice to be able to distinguish between autorenewal, opac, staff and SIP renewals in the after_circ_action renewal hook. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 30158] New: Add a QR code for the list of results when doing a research on the OPAC
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30158 Bug ID: 30158 Summary: Add a QR code for the list of results when doing a research on the OPAC Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Would it be possible to get a QR code for a list of results the same way we can scan one when we're on the details page for a single record ? -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 32617] New: Koha thinks a rule is currently being edited if All patron All type rule has a hard due date
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32617 Bug ID: 32617 Summary: Koha thinks a rule is currently being edited if All patron All type rule has a hard due date Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, I didn't know how to summerize this bug more than that as it is a VERY specific situation haha ! Context : When we are currently editing a rule and we don't save it and try to edit another rule, a message pops up and says : Are you sure you want to edit another rule? to alert us that we didn't save the rule we are editing. Problem : So if we have a rule with Patron category set to All and Item Type also set to All and this rule has a Hard Due Date, we always have the Are you sure you want to edit another rule? message that pops up when we want to edit a rule. The message pops up only if the All Patron and All type rule has a Hard Due date, I don't replicate if I set a Hard Due Date on another rule... I don't know if I explain that well so here's a test plan : 1. Create a rule with Patron Category and item type set to All with any other settings but don't set a Hard Due date 2. Create a rule with a specific Patron Category and a specific Item Type with any other settings 3. When both rules are saved, try to edit one of them. You will be able to do so as usual 4. Edit the All Patron All Item type rule and add a Hard Due Date. Save the rule. 5. Try to edit again any of the rule, you then have the Are you sure you want to edit another rule? as if we were currently editing a rule when in fact all rules are saved. 6. Delete the Hard Due Date on the All patron All Item Type rule and save the rule. 7. Try to edit a rule again and the message doesn't pop up. I tried that on 21.05 and then on ByWater's 22.05 demo and replicate the problem every time. Thank you -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31804] New: Filtering not working when searching for a basket number on the receive orders page
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31804 Bug ID: 31804 Summary: Filtering not working when searching for a basket number on the receive orders page Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Not a duplicate of bz31322 as I don't recreate the behaviour described. I am able to search with the box above the table and the box in every other colomn in the table, but not in the basket one. I don't have any kind of error or any kind of odd behaviour, the filtering just doesn't work when I am searching for a basket number. It seems to search only on the date. In previous version, searching for a basket number was filtering correctly the table. To recreate : Go to the receive orders page for any vendor Try searching for one of the basket number in the box above the table - Every line of the table disappear as if there was no basket with this number Try searching the same number in the Basket search box - same result Try searching for the date of the basket - appropriate lines are filtered Thank you -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2