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

[Bug 30704] New: Remove whitespace added by bug 29271
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '22

09 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30704 Bug ID: 30704 Summary: Remove whitespace added by bug 29271 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 29271 The patch set from bug 29271 added some unexpected whitespace to the cash register report export that should be removed again: Before patch set: Manager name;Patron cardnumber;Patron name;Transaction library;Transaction date;Transaction type;Notes;Amount;Title;Barcode;Item type koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;;LOST;;1.00;;; koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;;LOST;;3.00;;; koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;CREDIT;;;-343.00;;; koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;;LOST;;112.00;;; TOTAL ;;;;;;-227.00 After patch set: Manager name;Patron cardnumber;Patron name;Transaction library;Transaction date;Transaction type;Notes;Amount;Title;Barcode;Item type koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;Lost item;;1.00;;; koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;Lost item;;3.00;;; koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;Credit;;-343.00;;; koha;eda;Eda Eda;Centerville;2022-04-07T00:00:00;Lost item;;112.00;;; TOTAL;;;;;;;-227.00 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29271 [Bug 29271] Cash register report not displaying or exporting correctly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 29330] New: Koha cannot send emails with attachments
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '22

09 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29330 Bug ID: 29330 Summary: Koha cannot send emails with attachments Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org It looks like bug 22343 introduced a regression where the content_type from the database isn't used when creating a Koha::Email object when processing the message_queue table. Re-adding the content_type to the creation of the Koha::Email object should in theory fix this bug. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22343#c232 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 92

[Bug 31214] New: Regression: subfield code editable in MARC framework editor
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '22

09 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31214 Bug ID: 31214 Summary: Regression: subfield code editable in MARC framework editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)iki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 5917 The Subfield code field is incorrectly editable in the MARC framework subfield configuration page, on e.g. on the page http://localhost:8081/cgi-bin/koha/admin/marc_subfields_structure.pl?op=add… This is an regression from bug 5917 – When converting the old templating syntax to Template toolkit syntax some of the code was missed and the old syntax was left in the codebase. In marc koha-tmpl/intranet-tmpl/prog/en/modules/admin/marc_subfields_structure.tt the following line should be fixed: > [% IF ( subfieldcode == 0 || subfieldcode ) %] it should be > [% IF ( loo.subfieldcode == 0 || loo.subfieldcode ) %] Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5917 [Bug 5917] Switch Koha to use Template::Toolkit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 30673] New: Improve is_valid_date function for validating date strings
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '22

09 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30673 Bug ID: 30673 Summary: Improve is_valid_date function for validating date strings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The is_valid_date() function in calendar.js has two jobs: Confirm that the date string matches the current date format according to a regular expression; and confirm that the date is an actual date. Both must be true. For example: "2002-03-14" matches the date format "Y-m-d" and is a valid date -- valid date. "03/14/2002" doesn't match the date format "Y-m-d" even though it is a valid date -- invalid date. "38-44-2103" doesn't match the date format "Y-m-d" and isn't a valid date -- invalid date. is_valid_date() needs some changes in order for it to correctly handle custom date formats being specified which override the default date format (from the system preference). It also needs a new way to check that a date string represents a valid date. The old jQueryUI method looks similar but behaves differently. $.datepicker.parseDate() would throw an exception if the date were invalid. flatpickr.parseDate() will try to interpret an invalid date as if it were valid. For example: flatpickr.parseDate("2002-48-66", "Y-m-d") -> Date Sat Feb 04 2006 00:00:00 flatpickr.parseDate("2002-48-66", "m/d/Y") -> Date Mon Aug 02 2027 00:00:00 -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 30836] New: Elasticsearch mappings.yaml is out of sync with upgraded databases
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '22

09 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30836 Bug ID: 30836 Summary: Elasticsearch mappings.yaml is out of sync with upgraded databases 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We discovered on IRC today that the mappings.yaml default mappings for ES indexing has fallen out of sync with upgraded databases.. We need to create a DB update for each mappings change and we haven't been doing so. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 21092] New: Bad template in patron card creator can cause server issues
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '22

08 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21092 Bug ID: 21092 Summary: Bad template in patron card creator can cause server issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org While creating the PDF file for a patron card batch the CPU goes to 100% and brings the server down. We have seen this behaviour in 2 separate package installations running 17.11.07 so far. We have sadly not been able to make it happen in a dev environment. Filing the report in hope that someone has an idea or seen something similar that will help us to nail down the problem. So far we think the problem is related to 0 values in a patron card template. I will attach screenshots of the layout and patron card template used, when the problem appears. To test: - Add patron card template - Add patron card layout (or use existing) - Create batch of patrons - Export - Click on PDF link - Boom! There is no error, the system just keeps loading. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28371] New: Improve performance of XSLTParse4Display
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '22

08 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28371 Bug ID: 28371 Summary: Improve performance of XSLTParse4Display 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This routine is quite slow, and heavy on DB lookups -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 30756] New: Get skip block out of Koha_Authority.t and add TestBuilder
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '22

08 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30756 Bug ID: 30756 Summary: Get skip block out of Koha_Authority.t and add TestBuilder Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This test contains 3 skips on Jenkins. It uses a MARC file. We could quite easily resolve this with TestBuilder. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 20416] New: Remove hide_marc and advancedMARCeditor system preferences
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '22

08 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20416 Bug ID: 20416 Summary: Remove hide_marc and advancedMARCeditor system preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl These two system preferences allow small customizations of the cataloging interface, namely showing only labels, or only the numbers. I don't think it's any use, almost everyone has the same values according to hea, and i am pretty sure the few libraries who don't can deal with seeing a framework with tag numbers and labels. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 23190] New: Authority hierarchy display appears to be broken
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '22

08 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23190 Bug ID: 23190 Summary: Authority hierarchy display appears to be broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- We followed the instructions on bug 8523 comment 19, but we didn't manage to get a tree view: AuthDisplayHieararchy ON Example: 151 $aGermany 551 $a Baden-Württemberg $w h 151 $aBaden-Württemberg 551 $a Konstanz $w h 551 $a Germany $w g 151 $aKonstanz 551 $a Baden-Württemberg $w g 551 $a Fürstenberg $w h 551 $a Paradies $w h 151 $a Fürstenberg 551 $a Konstanz $w g 151 $a Paradies 551 $a Konstanz $w g The authority that is displayed shows as the only entry of the 'tree' abvove the record in staff and OPAC. Links have been cataloged in both directions. Screenshots from Owen on bug 21128 from 2018 suggest that the feature still worked at this time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11