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

[Bug 25008] New: Koha::RecordProcessor->options doesn't refresh the filters
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25008 Bug ID: 25008 Summary: Koha::RecordProcessor->options doesn't refresh the filters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On testing something in opac-showmarc.pl I noticed it wasn't applying the ViewPolicy filter! And it seems the way the record processor is used is to blame. I plan to submit a fix for opac-showmarc.pl but thought it was worth filing a bug against Koha::RecordProcessor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 25038] New: OPAC reading history checkouts and on-site tabs not working
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25038 Bug ID: 25038 Summary: OPAC reading history checkouts and on-site tabs not working Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org OPAC reading history table has three tabs for different checkout types: All, Checkouts, On-site checkouts. However, all of your checkouts are visible every tab regardless of checkout type. To reproduce: 1. Enable OnSiteCheckouts system preference 2. Perform two checkouts: one normal checkout, one on-site checkout 3. Go to OPAC /cgi-bin/koha/opac-readingrecord.pl 4. Observe your checkouts all are visible in every tab (All, Checkouts, On-site checkouts) -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 24966] New: Fix calls to maybe_add where method call does not return a value
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24966 Bug ID: 24966 Summary: Fix calls to maybe_add where method call does not return a value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com For reasons unknown to me, a call like: -- $resp .= maybe_add( FID_CALL_NUMBER, $item->call_number, $server ); -- will not work as expected if the item has no callnumber. One would expect the parameters to the subroutine to be: 'CY', under, and a SIPServer object. What is actually received is: 'CY', and a SIPServer object. We ingest the parameters like so: -- sub maybe_add { my ($fid, $value, $server) = @_; -- So, what happens is $value is populated with the server object! This can cause bad output like this: -- OUTPUT MSG: '101YNN20200324 063701AOBPL|AB32503201584185|AQBPL|AJCat /|CK001|CRn|CSJ 636.8 CLU|CYC4::SIP::SIPServer=HASH(0x1ea0e58)|DAC4::SIP::SIPServer=HASH(0x1ea0e58)|'--- I do not know why this is happening, but there are a couple solutions: 1) Move the $server parameter to be the first parameter of the subroutine call 2) Check the value of $value and swap $value and $server if it is the server object. I will write a patch implementing the latter solution, as it is a two line change, versus a many line change for the former. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 25050] New: Elasticsearch - authority indexing depends on mapping order
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25050 Bug ID: 25050 Summary: Elasticsearch - authority indexing depends on mapping order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com There is an assumption in the ES code that match-heading mappings will appear in a specified portion of the mappings array. Certain mappings setups will not meet this assumption. We need to move our searching up one level -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 24266] New: Noisy error in reconcile_balances.pl
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24266 Bug ID: 24266 Summary: Noisy error in reconcile_balances.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Cron <instance-koha@kohaMain> $KOHA_CRON_PATH/reconcile_balances.pl --verbose Gives this message when run: SQL::Abstract::puke(): [SQL::Abstract::__ANON__] Fatal: SQL::Abstract before v1.75 used to generate incorrect SQL when the -IN operator was given an undef-containing list: !!!AUDIT YOUR CODE AND DATA!!! (the upcoming Data::Query-based version of SQL::Abstract will emit the logically correct SQL instead of raising this exception) at /usr/share/koha/lib/Koha/Objects.pm line 209 It would be nice if this wouldn't happen, so that cron doesn't send mails about this error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 25095] New: Remove warn left in FeePayment.pm
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25095 Bug ID: 25095 Summary: Remove warn left in FeePayment.pm 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It appears that a debugging statement was accidentally left in FeePayment.pm by bug 5605. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 22778] New: Suggestions with no "suggester" can cause errors
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22778 Bug ID: 22778 Summary: Suggestions with no "suggester" can cause errors Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- If one tries to modify a suggestion that has no suggester you will get the following error: Can't call method "lang" on an undefined value at /usr/share/koha/lib/C4/Suggestions.pm line 506 Koha assumes that every suggestion has a borrowernumber in suggestedb.y -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 25188] New: Circulation notes only displays on checkouts tab, but not on details
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25188 Bug ID: 25188 Summary: Circulation notes only displays on checkouts tab, but not on details 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: 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 When a patron note is added via "Add message" it displays on both the checkouts and the details tab. But a circulation note (Edit patron...) is only displayed on the checkouts tab. It would be nice if the circulation note also showed on the details tab. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 23787] New: AUTO_RENEWALS is not in sample_notices.sql
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23787 Bug ID: 23787 Summary: AUTO_RENEWALS is not in sample_notices.sql Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices 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 wanted to translate the AUTO_RENEWALS notice, but it's not in the sample_notices.sql. It is only in the updatedatabase.pl Martin confirmed on IRC that it should be in both. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 20884] New: Stale data remaining in cache after koha-remove
by bugzilla-daemon＠bugs.koha-community.org 13 May '20

13 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20884 Bug ID: 20884 Summary: Stale data remaining in cache after koha-remove Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jcharaoui(a)cmaisonneuve.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Created attachment 75836 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75836&action=ed… 0001-Restart-memcached-after-koha-remove-if-needed.patch After running koha-remove, stale data remains in within the memcached server. Say if an instance is deleted then recreated immediately, changed data such as database credentials isn't loaded into the cache, resulting in strange, difficult to troubleshoot problems. The solution would be to flush memcached cache at the end of koha-remove. The most straightforward method to do this is simply restart the service. See attached patch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13