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

[Bug 17826] New: Allow extended patron attributes to be sent in arbitrary SIP2 fields
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '19

04 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17826 Bug ID: 17826 Summary: Allow extended patron attributes to be sent in arbitrary SIP2 fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Some libraries need to be able to send additional patron data from the extended patron attributes in made up SIP2 fields for the patron information and patron status responses. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 17768] New: spinelabel.css should be user editable.
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '19

02 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17768 Bug ID: 17768 Summary: spinelabel.css should be user editable. 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The quick-label CSS file is currently part of the Koha distribution, stored at koha-tmpl/intranet-tmpl/prog/en/css/spinelabel.css. This means that users who use package Koha cannot change the styling of the quick slips without resorting to javascript. I would suggest that koha-tmpl/intranet-tmpl/prog/en/css/spinelabel.css be a default, but that we can change this via syspref. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 16887] New: Entering a bad date in 'Koha out on loan' field sets items.onloan to 0000-00-00.
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '19

28 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16887 Bug ID: 16887 Summary: Entering a bad date in 'Koha out on loan' field sets items.onloan to 0000-00-00. 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To re-create 1/ Go to Circulation->Fast Cataloging 2/ Add a biblio record 3/ On Add Items screen, enter a space in 'Koha out on loan' (and enter item type of course). Save the item. 4/ items.onloan will be set to 0000-00-00. ... I'm not certain whether or not this is specific to the fast add framework. Note that this causes upstream issues with search -- any item that has items.onloan set to 0000-00-00 will cause an internal server error on the search results page, with the following error in plack.error.log: Can't locate object method "ymd" via package "dateonly" (perhaps you forgot to load "dateonly"?) at /usr/share/koha/li b/Koha/DateUtils.pm line 223. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17526] New: OPAC lists require a sortfield
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '19

27 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17526 Bug ID: 17526 Summary: OPAC lists require a sortfield Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Using the OPAC, going into the public lists, I click one of them and get DBIx::Class::Storage::DBI::_dbh_execute(): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ASC LIMIT 10) `me` JOIN `biblio` `biblionumber` ON `biblionumber`.`biblionumber' THis is because the sortfield is empty and creates a SQL like GROUP BY ASC LIMIT 10. Missing the group by. In the intranet list, there's a default usage of 'title' that makes it all work. TESTING: 1) just create a public list with no sortfield. - virtualshelves.category = 2 - virtualshelves.sortfield = '' 2) click on the list in the OPAC's public list. Boom! -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 15689] New: Label editor: Fix issues with wrong batch_id parameter
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '19

21 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15689 Bug ID: 15689 Summary: Label editor: Fix issues with wrong batch_id parameter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org There are issues with the label editor, related to the batch_id: 1/ You can select all the items and click on "remove selected" without any warning 2/ You can delete the last item clicking on the "Delete" button ("actions" column) In these 2 cases, the batch_id parameter is passed but is wrong. If you add a new batch on the resulting screen, the batch_id of the deleted batch will be displayed, but a new one will be used. Copied from the comment by Jonathan Druart on Bug 15663 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15663#c7 -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16102] New: Import batch into catalog very slow
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '19

21 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16102 Bug ID: 16102 Summary: Import batch into catalog very slow Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Dear team, The batch import into catalog is very slow when compared to 3.20 version in 3.22.4. I used the same machine for the same number of records in koha 3.22 and it takes almost 8 hours to import the data for 30000 records. In 3.20 it was taking only 30 minutes to 1 hour for this activity to be completed. Using Ubuntu 14.04 and 4GB ram machine for importing the data and this is a fresh installation of ubuntu and koha. Iam not sure if this is a issue with KOHA or issue with my koha settings. I already reported in the koha mailing list for any solution to overcome the issue, but not received any response, hence posting it here. Thanks & regards Suresh Kumar -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17422] New: Holds amount per record produce error
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '19

21 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17422 Bug ID: 17422 Summary: Holds amount per record produce error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 56127 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=56127&action=ed… Screen shot of settings In the circulation and fines rules module, If you set Holds allowed count & Holds per record count for a circulation rule to each 999, koha will produce a template error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 17326] New: KOha not asking if the book is to be renewed when max book limit is reached
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '19

21 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17326 Bug ID: 17326 Summary: KOha not asking if the book is to be renewed when max book limit is reached Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: daltonfury42(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When I try to check out a book that I have already checked out, koha will ask me if I want to renew the book instead. But this does not work if I have already taken the maximum allowed number of books. In this scenario, I get the "Too many checked out." notification, but I think it is logical to allow renewal as it does not increase the number of books that the patron has taken. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 16292] New: Allowtoomanyoverride - Don't allow does not give any message
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '19

21 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16292 Bug ID: 16292 Summary: Allowtoomanyoverride - Don't allow does not give any message Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dear team, When trying to issue more than the limit of items it stops issuing books, but the koha does not show any message/warning - this happens when Allowtoomanyoverride is Don't allow. When Allowtoomanyoverride is allow, it gives me a warning message do you wan't to override or issue. I feel system should tell that the limit reached. If this is not a system issue and I missed some system settings, please help me in setting the system preferences correctly. Iam using koha 3.22.05. Regards Suresh Kumar -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 17105] New: Do not see checkouts in the table of circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17105 Bug ID: 17105 Summary: Do not see checkouts in the table of circulation.pl 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Saw this problem under 3.22 (but could probably have been master too): Circulation page lists a number of checkouts. But clicking Show checkouts does not list them in the table. What happened? This javascript error occurred: Sunday not defined. Comes from includes/calendar.inc. And should be a zero. (As value for the preference CalendarFirstDayOfWeek.) After toggling this preference a few times, I could not reproduce the problem anymore under 3.22 (Plack+memcache). Probably a cache problem somehow. Note that dbrev 3.21.00.015 moved the old value of Sunday to 0. Just leaving this note here some time for future troubleshooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4