July 2019 - Koha-bugs - lists.koha-community.org

[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 22594] New: Validate SMS messaging numbers using the E.164 format
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '20

24 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22594 Bug ID: 22594 Summary: Validate SMS messaging numbers using the E.164 format Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Many SMS messaging services reject numbers that do not conform to the E.164 international public telecommunication numbering plan. On the OPAC we already We already tell patrons on the OPAC "Please enter numbers only. (123) 456-7890 would be entered as 1234567890." but we do not enforce this. We should be validating the patron's SMS number on both the staff side and the patron self-service for updating the SMS number. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 21189] New: GDPR: Log all CRUD actions on patron data
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '20

23 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21189 Bug ID: 21189 Summary: GDPR: Log all CRUD actions on patron data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Under the auspices of the recently issued European legislation regarding data privacy (GDPR), the Portuguese government has issued a series of mandatory requirements, as well as general recommendations, for software applications that are implemented under the umbrella of public bodies (RCM 41/2018). Since Koha is mostly used by municipalities and universities in Portugal, some of these mandatory requirements need to be address by Koha implementers in Portugal. We believe that this requirement is also useful for the community at large. Here’s a description of the requirement. *** Requirement description *** Every operation that has to do with creating, updating, deleting and changing permissions of user personal data should be logged. One should know who, when, on who and from the operation has been performed. *** Scope *** Applies in all cases. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 22705] New: Koha tries and fails to connect to local ElasticSearch while configuration points to a remote one
by bugzilla-daemon＠bugs.koha-community.org 20 Aug '20

20 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22705 Bug ID: 22705 Summary: Koha tries and fails to connect to local ElasticSearch while configuration points to a remote one Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com Target Milestone: --- Relevant configuration block in $KOHA_CONF: <elasticsearch> <server>elasticsearch5</server> <index_name>koha_master</index_name> </elasticsearch> % misc/search_tools/rebuild_elastic_search.pl -v Indexing biblios [Cxn] ** [http://127.0.0.1:9200]-[599] Could not connect to '127.0.0.1:9200': Connection refused, called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /home/koha/env/master/src/Koha/SearchEngine/Elasticsearch/Indexer.pm line 382. With vars: {'status_code' => 599,'request' => {'serialize' => 'std','method' => 'HEAD','qs' => {},'path' => '/koha_master_biblios','ignore' => [],'body' => undef}} It looks like it is related to the 'Sniff' CxnPool. When I remove this line https://gitlab.com/koha-community/Koha/blob/7e218b81e6f7e4cf8bb8be3aef547cd… everything works as expected -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[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