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

[Bug 22446] New: Koha/Patron/Categories.t is failing on March 1st (2019 only?)
by bugzilla-daemon＠bugs.koha-community.org 29 Feb '24

29 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22446 Bug ID: 22446 Summary: Koha/Patron/Categories.t is failing on March 1st (2019 only?) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com Target Milestone: --- koha_1 | # Failed test 'With enrolmentperiod defined and a date given in parameter, ->get_expiry_date should take this date + enrolmentperiod' koha_1 | # at t/db_dependent/Koha/Patron/Categories.t line 80. koha_1 | # got: '-1' koha_1 | # expected: '0' koha_1 | # Looks like you failed 1 test of 5. koha_1 | koha_1 | # Failed test 'get_expiry_date' koha_1 | # at t/db_dependent/Koha/Patron/Categories.t line 86. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 22340] New: Elasticsearch - sorting fields should have a fallback mechanism
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22340 Bug ID: 22340 Summary: Elasticsearch - sorting fields should have a fallback mechanism 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 Target Milestone: --- As an example 264 and 260 should be sortable for publisher Some records will have one, some will have both, it should eb configurable which to use and that we should not leave the sort field empty if one field is missing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 17975] New: TT syntax for notices - Prove that HOLD_SLIP is compatible
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '24

16 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17975 Bug ID: 17975 Summary: TT syntax for notices - Prove that HOLD_SLIP is compatible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 21858] New: RFC: Notices and slips documentation
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '24

15 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21858 Bug ID: 21858 Summary: RFC: Notices and slips documentation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha doesn't currently have a single point of truth for documentation of notices and slips, which has lead to a proliferation of markup syntaxes, especially in regard to repeating detail, e.g. DUEDGST/PREDUEDGST: <<items.content>> ODUE* <<items.content>> or <item> </item> CHECKOUT/CHECKIN/RENEWAL ---- Detail here ---- These have been documented in https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_M… , but this has gotten out of date as new notices get added in each version of Koha. Work to be done: Add Koha/Notices.pod which will document the following for each notice in the Letter table: * Letter Code * Source file where the notice is populated * Logic that triggers the notice * Detail syntax (if any) * Available data (tables and substitutions) * Message transport restrictions The output from this pod should be used as the basis for the Koha user documentation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 17967] New: TT syntax for notices - Prove that ODUE is compatible
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '24

15 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17967 Bug ID: 17967 Summary: TT syntax for notices - Prove that ODUE is compatible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 -- You are receiving this mail because: You are watching all bug changes.

1 18

[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 22603] New: Move boilerplate into Koha::Cron class
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22603 Bug ID: 22603 Summary: Move boilerplate into Koha::Cron class Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- There's a bunch of patterns in the koha cron scripts.. we should move some of the boilerplate into the new Koha::Cron base class and make our cron scripts DRYer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 22577] New: Cronjobs (and other scripts) should be attributed to a 'real' user
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22577 Bug ID: 22577 Summary: Cronjobs (and other scripts) should be attributed to a 'real' user 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently the userenv for cronjobs is set to '0' for the userid. This user does not exist and breaks/prevents foreign key constraints from working as expected. We should really add a hard coded default user to identify such actions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 22441] New: SCO sound alerts need a selenium test
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22441 Bug ID: 22441 Summary: SCO sound alerts need a selenium test Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I've vague recollection of fixes around this area often introducing regressions.. could we perhaps work out a selenium test for this? Relates to my comment in bug 22378 -- You are receiving this mail because: You are watching all bug changes.

1 5