Koha-bugs

Download

koha-bugs@lists.koha-community.org

October 2024

1 participants
4652 discussions

[Bug 38047] New: Convert DataTable in boraccount.pl to use API
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38047 Bug ID: 38047 Summary: Convert DataTable in boraccount.pl to use API Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Loading /cgi-bin/koha/members/boraccount.pl can take a long time to load. This is particularly problematic as many debits and credits will redirect to /cgi-bin/koha/members/boraccount.pl and the slowness of the loading can cause staff to be confused or panic and start reloading the page, clicking payment buttons again, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 38046] New: AddRenewal dies due to daylight savings time issue and some other unknown factor
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38046 Bug ID: 38046 Summary: AddRenewal dies due to daylight savings time issue and some other unknown factor Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We noticed recently if AddRenewal is run during automatic_renewals.pl between 2am and 3am, it will reliably crash for 1 Koha instance: {UNKNOWN}: Invalid local time for date in time zone: Australia/Sydney at /usr/share/koha/lib/C4/Circulation.pm line 3405 There is no valid Australia/Sydney time between October 6th 2:00am 2024 and October 6th 2:59am 2024, so I suspect that at some point during the AddRenewal process, there is an attempt to generate a DateTime object in the Australia/Sydney timezone within that datetime range. -- We're going to work around it by just making sure the automatic_renewals.pl cronjob doesn't run between 2am and 3am, but it's not a real solution... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

Jump to page: