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

[Bug 17427] New: Replace CGI::Session with Data::Session
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '24

15 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17427 Bug ID: 17427 Summary: Replace CGI::Session with Data::Session Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CGI::Session is not maintained for ages and seems quite buggy. It would be the culprit of random logout problems. Another issue is the following crazy code in CGI::Session::Driver::DBI sub DESTROY { my $self = shift; unless ( defined $self->{Handle} && $self->{Handle} -> ping ) { $self->set_error(__PACKAGE__ . '::DESTROY(). Database handle has gone away'); return; } unless ( $self->{Handle}->{AutoCommit} ) { $self->{Handle}->commit; } if ( $self->{_disconnect} ) { $self->{Handle}->disconnect; } } If AutoCommit is off, it will commit anyway... It causes some tests to fail (api) if SessionStorage is set to MySQL -- You are receiving this mail because: You are watching all bug changes.

1 131

[Bug 17120] New: Specify number of rows per page in report and initial run
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '24

14 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17120 Bug ID: 17120 Summary: Specify number of rows per page in report and initial run Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think we could enhance reports so that the &limit= parameter could be initially set with the report settings and stored in a field in the table. I also think we could have the drop down available on the parameters page when running the report the first time. If you have a report you know that would run well and could be completely shown with more rows, why not have the option to initially set it differently than the default? The LIMIT command in SQL is okay and works for actually limiting the total number of results, but does weird things if you specify a number larger than 20. The results still span multiple pages, plus it doesn't give you options while running like this would. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 16117] New: Feature request: Log borrower cardnumbers and item barcodes which are not valid
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16117 Bug ID: 16117 Summary: Feature request: Log borrower cardnumbers and item barcodes which are not valid Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On any circ screen where a barcode could be scanned (circ.pl, checkin.pl, checkout and return boxes), we should have the option of logging failed barcode scans, for the purpose of trouble-shooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 17337] New: waitingreserves.pl should trigger transfers as well as holds
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '24

10 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17337 Bug ID: 17337 Summary: waitingreserves.pl should trigger transfers as well as holds Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 17010 addresses triggering the next hold when a hold is cancelled, but transfers should also be triggered. Currently in 3.22.8 nothing happens. It is unclear if 17010 addresses transfers as well. Also, in 3.18 local holds were spotty when holds were triggered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 18936] New: Convert issuingrules fields to circulation_rules
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '24

07 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18936 Bug ID: 18936 Summary: Convert issuingrules fields to circulation_rules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 18930 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18930 [Bug 18930] Move lost item refund rules to circulation_rules table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 226

[Bug 17755] New: Move C4::Members::AttributeTypes to Koha::* namespace
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '24

31 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17755 Bug ID: 17755 Summary: Move C4::Members::AttributeTypes to Koha::* namespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 19372] New: Selecti MARC framework doesn' t work when adding to basket from an external source
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '24

29 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19372 Bug ID: 19372 Summary: Selecti MARC framework doesn't work when adding to basket from an external source Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mglavica(a)ffzg.hr QA Contact: testopia(a)bugs.koha-community.org In acquisitions, when adding items to basket from an external source there is an option to select MARC framework. No matter what we choose, the record is created in default framework. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 19938] New: Refactor C4::Overdues::checkoverdues
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '24

26 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19938 Bug ID: 19938 Summary: Refactor C4::Overdues::checkoverdues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While retesting a bug, I ran a prove -r -v t, which generated a lot of log noise. One such entry was: [Tue Jan 9 03:54:58 2018] starman: Use of uninitialized value $overdues_count in numeric gt (>) at /home/vagrant/kohaclone/opac/opac-main.pl line 76. The $overdues_count was set by a call to checkoverdues. Reading the code I noticed someone actually commented: # returning the count and the results is silly So, this is a refactor of the function and all the calls. It was surprisingly small. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 18207] New: smart-rules.pl should validate that all branches / patron categories / item types are covered by circ rules.
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '24

12 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18207 Bug ID: 18207 Summary: smart-rules.pl should validate that all branches / patron categories / item types are covered by circ rules. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com At present, It's possible to have combinations of branch / category / item type that are not covered by circulation rules. This may cause issues with circulation, holds and fines; we should require that all are covered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18054] New: Refreshing the screen for a confirmed checkout can cause odd results ( item checked out and waiting on hold)
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '24

11 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18054 Bug ID: 18054 Summary: Refreshing the screen for a confirmed checkout can cause odd results (item checked out and waiting on hold) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - Place a hold and confirm it to mark waiting 2 - Checkout that item to another patron and override the hold 3 - Leave that window open 4 - In a new tab checkin the item and confirm the hold as waiting 5 - Refresh the tab from #3 - the item checksout but waiting hold does not revert -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1