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

[Bug 27739] New: Advanced editor should use DefaultCountryField008 system preference rather than hardcoding xxu
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27739 Bug ID: 27739 Summary: Advanced editor should use DefaultCountryField008 system preference rather than hardcoding xxu 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: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 27738 cateditor-widgets-marc21.inc uses DefaultLanguageField008 for the initial value of the language in 008/35-37, but just hardcodes xxu rather than using the companion pref DefaultCountryField008 for 008/15-17. Since using the pref requires a fallback when it's unset, and bug 27738 proposes changing the current fallback in the basic editor, this bug should wait on an outcome there before being fixed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27738 [Bug 27738] Set fallback for unset DefaultCountryField008 to |||, "no attempt to code" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 28118] New: Fix missing "selected" attribute in "Pickup at" dropdown
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28118 Bug ID: 28118 Summary: Fix missing "selected" attribute in "Pickup at" dropdown Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In 20.05.06, when i find a record, click on "Place hold" and search for a patron, I get a form that contains a dropdown labeled "Pickup at". This dropdown has a "selected" attribute on one of the libraries: <select name="pickup" size="1" id="pickup"> <option value="A" selected="selected">A public library</option> <option value="B">B public library</option> </select> In 20.05.10 and 20.12.00.027 (current master), this "selected" attribute seems to be missing. I have not looked deeply at how different settings might affect which library is selected, but I think either way, one library should always be selected? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 28112] New: Z39.50 does not populate form with all passed criteria
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28112 Bug ID: 28112 Summary: Z39.50 does not populate form with all passed criteria Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 1277 Bug 1277 added options to the Z39.50 search form but didn't take into account that search terms for those new fields might be passed in the URL. For example, a URL containing all possible fields: /cgi-bin/koha/cataloguing/z3950_search.pl?frameworkcode=&isbn=isbn&issn=issn&title=title&author=author&dewey=dewey&subject=subject&lccall=lccall&controlnumber=controlnumber&stdid=stdid&srchany=srchany&publicationyear=publicationyear ...should bring up a form which has values in every field. Instead, these fields are empty: Subject heading Keyword (any) LC call number Control no. Dewey Standard ID Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1277 [Bug 1277] Enhance: Z39.50 More search criteria -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28121] New: Wrong ponctuation on desk deletion
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28121 Bug ID: 28121 Summary: Wrong ponctuation on desk deletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Question mark is wrongly placed when you want to delete a desk, for example : Delete desk "Accueil?" It should be placed after quotation mark. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 27726] New: OPACProblemReports cuts off message text
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27726 Bug ID: 27726 Summary: OPACProblemReports cuts off message text Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: hannah.co(a)northwestu.edu QA Contact: testopia(a)bugs.koha-community.org OPACProblemReport text is truncated to 255 characters, in both database and email. I tested and confirmed that the patron-facing form does not limit the amount of text entered, at least not before more than 500 characters. The form should either limit characters and warn patrons of the character limit, or the database field should be expanded to allow more data storage. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 28094] New: Fix bad encoding of OVERRIDE_SYSPREF_LibraryName
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28094 Bug ID: 28094 Summary: Fix bad encoding of OVERRIDE_SYSPREF_LibraryName Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org I am creating alternative OPACs for a Koha site using the SetEnv techniques. When I set this in the Apache config: RequestHeader add X-Koha-SetEnv "OVERRIDE_SYSPREF_LibraryName Slægtsforskernes Bibliotek" there is a problem with the encoding, the name is displayed like this: SlÃ¦gtsforskernes Bibliotek If I try to replace the "æ" with æ, that text is displayed as is, and not replaced by the proper letter: Slægtsforskernes Bibliotek Anyone got a clue how to fix this? -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 28097] New: t/db_dependent/Koha/Account/Line.t test fails with FinesMode set to calculate
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28097 Bug ID: 28097 Summary: t/db_dependent/Koha/Account/Line.t test fails with FinesMode set to calculate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - Confirm finesmode is set to do not calculate - prove t/db_dependent/Koha/Account/Line.t - it passes! - set FinesMode ot calculate and charge - prove t/db_dependent/Koha/Account/Line.t - it fails root@kohadevbox:koha(master)$ prove t/db_dependent/Koha/Account/Line.t t/db_dependent/Koha/Account/Line.t .. 7/14 # Looks like you planned 6 tests but ran 3. # Failed test 'checkout() tests' # at t/db_dependent/Koha/Account/Line.t line 615. Can't call method "checkout" on an undefined value at t/db_dependent/Koha/Account/Line.t line 607. # Looks like your test exited with 255 just after 9. t/db_dependent/Koha/Account/Line.t .. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 6/14 subtests Test Summary Report ------------------- t/db_dependent/Koha/Account/Line.t (Wstat: 65280 Tests: 9 Failed: 1) Failed test: 9 Non-zero exit status: 255 Parse errors: Bad plan. You planned 14 tests but ran 9. Files=1, Tests=9, 5 wallclock secs ( 0.02 usr 0.01 sys + 3.32 cusr 0.65 csys = 4.00 CPU) Result: FAIL -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 27991] New: Message field for OPAC problem reporting should have a maxlength set
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27991 Bug ID: 27991 Summary: Message field for OPAC problem reporting should have a maxlength set 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: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org Currently when a user is submitting a problem report via the OPAC at opac-reportproblem.pl, they can write as much as they want in the "message" field. When the report is submitted, only the first 255 characters are kept due to the field size of problem_reports.content which can result in a cut off message. It would be good to set a maxlength for the field and also make users aware of the limit. I'm using jQuery to set the maxlength attribute and add a character countdown so users know exactly how much they can type. //Problem Reporting $(document).ready(function() { //Enforce character limit on message field $('#opac-reportproblem #message').attr('maxlength', '255'); //Add character countdown $('#opac-reportproblem #message').after('<span id="charcounter">255</span> characters remaining'); //Update character countdown as data is entered var maxLength = 255; $('#opac-reportproblem #message').keyup(function() { var length = $(this).val().length; var length = maxLength-length; $('#opac-reportproblem #charcounter').text(length); }); }); -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 28077] New: Missing colon on suggestion modification page
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28077 Bug ID: 28077 Summary: Missing colon on suggestion modification page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org On the 'Edit purchase suggestion' page, a colon is missing after the 'Reason' label. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 28044] New: Calendar: Tables with closed days are no longer color coded
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28044 Bug ID: 28044 Summary: Calendar: Tables with closed days are no longer color coded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: oleonard(a)myacpl.org Maybe I missed a recent change here, but the tables on the calendar page no longer appear color coded. When you reload the page, you can see the color is there for a second and then disappears. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12