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

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

31 Aug '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 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 18947] New: Active Directory LDAP authentication broken
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '20

15 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18947 Bug ID: 18947 Summary: Active Directory LDAP authentication broken Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: helpdesk(a)neci.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Commit 68c365ea8ab536a85d92d3769b0bbaa0e1691116 introduced the following line in Auth_with_ldap.pm: $ldap->{anonymous_bind} = 1 unless $ldapname && $ldappassword; There is no comment in the code or the Git commit log as to why. This change silently overrides the settings in koha-conf.xml and causes a previously functional setup with LDAP authentication against Active Directory to fail unless koha-conf.xml defines values for <user> and <pass>. As user and pass are only used if auth_by_bind and anonymous_bind are both false, their values should not come into play in the other cases. Prior to this change, KOHA would bind against AD with the user supplied credentials, as expected. With the change, KOHA attempts an anonymous bind and then tries to search for the supplied user name. As there was no valid bind in place, AD rejects the attempt. Workaround: enter some value for <user> and <pass> in the ldapserver configuration block. These do not have to be real credentials as KOHA will not attempt to use them now that auth_by_bind has priority again. Note: there is an apparent duplicate attempt to do the same further down, by setting $config{anonymous} to ($ldapname and $ldappassword) ? 0 : 1, although that key is not used anywhere in Auth_by_ldap.pm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 16935] New: launch export_records.pl with deleted_barcodes param fails
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16935 Bug ID: 16935 Summary: launch export_records.pl with deleted_barcodes param fails Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: stephane.delaune(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz when I launch /home/koha/src/misc/export_records.pl with this command line : ~/src/misc/export_records.pl --date=`date +%d/%m/%Y` --deleted_barcodes --filename=/home/koha/test I've got this error message : DBD::mysql::db selectall_arrayref failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 4 [for Statement " ( SELECT DISTINCT barcode FROM deleteditems WHERE deleteditems.biblionumber = ? "] at /home/koha/src/misc/export_records.pl line 189. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 16535] New: Add the date on which the suggestion was managed on Purchase suggestions tab
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16535 Bug ID: 16535 Summary: Add the date on which the suggestion was managed on Purchase suggestions tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be helpful if the date on wich the suggestion was managed was added on Purchase suggestions tab on borrower account. There is just who managed the suggestion. This can be as like date on table in suggestion.pl Regards Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 17697] New: Notes Blacklist only blacklists fields on the OPAC main detail view ( not the OPAC MARC display)
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '20

20 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17697 Bug ID: 17697 Summary: Notes Blacklist only blacklists fields on the OPAC main detail view (not the OPAC MARC display) 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: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To replicate: Add a note to a field in a record (let's say 500) Verify the note shows in both the OPAC Detail and OPAC MARC views Add a blacklist entry to the NotesBlacklist system preference for field 500 Verify the note does not appear on the OPAC detail Verify the note DOES appear on the OPAC MARC detail. Blacklisted notes shouldn't display anywhere in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 20