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

[Bug 37577] New: Add additional fields support to ERM Packages
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '25

29 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37577 Bug ID: 37577 Summary: Add additional fields support to ERM Packages Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com After adding additional fields support to Licences (Bug 35287) we would love to see additional fields support for Packages. -- You are receiving this mail because: You are watching all bug changes.

1 37

[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 35339] New: numSearchRSSResults doesn't work
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35339 Bug ID: 35339 Summary: numSearchRSSResults doesn't work Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Preference numSearchRSSResults is supposed to limit the number of results in the RSS feed, but it doesn't. The RSS feed shows the number of results that is specified in OPACnumSearchResults instead. Test : 1. Fill numSearchRSSResults with a number, let's say 20. 2. Fill OPACnumSearchResults with a number, let's say 50. 3. Go to your OPAC and search for something with more than 50 results. 4. Click on the RSS feed button. The RSS feed will show 50 results instead of 20. -- You are receiving this mail because: You are watching all bug changes.

1 3

[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 33670] New: Changes from bz29146/bz30250 doesn't apply when duplicate record suspected
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33670 Bug ID: 33670 Summary: Changes from bz29146/bz30250 doesn't apply when duplicate record suspected Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bz29146/30250 changed the behavior of the default values to make it so they are only applied when creating a new record so if someone wanted to delete a field that had default valued in the framework, those informations wouldn't reappear when the record was saved. The old behavior seems to still apply when Koha detects a duplicate record. Test plan : 1. Have a framework with a default value in any non mandatory field. Make sure this field is visible in the editor. For my exemple I had "rdacontent" as the default value in subfield $2 of field 336. 2. Create a new record and delete the $2 that appears with my default value 3. Fill all the mandatory fields and in 245 write the title of an existing record in your catalogue to create a duplicate. 4. Save the record. The page will refresh and you'll have the "Duplicate record suspected" alert asking you if this is a new record or a duplicate. 5. Go to the field you deleted (336 in my exemple), the default value came back. To compare, do all of the same steps, but create a record that has no duplicate in the catalogue. When you save the record, the deleted field is not populated with the default values, it stays deleted as it should. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 33669] New: Adding options to ApplyFrameworkDefaults preference
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33669 Bug ID: 33669 Summary: Adding options to ApplyFrameworkDefaults preference Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi ! >From bz29146 and bz30250, a few changes have been made to enhance the way framework default values are applied in a record. But the changes made makes it impossible for someone to add quickly default values to a record they are editing since default values are applied only when a record is created. Before, when we saved a record, every empty field and/or subfield that had default values in the framework would get populated. Of course that was not ideal as someone could want to keep one of those field empty. But right now, if we edit a record, there is no way to populate those field... So I think a great way to keep the inhancement from 29146/30250 but to also have the option to add default values when editing a record (not only when creating one) would be to add two more options to ApplyFrameworkDefaults preference : - When repeating a field - When repeating a subfield This way, if my framework has a default value in field 336, for exemple, and I edit a record that has an empty 336 field, I could only use the "repeat this field" button to have a 336 field populated with my default values. The empty 336 would simply disappear when saving my record. And it would be the same for the subfield option, but having the two separated allows a bit more flexibility if a library wants to have default values when adding a complete field but not if they only repeat a subfield and vice versa. Thank you ! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 33583] New: Put back the biblionumber coloumn in batch records import table
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33583 Bug ID: 33583 Summary: Put back the biblionumber coloumn in batch records import table Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, In 21.05, the record column in the batch records import table displayed the biblionumber of the imported record. Now, this column displays 2 buttons : edit and view. It would be nice to keep those two buttons but also have the option to have the biblionumber displayed in that table. A couple of libraries would use this table to export a list of records to edit (add an image, edit the items, etc.) after the import. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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