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

[Bug 17005] New: REST API: add routes to list checkouts history
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '21

25 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17005 Bug ID: 17005 Summary: REST API: add routes to list checkouts history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org Add API to list checkouts history for a user. This is very useful for use with VuFind. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 92

[Bug 17454] New: Omnibus POD Cleanup
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '21

21 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17454 Bug ID: 17454 Summary: Omnibus POD Cleanup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I would like to see better developer documentation in Koha; this ranges in scope from cleaning up POD errors (easy), adding POD to modules and scripts where it's missing (moderate), to documenting the weird and wonderful corners of the holds queue or Search.pm (hard). -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16149] New: Generate and send custom notices based on report output
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '21

17 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16149 Bug ID: 16149 Summary: Generate and send custom notices based on report output Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/custom-notic es-based-report-output/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Work to be done: Write a cron script that will a) Accept parameters for 1) a report id 2) a notice code 3) a notice module 4a) a branchcode 4b) or database column from which to select the branchcode 5) a column from which to select the email address to send to ( if not set, Koha will use the first available email address for the patron ) 6a) A "from" email address 6b) A column from which to select the "from" email address b) The script will run the report and for each row of results will generate a notice and queue it for sending. All and only the columns from the report will be available to be used in the notice text. Looking for sponsors: http://devs.bywatersolutions.com/projects/custom-notices-based-report-outpu… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 15933] New: Regarding publishercode
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '21

12 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15933 Bug ID: 15933 Summary: Regarding publishercode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, As in the serials module there is an option to search for an existing vendor and add the vendor code while creating a new one, I could not find an option to search for a publishercode. If this is available the data entry part of the publishercode will be very uniform throughout the cataloging entries. I could not find this option any where hence posting it here. Regards Suresh Kumar -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 17801] New: 'Top Most-circulated items' gives wrong results when filtering by checkout date
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '21

08 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17801 Bug ID: 17801 Summary: 'Top Most-circulated items' gives wrong results when filtering by checkout date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We had a library reporting that records show up on this report that haven't been checked out within the selected date range of checkout dates. After looking at the script I think this is because it checks the timestamp column instead of the issuedate of old_issues. In old_issues the timestamp is the date of return, so that's not right and explains the results the library reported. Side note: the report does also not seem to count current checkouts as it avoids the issues table? -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 17819] New: Performance 16.11 - Omnibus
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '21

05 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17819 Bug ID: 17819 Summary: Performance 16.11 - Omnibus Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW 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 https://wiki.koha-community.org/wiki/Benchmark_for_16.11 -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 17320] New: MySQL 5.7 doesn't work well with SQL using '0000-00-00'
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '20

18 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17320 Bug ID: 17320 Summary: MySQL 5.7 doesn't work well with SQL using '0000-00-00' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) 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 Several SQL statements in updatedatabase.pl have '0000-00-00'. A simple substitution to 0 will prevent a default MySQL 5.7 on Ubuntu from barfing. This patch will touch as far back as 3.0.6, but given the magnitude of other errors while upgrading, finding no 0000-00-00 barfs after the patch up to 3.9 and then finding no 0000-00-00 barfs from 3.14.x upwards seems sufficient to check. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 16067] New: Koha::Cache, fastmmap caching system is broken
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16067 Bug ID: 16067 Summary: Koha::Cache, fastmmap caching system is broken 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: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org After Bug 11998, fastmmap caching system implementation in Koha::Cache ceased to work properly. If fastmmap is enabled (= environment variable CACHING_SYSTEM is set to 'fastmmap'), any CGI script call causes the following error: Use of uninitialized value $db_name in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. Use of uninitialized value $db_host in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. DBI connect('database=;host=;port=','',...) failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1249 DBIx::Class::Storage::DBI::dbh(): DBI Connection failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1253. at /home/koha/devkohaclone/Koha/Database.pm line 90 To reproduce on command line: 0) ensure that you have fastmmap perl module installed (libcache-fastmmap-perl in debian) 1) export CACHING_SYSTEM=fastmmap 2) export GATEWAY_INTERFACE=1 3) try to run this simple script: #!/usr/bin/perl use Modern::Perl; use C4::Biblio; GetMarcStructure(); -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 17374] New: Make use of fields from syspref ' DefaultPatronSearchFields' in patron search fields dropdown
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '20

14 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17374 Bug ID: 17374 Summary: Make use of fields from syspref 'DefaultPatronSearchFields' in patron search fields dropdown Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 14874 introduced syspref 'DefaultPatronSearchFields' to define what fields should be used in default patron search. It would be nice see the fields in the search fields drop down as well. At the moment the are hard coded to: Surname,Email,Borrower number,Username,Phone number,Street Address,Date of birth,Sort field 1,Sort field 2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 77

[Bug 17268] New: Advanced cataloging editor - rancor - macros are lost when browser storage cleared
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '20

14 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17268 Bug ID: 17268 Summary: Advanced cataloging editor - rancor - macros are lost when browser storage cleared Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In development macros were stored in the browser to allow different users to have their own. Unfortunately this means macros are lost when browser storage is cleared. Should have a more robust method for retaining these. -- You are receiving this mail because: You are watching all bug changes.

1 129