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

[Bug 18088] New: Software error additem.pl Can' t call method subfield error. Can't add items.
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18088 Bug ID: 18088 Summary: Software error additem.pl Can't call method subfield error. Can't add items. Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: hard359(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl While adding items it sais: Can't call method "subfield" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 91. Line 88 to 103 sub _increment_barcode { my ($record, $frameworkcode) = @_; my ($tagfield,$tagsubfield) = &GetMarcFromKohaField("items.barcode",$frameworkcode); unless ($record->field($tagfield)->subfield($tagsubfield)) { my $sth_barcode = $dbh->prepare("select max(abs(barcode)) from items"); $sth_barcode->execute; my ($newbarcode) = $sth_barcode->fetchrow; $newbarcode++; # OK, we have the new barcode, now create the entry in MARC record my $fieldItem = $record->field($tagfield); $record->delete_field($fieldItem); $fieldItem->add_subfields($tagsubfield => $newbarcode); $record->insert_fields_ordered($fieldItem); } return $record; } -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 18199] New: Proxy support for UsageStats
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18199 Bug ID: 18199 Summary: Proxy support for UsageStats Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: tkalix(a)bredex.de QA Contact: testopia(a)bugs.koha-community.org Hello, I have had problems uploading the usage stats. The monthly script failed with some error message. The solution was to edit the file UsageStats.pm and insert my http proxy after line 347. And now it is working fine. It would be good if the utility uses the proxy support I configured in Koha, so one does not need to use the workaround I did. Thanks, Torsten. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 19923] New: conceptual searching in koha
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19923 Bug ID: 19923 Summary: conceptual searching in koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: reza0770(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Dear Friends, Why can’t we used the references systems (conceptual searching) based on our authority files in the OPAC of KOHA. What is the matter exactly and what should we do for using its benefits. Mainly, we have some authority files including subjective authority data, name authority data, etc., But our end users can’t do conceptual searches in the OPAC. For instance, where a user searches a non-preferred term of a name or a subject, the KOHA searching system (in the OPAC environment) cannot recognizes the relationship between the searched terms to the related preferred term in an authority file. While KOHA supports such kind of search in the authority data module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19948] New: Rest API documentation is out of date in Koha manual
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19948 Bug ID: 19948 Summary: Rest API documentation is out of date in Koha manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The 'REST services' documentation does not fit the current implementation of the koha rest API. For instance, the documentation shows a 'user' endpoint: GET user/byid/:borrowernumber/holds GET user/:user_name/holds GET user/byid/:borrowernumber/issues GET user/:user_name/issues GET user/:user_name/issues_history GET user/byid/:borrowernumber/issues_history GET user/today GET user/all POST user But the endpoint implemented in api/v1 is "patrons", e.g. https://intranet.bywatersolutions.com/api/v1/patrons/221 The best current documentation that I'm aware of is https://wiki.koha-community.org/wiki/REST_api_RFCs It would be nice to build this documentation via api/v1/spec see also bug 17694 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21817] New: Mock userenv should be a t::lib::Mocks method
by bugzilla-daemon＠bugs.koha-community.org 04 May '19

04 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21817 Bug ID: 21817 Summary: Mock userenv should be a t::lib::Mocks method Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 18750] New: t/db_dependent/Circulation/Branch.t fails.
by bugzilla-daemon＠bugs.koha-community.org 04 May '19

04 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18750 Bug ID: 18750 Summary: t/db_dependent/Circulation/Branch.t fails. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: mtompset(a)hotmail.com QA Contact: gmcharlt(a)gmail.com prove t/db_dependent/Circulation/Branch.t fails test 12 not ok 12 - AddReturn respects default return policy - return to homebranch In C4::Circulation, the CanBookBeReturned returns 0 for the wrong branch, but never tests if it is returnable for the right branch. Adding in logic triggers the NeedsTransfer else case near the end of the AddReturn function. It is unclear what else might break as a side-effect of this patch method. I will put this into Discussion, unless someone else can verify this is the correct way to fix the problem. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 20997] New: Add Koha::Account::Line::apply
by bugzilla-daemon＠bugs.koha-community.org 03 May '19

03 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20997 Bug ID: 20997 Summary: Add Koha::Account::Line::apply 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There should be a method to apply a credit to a debit. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 21607] New: Koha::Account::Line->apply should store credits as negative amounts
by bugzilla-daemon＠bugs.koha-community.org 03 May '19

03 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21607 Bug ID: 21607 Summary: Koha::Account::Line->apply should store credits as negative amounts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It incorrectly sets positive values, which are internally considered debits in Koha. This should be fixed ASAP so 18.11 doesn't include the bug (it is the first release to have this code). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 21844] New: Add callnumber to fines descriptions
by bugzilla-daemon＠bugs.koha-community.org 03 May '19

03 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21844 Bug ID: 21844 Summary: Add callnumber to fines descriptions 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would like to be able to do a shelf check when a patron disputes a lost charge. Providing the callnumber in the lost fine description would make this much easier -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 19496] New: Patron notes about item does not get emailed as indicated
by bugzilla-daemon＠bugs.koha-community.org 02 May '19

02 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19496 Bug ID: 19496 Summary: Patron notes about item does not get emailed as indicated Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org According to Bug 14224, with the system preference 'allowcheckoutnotes' enabled, the process should go like this: 1.The patron leaves a note on an item in the OPAC 2.A notice is generated and will be emailed to branch email. 3. Upon checkin of the item the note is displayed on the staff client. However, currently with this system preference enabled, 1. The patron leaves a note on the item in the OPAC 2. The patron's email receives the notice. 3. Upon check in of the item, the note is displayed on the staff client. There are two other bugs are shown as block to the original bug 14224 - these bugs are 17698 and 18915. -- You are receiving this mail because: You are watching all bug changes.

1 28