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

[Bug 23688] New: System preference uppercasesurnames broken by typo
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '19

13 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23688 Bug ID: 23688 Summary: System preference uppercasesurnames broken by typo Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 In the process of moving this feature from memberentry.pl to Patron.pm, the 's' on uppercasesurnames was dropped, breaking the feature. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 22804] New: OPAC Overdrive JavaScript contains untranslatable strings
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '19

13 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22804 Bug ID: 22804 Summary: OPAC Overdrive JavaScript contains untranslatable strings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- There are several English strings in overdrive.js. These should be moved into the template so they can be translated. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 23679] New: Software error when trying to transfer an unknown barcode
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '19

13 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23679 Bug ID: 23679 Summary: Software error when trying to transfer an unknown barcode 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When trying to transfer an unknown barcode in /cgi-bin/koha/circ/branchtransfers.pl you get the error : Can't call method "itemnumber" on an undefined value at /home/koha/src/C4/Circulation.pm line 319. This comes from C4::Circulation::transferbook which should stop when finding unknown barcode. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 23057] New: If checked_in_ok is set and item is not checked out, alert flag is supressed for *any* reason
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '19

13 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23057 Bug ID: 23057 Summary: If checked_in_ok is set and item is not checked out, alert flag is supressed for *any* reason Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major 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 Target Milestone: --- Because of the way the alert suppression was implemented on bug 15221, the alert flag is suppressed for any and all reasons if checked_in_ok is set and the item is not checked out. This is problematic because the alert flag may be set because the item has been trapped for a hold or another reasons not related to its checked in status. Because of this, SIP AMHs ( automated material handlers iirc ) will send the items to be reshelved instead of sending them to the hold shelf. This code needs to be made aware of the reason the alert flag was triggered or not ( and probably a list of the reasons it was triggered ). That way if the only reason the flag was triggered is due to the item not being checked out, the SIP server can suppress the flag correctly, and allow it to be flagged if there are other reason to raise the alert flag. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 23265] New: Update to DB revision 16.12.00.032 fails: Unknown column 'me.item_level_hold'
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '19

13 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23265 Bug ID: 23265 Summary: Update to DB revision 16.12.00.032 fails: Unknown column 'me.item_level_hold' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org When creating an instance from an older DB and running koha-upgrade-schema, the following error occurs. >[…] >Upgrade to 16.12.00.030 done (Bug 16344 - Add a circ rule to limit the auto renewals given a specific date) >Upgrade to 16.12.00.031 done (Bug 15108: OAI-PMH provider improvements) >DBD::mysql::st execute failed: Unknown column 'me.item_level_hold' in 'field list' [for Statement "SELECT `me`.`reserve_id`, `me`.`borrowernumber`, `me`.`reservedate`, `me`.`biblionumber`, `me`.`branchcode`, `me`.`notificationdate`, `me`.`reminderdate`, `me`.`cancellationdate`, `me`.`reservenotes`, `me`.`priority`, `me`.`found`, `me`.`timestamp`, `me`.`itemnumber`, `me`.`waitingdate`, `me`.`expirationdate`, `me`.`lowestPriority`, `me`.`suspend`, `me`.`suspend_until`, `me`.`itemtype`, `me`.`item_level_hold` FROM `reserves` `me` WHERE ( ( `found` = ? AND `priority` = ? ) )" with ParamValues: 0='W', 1=0] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836. >DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.item_level_hold' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 209 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 19740] New: Self checks calculating wrong due dates / configuration changes go unnoticed
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '19

13 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19740 Bug ID: 19740 Summary: Self checks calculating wrong due dates / configuration changes go unnoticed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When using a self check via SIP2 a calendar change will take no effect resulting in due dates being calculated differently for self checks than on the circulation desk. The calculation will remain false until the SIP server is restarted. This also seems to apply to system preference changes, which happen less often. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19770] New: Add cardnumber to holds awaiting pickup screen and add classes to borrower info
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '19

12 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19770 Bug ID: 19770 Summary: Add cardnumber to holds awaiting pickup screen and add classes to borrower info 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries use a combination of borrowers surname and cardnumber on hold slips, this seems to be a fairly common occurence. To facilitate this it would be nice to have the cardnumber available on the waiting holds report. Additionally it would be nice to have classes add to the borrower information so that they can be accessed via javascript for constructing the special code used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 23600] New: url broken in advanced search
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '19

11 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23600 Bug ID: 23600 Summary: url broken in advanced search Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: aovalle(a)biteca.com QA Contact: testopia(a)bugs.koha-community.org Hello, When performing an advanced search I have several libraries defined in a group. When performing the search it works fine, but when browsing the results it throws URL error (Request-URI Too LongThe requested URL's length exceeds the capacity limit for this server.) How could this be resolved from Koha or from the server? Regards! Andrés -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20407] New: Hide some fields from unauthoriezd users
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '19

08 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20407 Bug ID: 20407 Summary: Hide some fields from unauthoriezd users Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com The main goal here is to be able to make some fields/properties/columns "non public" to unauthorized people ( permission => catalogue ) by setting a "x-public" key to false in Swagger definitions files. Patch is coming... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 23630] New: Elasticsearch indexing is removing field 999
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '19

08 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23630 Bug ID: 23630 Summary: Elasticsearch indexing is removing field 999 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Elasticsearch indexing uses 999$c to store record id by deleting the all field first ! So you can not store anything in field 999, even in UNIMARC and even in authorities records. Looks like it is quick fix code added to start Elasticsearch use. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20