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

[Bug 16466] New: Patron discharge page should show pending requests
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '20

02 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16466 Bug ID: 16466 Summary: Patron discharge page should show pending requests Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/members/discharge.pl OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a patron has requested a discharge via the OPAC, that request does not show up on their discharge page in the staff client. I think it should. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 19967] New: Search patrons with non-Latin languages is brocken if DefaultPatronSearchFields includes dateofbirth
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '20

02 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19967 Bug ID: 19967 Summary: Search patrons with non-Latin languages is brocken if DefaultPatronSearchFields includes dateofbirth Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: ulrich.kleiber(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In this particular case you get the mysql error message: Illegal mix of collations for operation 'like' You can prevent this error by removing dateofbirth from DefaultPatronSearchFields or by the following patch: diff --git a/C4/Utils/DataTables/Members.pm b/C4/Utils/DataTables/Members.pm index 2446703..ba32a12 100644 --- a/C4/Utils/DataTables/Members.pm +++ b/C4/Utils/DataTables/Members.pm @@ -117,7 +117,12 @@ sub search { my @where_strs_or; for my $searchfield ( split /,/, $searchfields->{$searchfieldstype} ) { - push @where_strs_or, "borrowers." . $dbh->quote_identifier($searchfield) . " LIKE ?"; + if ( $searchfield eq 'dateofbirth' ) { + push @where_strs_or, "DATE_FORMAT(borrowers." . $dbh->quote_identifier($searchfield) . ", '%Y-%m-%d') LIKE ?"; + } else { + push @where_strs_or, "borrowers." . $dbh->quote_identifier($searchfield) . " LIKE ?"; + } + push @where_args, $term; } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 15985] New: Include transacting library in fines
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '20

01 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15985 Bug ID: 15985 Summary: Include transacting library in fines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Work to be done: 1) Add column issue_id to accountlines table 2) Modify fines generation to set issue_id for fine upon generation 3) Modify updatedatabase.pl to insert issue_id in accountlines for currently accruing fines 4) On the pay fines page, use this data to display the library where the item was checked out from -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 86

[Bug 18251] New: SCO alerts - need a trigger for successful checkouts
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '20

26 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18251 Bug ID: 18251 Summary: SCO alerts - need a trigger for successful checkouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Failed checkouts on the sco can be triggered by presence of alert, however, we have no feedback for a successful checkout. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 19287] New: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287 Bug ID: 19287 Summary: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The BULAC (http://www.bulac.fr/) would like to mark items not found on shelves after patrons’ holds as ‘Lost’ directly from the “Circulation > Holds awaiting pickup” list. We could have a new button on the “Action” columns of the 2 tabs, producing 3 automatic actions : - cancel the hold - notify the patron if the hold was supposed to be available (the notice should be set on the “Tools > Notices and Slips” menu) - set the field “items.notforloan” or “items.itemlost” (define in a system preference) from “0” to a value from the same ‘authorized values list’ and set in another system preference As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 108

[Bug 17098] New: Validation problems with form field type "number" ( decimal separator)
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '20

19 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17098 Bug ID: 17098 Summary: Validation problems with form field type "number" (decimal separator) 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org With Koha language set to de-DE, it is not possible to enter numeric values with decimal separator point like 5.00 if the input field is of type "numeric". Validation requires comma (,) Independently on Koha language and CurrencyFormat settings, you get an error message (in German): "Bitte geben Sie eine Nummer ein." To verify: - Install language de-DE (alternatively use Firebug to manipulate page HTML to <html lang="de-DE"> or to set lang="de-DE directly in form field). - Go to /cgi-bin/koha/members/maninvoice.pl?borrowernumber=XXX ("Manuelle Gebühr") - In field "Betrag:", enter 5.00 Result: Field border turns to red, field shows tooltip "Bitte geben Sie eine Nummer ein." Expected result: Point as decimal separator is accepted. Same behaviour with it-IT, fr-FR, nl-NL However if you set language to en or de-CH, both comma and point are accepted. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 20576] New: t/db_dependent/Koha_SearchEngine_Elasticsearch_Search.t fails if Elasticsearch is configured but not running
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '20

19 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20576 Bug ID: 20576 Summary: t/db_dependent/Koha_SearchEngine_Elasticsearch_Search. t fails if Elasticsearch is configured but not running Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org Similar to bug 18738, except with Koha_SearchEngine_Elasticsearch_Search.t -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 19046] New: IntranetCatalogSearchPulldown doesn' t retain last selection
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '20

19 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19046 Bug ID: 19046 Summary: IntranetCatalogSearchPulldown doesn't retain last selection Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client 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 On the OPAC if you have the pulldown enabled and perform a 'Title' search, this selection carries over. On the staff client the default is always 'Keyword' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 15770] New: Number::Format issues with large numbers
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '20

18 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15770 Bug ID: 15770 Summary: Number::Format issues with large numbers 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: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In my database I have some large numbers in some database columns (categories.enrolmentfee for instance), because of TestBuilder I think. In that case, this cause admin/categories.pl to die with the following error message: Template process failed: undef error - round() overflow. Try smaller precision or use Math::BigFloat at /home/koha/src/Koha/Number/Price.pm line 44 This shouldn't happen in real life, but as Koha allows to enter such big numbers, this should probably be fixed. Steps to reproduce: 1. Go to Admin » Categories 2. Click on "New category" button 3. Fill in the required field and set enrolment fee to a big number like 123456789012345 (15 digits seem to be the minimum to reproduce the bug) 4. Save 5. Boom! -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 20154] New: stay in the open tab when going into edit mode
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '20

17 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20154 Bug ID: 20154 Summary: stay in the open tab when going into edit mode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, When we consult an authority in the authorities module, it would be nice too stay in the tab that are actually open when we switch to edit mode. Currently when you consult an authority notice and you open a tab (for exemple the tab 2) if you switch to the edit mode we will automaticaly arrive at the record in edit mode but with tab "0" open. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11