October 2015 - Koha-bugs - lists.koha-community.org

[Bug 15068] New: Get rid of warnings in members/summary-print.pl
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15068 Bug ID: 15068 Summary: Get rid of warnings in members/summary-print.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial 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 Printing a summary from a member's detail page can result in a lot of warnings like: - use of uninitialized value in sprintf at /usr/share/kohaclone/members/summary-print.pl line 47 - Use of uninitialized value $roadtype in concatenation (.) or string at /usr/share/kohaclone/members/summary-print.pl line 61 - Use of uninitialized value in addition (+) at /usr/share/kohaclone/members/summary-print.pl line 87 - Argument "2015-11-03 23:59:00" isn't numeric in numeric comparison (<=>) at /usr/share/kohaclone/members/summary-print.pl line 103 -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 15036] New: Closeing and reopening a basket should not alter status of completed orders
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15036 Bug ID: 15036 Summary: Closeing and reopening a basket should not alter status of completed orders Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When a basket is closed all orders are set to status 'ordered', if reopened they are all set to 'new', however if some orderlines are receipted and the basket subsequently reopened and again closed (e.g. to cancel some orders) although the order has copies received set, a datereceived and a link to an invoice it status reverts to new 9after reopen) or on order (after close) which does not reflect its true state. These operations should not include completed lines in their status updates -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 14388] New: add sorting to funds
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14388 Bug ID: 14388 Summary: add sorting to funds Change sponsored?: --- Product: Koha Version: master Hardware: All URL: cgi-bin/koha/acqui/acqui-home.pl OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The list of funds on this page (cgi-bin/koha/acqui/acqui-home.pl) has no sorting in place. It should sort on fund name or code or something useful to help people find the fund they want. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 15079] New: Batch Delete Records Error
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15079 Bug ID: 15079 Summary: Batch Delete Records Error Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using the batch deletion tool, if the script attempts to delete an undeletable item, the script will die with the error: Label not found for "next BIBLIONUMBER" at /usr/share/koha/intranet/cgi-bin/tools/batch_delete_records.pl line 172. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 15061] New: Can't add item to rotating collection
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15061 Bug ID: 15061 Summary: Can't add item to rotating collection Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Everytime you enter barcode to add it to rotating collection, you get an error message: "Failed to add item with barcode xxx: NO_ID" Also, in empty collection you see table with items, but only with one empty row... -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 14632] New: Incorrect alert while deleting single item in batch
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14632 Bug ID: 14632 Summary: Incorrect alert while deleting single item in batch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: indradg(a)gmail.com Reporter: indradg(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In "Manage patron card batches", the user is prevented from deleting the items from a single item batch as that would remove the entry from table creator_batches effectively deleting the batch. However, the JS alert's message reads as "Please select at least label to delete.". This is incorrect as one item is already selected. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 14673] New: Renewals cause Sipserver to crash
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14673 Bug ID: 14673 Summary: Renewals cause Sipserver to crash Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Bug 13315 Changed the return of C4::Circulation::AddIssue to a hash reflecting the added issue ; However if AddIssue is called with the borrower currently having the item on loan a renewal is carried out nut as no issue is created in the db undef is returned rather than the issue structure. The same bug made the first thing the sipserver does is to extract the due_date from that non-existent structure causing a fatal error if it is a renewal. This is potentially a major bug as almost all self-issue units use checkout requests rather than renewal requests when renewing borrowers items -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 13411] New: Koha's SIP server returns not ok for checking in items that are not checked out
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13411 Bug ID: 13411 Summary: Koha's SIP server returns not ok for checking in items that are not checked out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 If an item is not checked out when a checkin via SIP2 is attempted, Koha's SIP server sends back an "ok" of 0, and the AF message "Item not checked out". I am not entirely sure this is good and correct behavior by the SIP2 protocol. In particular, this will cause SIP2 book sorting devices to fail on all items that are not checked out, causing them all to be put into the "special handling" been that should be reserved for things like items checked in at the wrong library and items on hold. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 14735] New: cache_expiry is not saved when updating a SQL report
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14735 Bug ID: 14735 Summary: cache_expiry is not saved when updating a SQL report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Steps to duplicate (must have memcached enabled): 1. Create and save a report using the default values for "Report is public" and cache time. 2. Run the report. 3. Edit the report changing the setting for "Report is public" to yes. 4. Save the report. The cache time is now 0. 5. Edit the report changing the cache time to 300. 6. Save the report. The cache time is now 0 again. This seems to be due to the fact that cache_expiry is not passed to the update_sql function in the phase 'Update SQL'. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 14739] New: Regression on adding several patrons to a new batch
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14739 Bug ID: 14739 Summary: Regression on adding several patrons to a new batch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org >From bug 14123 comment 4 Patron's Batches can only have a single patron added when making a new "batch". Clicking the "Add" text next to a name keeps placing it behind the pop-up, but replacing the previously clicked user. -- You are receiving this mail because: You are watching all bug changes.

1 74