February 2025 - Koha-bugs - lists.koha-community.org

[Bug 36157] New: Links in the "Run with template" dropdown at guided_reports.pl have odd formatting
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36157 Bug ID: 36157 Summary: Links in the "Run with template" dropdown at guided_reports.pl have odd formatting 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: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 162385 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=162385&action=e… Dropdown formatting differences When using the feature added by bug 34136, the new "Run with template" dropdown has btn classes on the links in the dropdown list which gives it odd formatting compared to the rest of the dropdowns in the toolbar. I attached a screenshot to hopefully better illustrate. To replicate: - Create a notice with the module of "Reports" -- add something to the "Print" section. Example from the other bug: [% FOREACH b IN data %] <div class="panel panel-default"> <div class="panel-heading">[% b.surname %], [% b.firstname %]</div> <div class="panel-body">Expiration: [% b.dateexpiry %]</div> <div class="panel-footer">ID: [% b.borrowernumber %]</div> </div> [% END %] - Create and run a saved report. Example from the other bug: SELECT * FROM borrowers - Click on the "Run with template" dropdown and hover the template title. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 36156] New: Duplicate selected value when a field or subfield is cloned
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36156 Bug ID: 36156 Summary: Duplicate selected value when a field or subfield is cloned Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello all, I'm surprised I haven't seen a bug about this, so I'm not 100% sure it's a bug, but I find the behavior inappropriate. When a field or subfield is linked to a list of authorised values (and therefore a select) and is repeatable, the selected value from the select is repeated in the clone. It would be more appropriate to leave the field empty. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 25539] New: Remove AddBiblio "defer_marc_save" option
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25539 Bug ID: 25539 Summary: Remove AddBiblio "defer_marc_save" option 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In bulkmarcimoprt.pl AddBiblio is called with defer_marc_save => 1. This perhaps made sense sometime when items where saved embedded with the MARCXML, but since that is no longer the case(?) there is no need for saving the MARC-data once more after processing items in bulkmarcimport.pl. Thus this option can/should be removed. The current behavior actually blocks bug 14957, we recently discovered, since calling ModBiblioMarc after the record has been saved bypasses marc merge rules on updates (which are applied in ModBiblio) and that save will ignore the possible rules that has been setup. I also discovered some other odd things that will not address in this bug. One of the being that since ModBiblio runs _strip_item_fields no items will ever be imported though bulkmarcimport on updates (but will be in inserts). I'm pretty sure this is the case (have tested and verified, but seems odd this kind of bug has survived undetected for so long). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 106

