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

[Bug 24653] New: Failing tests in 19.05.x
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24653 Bug ID: 24653 Summary: Failing tests in 19.05.x Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: lucas(a)bywatersolutions.com tests are failing in 19.05: -t/db_dependent/Koha/Charges/Fees.t -t/db_dependent/SIP/Transaction.t Something is not accounted for when there is no ALL/ALL circ rule. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 25018] New: Jenkins is not running the test with $ENV{_} eq 'prove'
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25018 Bug ID: 25018 Summary: Jenkins is not running the test with $ENV{_} eq 'prove' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org In some tests we want to know if we are in a testing environment. When run the usual way, our trick works, the perl interpreter matches 'prove': $ENV{_} eq 'prove' In other situations, we have the KOHA_NO_TABLE_LOCKS environment variables, for the SendCirculationAlert race conditions (see bug 15854 and bug 18364). For unknown reasons, Jenkins runs the tests with /usr/bin/perl. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20674] New: One off report
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20674 Bug ID: 20674 Summary: One off report Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: tlamannajr(a)chplnj.org QA Contact: testopia(a)bugs.koha-community.org Right now the only way to create and run a report is to save it to a list, but there are plenty of times I just need a one-off report and it's a bit of a pain to have to create and name a report then delete in when I'm done. This clutters up the reports list a lot. Not a massive problem, but I'm hoping we can streamline one off reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24755] New: chance to define expiration hour for in-site loans
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24755 Bug ID: 24755 Summary: chance to define expiration hour for in-site loans Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com on reserves.expirationdate's mysql format is date, however I think it could be datetime I have identified that many koha's librries are cataloguing pc's, study rooms as in-ite loans, the students may hold this kind of material, but the hold expiration date is suitable for books, but not suitable at all for in-site loans. It should be great if we could define expiration days for home-loans and expiration hour for in-site loans It should be also great if we could define close hours to do not assign a date_due beyond the close date -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24505] New: Print overdue notice with html gives message: "The following terms were not matched and replaced"
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24505 Bug ID: 24505 Summary: Print overdue notice with html gives message: "The following terms were not matched and replaced" Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: somesecretemail(a)mailinator.com QA Contact: testopia(a)bugs.koha-community.org In overdue notice for the option "print" we use a template containing html. After running the overdue_notices cron job: > sudo perl /usr/share/koha/bin/cronjobs/overdue_notices.pl -t -v -html /tmp a message is presented by the system "The following terms were not matched and replaced: html, div, etc...". It seems like the system confuses the "<< >>" enclosed text with the html components. Nothing from the template is added to the generated html file. This bug is exactly the same as this bug fixed in 2013: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10720 You can also find it well documented in the commit here: https://gitlab.deichman.no/digibib/Koha/commit/394be84dcd65a4569d0467bc12b9… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24504] New: branchtransfers.pl - Entering checked out item cause Internal Server Error
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24504 Bug ID: 24504 Summary: branchtransfers.pl - Entering checked out item cause Internal Server Error Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fraktik(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Interestingly enough this is happening only first time (item get checked in and then this "Internal Server Error" blank page appears). If I get back to /cgi-bin/koha/circ/branchtransfers.pl and put the same barcode second time, the transfer is processed without any further error. Possible relation to the Bug 3536 - Checked In item requiring transfer does not consistently trigger transfer prompt (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3536) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 21269] New: add unique id to issuingrules, include that id in issues table
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21269 Bug ID: 21269 Summary: add unique id to issuingrules, include that id in issues table Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Perhaps an overly-large ask, but would be a huge boon for troubleshooting circulation behavior. If issuingrules contained a column for issuingrule_id, that value could be included in the issues table, allowing easy identification of which issuing rule applied to a given checkout. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 21253] New: Clarify calendar used by book drop mode
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21253 Bug ID: 21253 Summary: Clarify calendar used by book drop mode Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using book drop mode in returns.pl, the checkin date is set to the last date the library was open. However, this gets confusing when multiple branches within the same system have different calendars. Book drop mode selects a date based on the calendar of the library whose circ rules governed the checkout (the library indicated by the CircControl and HomeOrHolding sysprefs). It does not consult the calendar of the library at which the checkin is taking place. This is not a particularly transparent behavior and is not explained in the manual. I'd like to see an explanation added to https://koha-community.org/manual/17.11/html/05_circulation.html#check-in-r…. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21197] New: Search index list doesn't show other-control-number
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21197 Bug ID: 21197 Summary: Search index list doesn't show other-control-number Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The search index list at https://koha-community.org/manual/17.11/html/13_searching.html#koha-search-… doesn't mention the indexing of the 035 as other-control-number established in Bug 6499 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6499) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 21147] New: When suspension ends today, the datepicker shows tomorrow's date
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21147 Bug ID: 21147 Summary: When suspension ends today, the datepicker shows tomorrow's date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 When a suspension ends on today's date, the datepicker in the holds table will show tomorrow's date, as today can't be picked. That might hide a problem with the cronjob not running and it would be nice, if the actual date could be displayed instead. Marking as minor as with correctly running cronjobs you might not encounter this ever. -- You are receiving this mail because: You are watching all bug changes.

1 1