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

[Bug 24037] New: Koha manual missing System Preference documentation for GDPR
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '21

24 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24037 Bug ID: 24037 Summary: Koha manual missing System Preference documentation for GDPR Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With the new system preference in 19.05 that works with GDPR, it was brought to our attention that the original system preference GDPR_policy is not in the 18.11 manual. It is in the 19.05 manual. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24055] New: Description of PayPalReturnURL system preference is unclear
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '21

24 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24055 Bug ID: 24055 Summary: Description of PayPalReturnURL system preference is unclear Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial 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 PayPalReturnURL says: After payment or cancellation, PayPal should return to the␠OPAC's alias It's not clear what is meant by OPAC's alias. Could this be rephrased or an example be added to make this clearer? -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 17179] New: Add keyboard shortcuts to repeat (duplicate) a field, and cut text
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '21

24 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17179 Bug ID: 17179 Summary: Add keyboard shortcuts to repeat (duplicate) a field, and cut text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl add two more keyboard shortcut commands to the list already available: Ctrl-R : Repeat or duplicate a field Ctrl-C : cut command (to be used with paste - Ctrl-V) -- You are receiving this mail because: You are watching all bug changes.

1 56

[Bug 23403] New: SIP2 lends to wrong patron if cardnumber is missing
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '21

23 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23403 Bug ID: 23403 Summary: SIP2 lends to wrong patron if cardnumber is missing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To reproduce: Make sure you have two borrowers with no cardnumber, but with a userid. Determine which of the two patrons has the *highest* borrowernumber and lend a book to this patron via SIP2. If you do not have a SIP2 self check machine on hand you can do it thusly on the command line: $ telnet localhost <SIP2 port number> > 9300CN<SIP2 username>|CO<SIP2 password>|CP<library code>| > 11NN20190731 14163520190731 141635AO<library code>|AA<userid>|AB<barcode>|ACmy password|AD| Now check who the book is actually on loan to. In my testing it has been the patron without a cardnumber that has the lowest borrowernumber! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 24227] New: System Preference: EmailPurchaseSuggestion missing from the 19.05 manual
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '21

23 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24227 Bug ID: 24227 Summary: System Preference: EmailPurchaseSuggestion missing from the 19.05 manual Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The system preference, EmailPurchaseSuggestion is missing from the 19.05 (and 19.11) manual. Here is the information needed for this system preference There are two new system preferences that work together on this new feature: EmailPurchaseSuggestions &EmailAddressForSuggestions There are a few options for the first system preference, EmailPurchaseSuggestion. The email can be sent: -None -Email Address of Branch (found in the Libraries section of Admin) -Email address for Suggestions - which if chosen, then the next system preference will be used -Koha Admin Email Address- which is an email in the system preference, KohaAdminEmail. If a library would like to use an email separate from either the Email Address of the Branch ore the Koha Admin Email Address, then the next system preference, EmailAddressforSuggestions, should be filled in. If a library does not want to be emailed when a purchase suggestion has been made, a library would choose None (which will be set as the default on an upgrade). There is a new notice that is called New_Suggestion for this email. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20410] New: Remove OpacGroupResults system preference and feature
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '21

22 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20410 Bug ID: 20410 Summary: Remove OpacGroupResults system preference and feature Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org This is used only once according to HEA, but i am pretty sure this doesn't work, and probably never will. I suggest removing it entirely. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 23947] New: Phase out jquery.cookie.js: Authority merge
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '21

22 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23947 Bug ID: 23947 Summary: Phase out jquery.cookie.js: Authority merge Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 23944 The authority merge process sets cookes to track which records are being merged. This process should use the newer cookie library, js-cookie. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23944 [Bug 23944] Phase out use of jquery.cookie.js in favor of js.cookie.js -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 18146] New: C4:: Circulation CanBookBeRenewed lacks full test coverage.
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '21

19 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18146 Bug ID: 18146 Summary: C4::Circulation CanBookBeRenewed lacks full test coverage. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: mtompset(a)hotmail.com QA Contact: gmcharlt(a)gmail.com While testing bug 17941, I discovered two cases where test coverage was lacking from t/db_dependent/Circulation.t Around line 2725: if ( $restricted and $restrictionblockrenewing ) { return ( 0, 'restriction'); } elsif ( ($hasoverdues and $overduesblockrenewing eq 'block') || ($itemissue->{overdue} and $overduesblockrenewing eq 'blockitem') ) { return ( 0, 'overdue'); } The elseif is never triggered. Around line 2759: if ( $soonestrenewal > DateTime->now( time_zone => C4::Context->tz() ) ) { return ( 0, "auto_too_soon" ) if $itemissue->{auto_renew}; return ( 0, "too_soon" ); } elsif ( $itemissue->{auto_renew} ) { return ( 0, "auto_renew" ); } There is no else, but the code never attempts something that would trigger one. To reproduce add: print STDERR "CHECK!\n"; just before the return ( 0, 'overdue') in the first case, and after the elsif's curly brace in the second case. running t/db_dependent/Circulation should not generate the CHECK points. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 22713] New: Replacement price removed when receiving if using MarcItemFieldstoOrder
by bugzilla-daemon＠bugs.koha-community.org 17 Feb '21

17 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22713 Bug ID: 22713 Summary: Replacement price removed when receiving if using MarcItemFieldstoOrder Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: nick(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 88048 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=88048&action=ed… replacement price in item record acq process In 18.11 the wording and functionality changed in Acquisitions with the field Replacement price. This allowed libraries to have their replacement price set in the Acquisitions order and also in the item record. However, if a library is using MarcItemFieldstoOrder system preference and setting their replacement price in the marc record upon Importing. The replacement price only stays on the Item Record and will not be included into the Acquisitions order and it won't populate into the receiving process- and therefore making it $0. It would be nice if the item record had the replacement price from the MarcItemFieldstoOrder, and this would follow it through the process and since it is there in the item, it be used in the Order. Process currently: 1. Set marcitemfieldstorder to have a $v replacement price (975$v) 2. Create a basket 3. Upload a marc file that has a replacement price in the record 4. Add this file to your basket. 5. The item record will display the replacement price. 6. The basket.pl will not display the replacement price of this item 7. CLose the basket 8. When receiving the item in Acquisitions, the replacement price is zeroed out 9. The item will not have a replacement price once it is received. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 22838] New: Warning from runreport.pl 'Explicitly setting a MIME header field (content-type) is dangerous'
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '21

16 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22838 Bug ID: 22838 Summary: Warning from runreport.pl 'Explicitly setting a MIME header field (content-type) is dangerous' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- Explicitly setting a MIME header field (content-type) is dangerous: use the attr() method instead. at misc/cronjobs/runreport.pl line 312. It seems the error comes from Koha/Email.pm: 72 $mail{'Content-Type'} = $params->{contenttype} if $params->{contenttype}; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13