[Bug 30349] New: cleanup bulkmarcimport.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30349 Bug ID: 30349 Summary: cleanup bulkmarcimport.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: davewood(a)gmx.at QA Contact: testopia(a)bugs.koha-community.org the help page of bulkmarcimport.pl doesnt use double dashes for multi-character options. Id like to update the help info and add multi-character options where they are missing. (e.g. --help for -h) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 29440] New: Refactor/clean up bulkmarcimport.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29440 Bug ID: 29440 Summary: Refactor/clean up bulkmarcimport.pl 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In order to address various issues with and add some new features to bulkmarcimport.pl I found it necessary to first clean up the script. At our library we run a modified version of bulkmarcimport.pl that for practical reasons was squashed into one commit. I have split this commit into various feature branches, all which depends on the clean up version of the script. So in the first commit of this issue I tried to isolate all the changes that should not affect current script behavior and are mostly related to code formatting, structure and optimizations. The next commits (for this issue) will contain changes that do affect script behavior, but that I would argue should be the default behavior and where the current could be considered confusing and/or buggy. I will later create new related issues for the newly added features mentioned above (and it's possible there is stuff in this patch that should have been broken out and I have overlooked). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 132

[Bug 35962] New: t/db_dependent/Koha/BackgroundJob.t failing on D10
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35962 Bug ID: 35962 Summary: t/db_dependent/Koha/BackgroundJob.t failing on D10 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Not failing locally, but on D10: koha_1 | koha_1 | # Failed test 'Enqueue MARCImportCommitBatch with mock throws exception' koha_1 | # at t/db_dependent/Koha/BackgroundJob.t line 85. koha_1 | # expecting: Koha::Exceptions::BackgroundJob koha_1 | # found: normal exit koha_1 | # Looks like you planned 10 tests but ran 2. koha_1 | # Looks like you failed 1 test of 2 run. koha_1 | koha_1 | # Failed test 'enqueue() tests' koha_1 | # at t/db_dependent/Koha/BackgroundJob.t line 128. koha_1 | Can't locate object method "unmock" via package "0" (perhaps you forgot to load "0"?) at t/db_dependent/Koha/BackgroundJob.t line 87. koha_1 | # Looks like your test exited with 255 just after 2. koha_1 | [14:12:00] t/db_dependent/Koha/BackgroundJob.t ......................................... koha_1 | Dubious, test returned 255 (wstat 65280, 0xff00) koha_1 | Failed 4/5 subtests Coudl this be related to bug 35507 or bug 30734? -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 35843] New: No such thing as Koha::Exceptions::Exception
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35843 Bug ID: 35843 Summary: No such thing as Koha::Exceptions::Exception Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org On Koha 22.11.04-1 installed with the Debian packages I have some background jobs that are failing, and I see this in the logs: ==> /var/log/koha/mykoha/plack-intranet-error.log <== [2024/01/19 08:47:02] [WARN] The job has not been sent to the message broker: (Can't locate object method "throw" via package "Koha::Exceptions::Exception" (perhaps you forgot to load "Koha::Exceptions::Exception"?) at /usr/share/koha/lib/Koha/BackgroundJob.pm line 141. ) at /usr/share/koha/lib/Koha/BackgroundJob.pm line 148. The relevant code looks like this: 134 try { 135 # This namespace is wrong, it must be a vhost instead. 136 # But to do so it needs to be created on the server => much more work when a new Koha instance is created. 137 # Also, here we just want the Koha instance's name, but it's not in the config... 138 # Picking a random id (memcached_namespace) from the config 139 my $namespace = C4::Context->config('memcached_namespace'); 140 my $encoded_args = Encode::encode_utf8( $json_args ); # FIXME We should better leave this to Net::Stomp? 141 $conn->send_with_receipt( { destination => sprintf("/queue/%s-%s", $namespace, $job_queue), body => $encoded_args } ) 142 or Koha::Exceptions::Exception->throw('Job has not been enqueued'); 143 } catch { 144 $self->status('failed')->store; 145 if ( ref($_) eq 'Koha::Exceptions::Exception' ) { 146 $_->rethrow; 147 } else { 148 warn sprintf "The job has not been sent to the message broker: (%s)", $_; 149 } 150 }; This code is the only place Koha::Exceptions::Exception is mentioned in the code: $ sudo grep -rn "Koha::Exceptions::Exception" /usr/share/koha/ /usr/share/koha/lib/Koha/BackgroundJob.pm:142: or Koha::Exceptions::Exception->throw('Job has not been enqueued'); /usr/share/koha/lib/Koha/BackgroundJob.pm:145: if ( ref($_) eq 'Koha::Exceptions::Exception' ) { -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 29510] New: objects.find should call search_limited if present
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29510 Bug ID: 29510 Summary: objects.find should call search_limited if present 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: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 34479] New: Clear saved patron search selections after certain actions
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34479 Bug ID: 34479 Summary: Clear saved patron search selections after certain actions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: cslone(a)camdencountylibrary.org, gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, testopia(a)bugs.koha-community.org Depends on: 29971 +++ This bug was initially created as a clone of Bug #29971 +++ (In reply to Chris Slone from comment #17) > I think this is a problematic implementation, as it seems to be retaining > the selected patrons even after you perform a function (merge patrons, > create a list, do a batch edit) and do a completely new search. This means > that the previously selected patrons remain selected even when it doesn't > really make logical sense. It's great to be able to select multiple patrons > across different searches, but doing something like merging accounts should > absolutely clear out that selection. > > It seems to already be causing some issues, see this ticket: > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34262 > > We've also had some errors at our library from this (before we realized what > was happening). I'm moving this issue into a new bug report because we don't re-open bugs for features which have been pushed. This will let us have a discussion about refining the behavior. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29971 [Bug 29971] Remember selections across patron search pages -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 35341] New: Circulation rule dates are being overwritten
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35341 Bug ID: 35341 Summary: Circulation rule dates are being overwritten Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When setting either the "Hard due date" or the "No automatic renewal after (hard limit)" columns - if only one is amended then the other will be overwritten with the value of the last rule that was in the editor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 68