September 2016 - Koha-bugs - lists.koha-community.org

[Bug 17218] New: New list add attempt while logged in as dbadmin should be prevented pre-emptively
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '18

05 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17218 Bug ID: 17218 Summary: New list add attempt while logged in as dbadmin should be prevented pre-emptively Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: indradg(a)l2c2.co.in QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Right now it allows the Koha db admin login to attempt adding a new list. Only while trying to save it does it inform that it is not possible to do so. This is should be made pre-emptive right after the "+ New list" option is clicked. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 15705] New: Notify the user on auto renewing
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '18

02 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15705 Bug ID: 15705 Summary: Notify the user on auto renewing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Customisable notices must be triggered to tell patrons if the items were renewed and when failed to renew. -- You are receiving this mail because: You are watching all bug changes.

1 87

[Bug 17378] New: Add ability to specify maximum number of items per record
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17378 Bug ID: 17378 Summary: Add ability to specify maximum number of items per record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries want to be able to specify a hard limit on the number of items a record can have. It would be nice to have this set per record type, but since most libraries use item level itemtypes, that would make it confusing and non-intuitive. The simplest and most straight forward approach would just be to have a system preference. Koha should then just report that it failed to create an item if the librarian has hit the upper limit specified in the system preference. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 15707] New: Add ability to define hierarchical groups of libraries
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '18

26 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15707 Bug ID: 15707 Summary: Add ability to define hierarchical groups of libraries Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha needs the ability to create hierarchical groups of libraries. This ability could be used in many areas of Koha to make Koha much more flexible and consortium friendly. -- You are receiving this mail because: You are watching all bug changes.

1 276

[Bug 16858] New: import_borrowers.pl does not load because of mysql 5.7
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '18

25 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16858 Bug ID: 16858 Summary: import_borrowers.pl does not load because of mysql 5.7 Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: npm(a)zefanjas.de QA Contact: testopia(a)bugs.koha-community.org The Import Patrons tool does not load on MySQL 5.7 because of the default sql_mode: only_full_group_by. This is the error I got: http://paste.koha-community.org/16 Can't use an undefined value as an ARRAY reference at /usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm line 2083 If I change the sql_mode to a mysql 5.6 behavior the import page loads fine. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 16575] New: Irregular behaviour using window.print() followed by window.location.href=
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16575 Bug ID: 16575 Summary: Irregular behaviour using window.print() followed by window.location.href= Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As we noticed in bug 11014, different browsers handle "window.print()" differently. In the case of window.print() followed by window.location.href=, I've found in IE 11 on Windows 8.1 that the browser changes the window location before the system print dialogue even opens. If I try to mitigate that using the timer from bug 11014, it works in IE and Chrome, but it breaks in Firefox. If I try to use the onafterprint in IE and Firefox, it works in IE but it breaks in Firefox. I started wondering if we even need to be using this window.print() followed by window.location.href= and it occurred to me that we really don't. We should just be using print.css. Patch to follow soon... -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 16653] New: reports/cat_issues_top.pl does not export "Count of checkouts" column as CSV
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16653 Bug ID: 16653 Summary: reports/cat_issues_top.pl does not export "Count of checkouts" column as CSV 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org reports/cat_issues_top.pl does not export "Count of checkouts" column as CSV To replicate: 1/ Make sure that test instance has circulation in a given date range 2/ Go to Home › Reports › Most-circulated items 3/ Select a date range 4/ Select 'To screen into the browser' radio button, click submit. 5/ Note that Columns 'Rank/Biblioitemnumbers', 'Global' and 'Count of checkouts' appear in screen output. 6/ Click the browser's back button 7/ Change output to 'To a file', click submit. 8/ Note that the columns "100/", "Global" and "Total" are exported to the CSV file. "100/" contains the rank, "Global" is still global, and the "Total" column is empty. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 15971] New: Allow use of all biblio and biblioitems fields in serial claim letters
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15971 Bug ID: 15971 Summary: Allow use of all biblio and biblioitems fields in serial claim letters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When creating a serial claim letter only title, author and serial are offered as fields in the notice editor. It should be possible to print all fields from the biblio and biblioitems tables including the ISSN in the notices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 16833] New: printoverduefaq is out of date
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '18

20 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16833 Bug ID: 16833 Summary: printoverduefaq is out of date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org http://manual.koha-community.org/3.22/en/circfaq.html#printoverduefaq contains "The print and email overdues use the same notice file. The print notices for holds are different -- there's a separate HOLD_PRINT notice file and the system uses it if there's no email address. Then a nightly cron job runs to gather those up from the message queue and put them in an HTML file in the notice directory, as above. The cron entry is gather_print_notices.pl /tmp/noticedir" This is out of date in the following respects: 1) HOLD_PRINT no longer exists -- this is handled by the print message under the HOLD letter. 2) gather_print_notices.pl now supports printing overdue notices. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17195] New: Split logging of item modifications from CataloguingLog into separate system preferences
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '18

18 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17195 Bug ID: 17195 Summary: Split logging of item modifications from CataloguingLog into separate system preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Because logging modifications to items has so much overhead, it is not recommended that CataloguingLog be enabled. If we split off modifications to items into a separate system preference CataloguingLogItems, then libraries can at least log modifications to records without taking a large processing hit. -- You are receiving this mail because: You are watching all bug changes.

1 6