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

[Bug 18655] New: Unimarc field 210c fails on importing fields with a simple quote
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18655 Bug ID: 18655 Summary: Unimarc field 210c fails on importing fields with a simple quote 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you search for an editor with a simple quote in the name, the escaping fails and nothing happens. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 17561] New: ReserveSlip needs itemnumber for item level holds on same biblio
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17561 Bug ID: 17561 Summary: ReserveSlip needs itemnumber for item level holds on same biblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: benjamin.rokseth(a)kul.oslo.kommune.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With bug 14695 patrons can now place multiple holds on same biblio. The ReserveSlip function used by hold-transfer-slip.pl though doesn't take itemnumber as param, so any item returned belonging to the same patron's reservation on the same biblio will trigger the same slip, which is the first match. It itemnumber (or barcode) is included in request to ReserveSlip, the correct hold slip should be returned. GetReserveId used in ReserveSlip takes itemnumber anyways, so it makes sense to include it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 19068] New: OPAC purchase suggestion doesn' t allow users to enter quantity of items
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19068 Bug ID: 19068 Summary: OPAC purchase suggestion doesn't allow users to enter quantity of items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: J.P.Knight(a)lboro.ac.uk QA Contact: testopia(a)bugs.koha-community.org Created attachment 65767 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65767&action=ed… One line addition to opac-suggestions.tt to allow quantities to be entered Our librarians commented that the Koha purchase suggestions form doesn't allow the quantity of items to be suggested. In an academic library, sometimes the academics will make suggestions for reading material and have an idea how popular it may be, even for modules/courses that aren't yet running so don't (officially) have any students allocated to them. This enhancement just exposes the quantity field to the OPAC suggestions form to permit the end user to enter this if they wish. The librarians can of course override this quantity when they process the suggestion. Test Plan (assuming using kohadevbox VM): 1) apply patch and turn on purchase suggestions 2) Go to http://localhost:8080/cgi-bin/koha/opac-suggestions.pl?op=add and notice that there is now a quantity field available. 3) Make a purchasing suggestion using this form, including a quantity. 4) Log in as a member of library staff and go to Home › Acquisitions › Suggestions 5) Confirm that the previously entered suggestion is there, and that the correct quantity appears in the "Acquisition information" section. 6) Edit the purchasing suggestion, change the quantity, save it and check that the new quantity appears in the suggestion. I've popped an ID attribute of "opac-suggestion-quantity" to the surrounding <li> so that CSS can easily make this optional field disappear (as suggested by cait on IRC). -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 18570] New: Password recovery e-mail only sent after message queue is processed
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18570 Bug ID: 18570 Summary: Password recovery e-mail only sent after message queue is processed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: jens.weber(a)phsh.ch QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org The password recovery process triggers an e-mail to the patron with a link to reset his or her password. This e-mail is put into the message queue like any other notification (e.g. filled HOLD) and hence only sent the next time process_message_queue.pl is triggered with the time setting in cron.d (the default here being every 15 minutes!). This behavior is not what a user would expect from such a function (especially not with the wording from opac-password-recovery.tt: 'An email **has been sent**'). Accordingly -- even though this is not a malfunction -- I flagged this a bug and not an enhancement, as from the point of view of the patron it must seem to be a bug/problem if the e-mail does not arrive in a normal time span. -- You are receiving this mail because: You are watching all bug changes.

1 55

[Bug 18821] New: GetPatronLastActivity is a performance killer
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18821 Bug ID: 18821 Summary: GetPatronLastActivity is a performance killer 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 Enabling GetPatronLastActivity can cause an extreme performance hit, especially on the staff side during checkin and checkout. It makes more sense to only update the last activity timestamp on the first access of a given session. This will greatly improve performance while retaining the same basic information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 18799] New: XSLTresultsdisplay hides the icons
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18799 Bug ID: 18799 Summary: XSLTresultsdisplay hides the icons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org to reproduce : 'xsltresultsdisplay' => default In intranet search, icons are not displayed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 18474] New: Placing multiple holds from results breaks when patron is searched for
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18474 Bug ID: 18474 Summary: Placing multiple holds from results breaks when patron is searched for Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests 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 To recreate: 1 - Search in staff client 2 - Check multiple titles 3 - Click 'Place hold' button in toolbar 4 - Type 'a' into Patron: search (or any search the returns multiple patrons) 5 - Select a patron from the results 6 - You are taken to screen to place a single hold 7 - Repeat 1-3 8 - Enter a cardnumber or type and select a patron directly 9 - You can place the multiple holds as expected. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 17869] New: Don' t show pick-up library for holds in OPAC account when there is only one branch
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17869 Bug ID: 17869 Summary: Don't show pick-up library for holds in OPAC account when there is only one branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When there is only one branch in an installation, it makes no sense to show a pick-up library column in the holds list in the patron account in OPAC. We should remove it from display, as we do in other spots. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 18725] New: Process_message_queue sends duplicate emails if message_queue is not writable.
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18725 Bug ID: 18725 Summary: Process_message_queue sends duplicate emails if message_queue is not writable. 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Last week, we had a database server whose disk filled, causing database writes to fail. This meant that messages in message_queue marked 'pending' were not marked as 'sent' when they were added to the postfix mail queue; messages were sent every 15 minutes (as specified in the cron job) until the disk space issues were cleared. I would suggest adding a token write to the start of process_message_queue.pl as a 'canary in the coal mine'. If the database write fails, process_message_queue should stop, because it's not safe to proceed sending emails that may not be marked 'sent'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 19338] New: Dates sorting incorrectly in opac-account.tt
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '18

23 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19338 Bug ID: 19338 Summary: Dates sorting incorrectly in opac-account.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: liz(a)catalyst.net.nz Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Looks like we never put the title-string spec in on this page to make the dates sort correctly. We should fix that, so that the dates are right in all formats. -- You are receiving this mail because: You are watching all bug changes.

1 17