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

[Bug 25641] New: Koha/XSLT/Base.t is failing on U20
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25641 Bug ID: 25641 Summary: Koha/XSLT/Base.t is failing on U20 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org kohadev-koha@a72d3d9a1f4d:/kohadevbox/koha$ prove t/db_dependent/Koha/XSLT/Base.t t/db_dependent/Koha/XSLT/Base.t .. 1/33 # Failed test 'Malformed XML warning correctly displayed' # at t/db_dependent/Koha/XSLT/Base.t line 87. # found warning: XSLT::Base: :1: parser error : Opening and ending tag mismatch: a line 0 and b # expected to find warning: (?^u:parser error : Opening and ending tag mismatch: a line 1 and b) # Failed test 'Malformed XML warning correctly displayed' # at t/db_dependent/Koha/XSLT/Base.t line 99. # found warning: XSLT::Base: :1: parser error : Opening and ending tag mismatch: a line 0 and b # expected to find warning: (?^u:parser error : Opening and ending tag mismatch: a line 1 and b) # Failed test 'Malformed XML warning correctly displayed' # at t/db_dependent/Koha/XSLT/Base.t line 104. # found warning: XSLT::Base: :1: parser error : Opening and ending tag mismatch: a line 0 and b # expected to find warning: (?^u:parser error : Opening and ending tag mismatch: a line 1 and b) # Failed test 'Malformed XML warning correctly displayed' # at t/db_dependent/Koha/XSLT/Base.t line 110. # found warning: XSLT::Base: :1: parser error : Opening and ending tag mismatch: a line 0 and b # expected to find warning: (?^u:parser error : Opening and ending tag mismatch: a line 1 and b) # Looks like you failed 4 tests of 33. t/db_dependent/Koha/XSLT/Base.t .. Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/33 subtests Test Summary Report ------------------- t/db_dependent/Koha/XSLT/Base.t (Wstat: 1024 Tests: 33 Failed: 4) Failed tests: 10, 12, 14, 16 Non-zero exit status: 4 Files=1, Tests=33, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.44 cusr 0.04 csys = 0.52 CPU) Result: FAIL -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 26000] New: Holiday exceptions are incorrectly cached for an individual branch
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26000 Bug ID: 26000 Summary: Holiday exceptions are incorrectly cached for an individual branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical 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 When updating exception holidays they are cleared from the cache until Koha::Calendar->exception_holidays is called That routine checks the cache, and then generates the holidays for a single branch and sets them in the cache. This is incorrect. single_holidays handles the situation correctly and exception_holidays should do the same. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 26012] New: Date in 'Paid for' information not formatted to Time/DateFormat system preferences
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26012 Bug ID: 26012 Summary: Date in 'Paid for' information not formatted to Time/DateFormat system preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial 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 The information shown in Paid for? on the items tab on detail view shows a date in database format. To test: - Make sure there is a replacement cost in the item - check it out - Mark it lost - Pay the lost item fee - Go to the detail page and look on the items tab for the item - It will show an entry with "Paid for?" label -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 26165] New: Duplicating large saved report leads to error due to length of URI
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26165 Bug ID: 26165 Summary: Duplicating large saved report leads to error due to length of URI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org If the combined character length of a saved report's title, notes and SQL is too long then pressing the 'duplicate' button will lead to an error: "Request-URI Too Long The requested URL's length exceeds the capacity limit for this server." This seems to be happening after the URL reaches 8226 characters. I originally encountered this error when duplicating a long SQL report but I think the easiest way to replicate it is to add a lot of text to the notes field: 1. Create a simple SQL report and add a lot of text into the notes field (the combined URL lenth must be >8225 characters) 2. Save the report 3. Press the duplicate the report from the saved reports page (guided_reports.pl?phase=Use%20save) As a workaround for this bug, users can copy and paste the SQL into a new report and save it that way or write shorter reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 23542] New: SRU import ending issue
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23542 Bug ID: 23542 Summary: SRU import ending issue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When importing records from a SRU server, the diacritics have bad encoding. I reproduce with BNF server so it may be a UNIMARC issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 25882] New: Elasticsearch - Advanced search itemtype limits are being double quoted
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25882 Bug ID: 25882 Summary: Elasticsearch - Advanced search itemtype limits are being double quoted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com To test: 1 - Have koha using ES 2 - Go to advanced search 3 - Limit by a single itemtype that exists 4 - Get some results 5 - Limit by a different itemtype that exists 6 - Get some results 7 - Limit by both itemtypes 8 - Get only the results for the second itemtype 9 - Enable DumpTemplateVarsIntranet and DumpSearchQueryTemplate 10 - Repeat search 11 - View page source and find 'search_query' 12 - See limit looks like itype:("("BK")" OR "("CR")") -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 25336] New: Show checkouts/fines to guarantor is in the wrong section of the patron file
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25336 Bug ID: 25336 Summary: Show checkouts/fines to guarantor is in the wrong section of the patron file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello! I noticed that the Show checkouts to guarantor and Show fines to guarantor flags are in the "Library use" section of the patron file. However, they are set in the "Contact information" section with the setting of the guarantor. This is confusing because if you want to edit the flags, you cannot do it by clicking the "Edit" button next to "Library use", even though the flags are in that section. You have to know that they are set in the "Contact information" section and use that "Edit" button to change them. Caroline -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 25853] New: update_patrons_category.pl has incorrect permissions in repo
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25853 Bug ID: 25853 Summary: update_patrons_category.pl has incorrect permissions in repo Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement 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 The permissions for this are -rw-r--r-- and need to be -rwxr-xr-x -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 26009] New: ElasticSearch homebranch and holdingbranch facets are limited to 10
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26009 Bug ID: 26009 Summary: ElasticSearch homebranch and holdingbranch facets are limited to 10 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com bug 14419 added the 'size' parameter to most facets, but home/holdingbranch were missed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 25683] New: update_patron_categories.pl should recognize no fine history = 0 outstanding fines
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25683 Bug ID: 25683 Summary: update_patron_categories.pl should recognize no fine history = 0 outstanding fines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Bug 17168 introduced update_patron_categories.pl, which can change patron categories based on fine totals. But it doesn't understand that an absence of fines is the same as $0 owed. To replicate: - Have a patron with nothing in accountlines - run update_patron_categories to find patrons with fines under $5 (-fu=5) - Your patron is not found - Give your patron a manual charge of $1 - rerun the cron, your patron is found - pay off your patron's fine, putting their balance at $0 - rerun the cron, your patron is found -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32