April 2022 - Koha-bugs - lists.koha-community.org

[Bug 23263] New: RecordedBooks shows 'Check out' button for unavailable items
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '22

24 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23263 Bug ID: 23263 Summary: RecordedBooks shows 'Check out' button for unavailable items 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The recorded books code checks if the current patron has a specific item checked out, if not it shows a checkout button. We should instead check the availability of the item and only show a button if it is available. Currently RB digital results don't have this information: https://gitlab.com/srdjan-catalyst/webservice-ils/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 22028] New: RecordedBooks integration with audio and magazine titles
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '22

24 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22028 Bug ID: 22028 Summary: RecordedBooks integration with audio and magazine titles Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently, the Recorded Books integration from [17602] Integrates support for RecordedBooks (formerly OneClickDigital) API integrates ebook titles. Audiobooks and magazines would be a good enhancement to be searched and circulated with this integration. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30449] New: Missing FK constraint on borrower_attribute_types
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '22

24 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30449 Bug ID: 30449 Summary: Missing FK constraint on borrower_attribute_types Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Not in kohastructure, but present for a long time already in updatedatabase: $DBversion = "3.07.00.034"; $dbh->do("ALTER TABLE borrower_attribute_types ADD CONSTRAINT category_code_fk FOREIGN KEY (category_code) REFERENCES categories(categorycode)"); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 21586] New: Add generic OpenIDConnect client implementation
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '22

24 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21586 Bug ID: 21586 Summary: Add generic OpenIDConnect client implementation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org It would be great to have a generic OpenIDConnect client that anyone could point at any OpenIDConnect server for authentication. Years ago, I wrote this software client for a client that needed to connect to 2 different upstream servers. More recently, I've re-used the code for a different client with a different upstream server. The first third-party server wasn't compliant to the standard, so there are some hacks in my code, but the second latest third-party server does seem compliant, so you should be able to use this code legitimately without compromising as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 28696] New: Point of sale: attempting to pay with the "Enter" key cause an overcharge in the database
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '22

24 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28696 Bug ID: 28696 Summary: Point of sale: attempting to pay with the "Enter" key cause an overcharge in the database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: marie-luce.laflamme(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This problem occurs if you forget to fill in the collect payment fields, then press on the “Enter” key. When a message Required field shows up, the payment will not be saved correctly in the database. Instead, Koha secretly charges the failed payment in the database before confirming the real payment on the web interface. E.g . If the item cost = $1 and you press 3 times «Enter» with missing payment fields, the web interface and receipt confirm a $1 payment, while the database register a $3 payment (3 X $1 ) for the same transaction id. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 30478] New: Unexpected behavior in patrons' accounts when un-losing items via batch item modification
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '22

23 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30478 Bug ID: 30478 Summary: Unexpected behavior in patrons' accounts when un-losing items via batch item modification Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If circulation rules allow refunds on returns and MarkLostItemsAsReturned is set to return from batch mod, an item that is charged as Lost to a patron's account will have the replacement fee removed if that item is un-lost through batch item modification. Additionally, if the item is still checked out, it will be returned/removed from their account. Scenario 1: -Set 'Lost item fee refund on return policy' to 'Refund lost item charge' -Set MarkLostItemsAsReturned to 'from the batch item modification tool' -Check item out to patron -Lose item from Items tab (items are *not* returned when marked lost on Items tab per MarkLostItemsAsReturned) -In patron's account, verify that item is still checked out to patron with lost status applied, and that replacement fee is charged to their account -In bib, verify that item shows as Lost and checked out -In Batch Item Modification, delete lost status (no other changes made) -In patron's account, note that item is no longer checked out and the replacement fee has been removed. The Accounts tab indicates that the item was returned. -In bib, item status is Lost but the item is no longer marked as checked out. Scenario 2: -Set 'Lost item fee refund on return policy' to 'Refund lost item charge' -Set MarkLostItemsAsReturned to 'from the batch item modification tool' and 'from the items tab of the catalog module' -Check item out to patron -Lose item from Items tab -In patron's account, verify that item is no longer checked out, and that replacement fee is charged to their account -In bib, verify that item shows as Lost but not checked out -In Batch Item Modification, delete lost status (no other changes made) -In patron's account, note that the replacement fee has been removed. The Accounts tab indicates that the item was returned. -In bib, item status is Available -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 30620] New: Add a warning close to /*!VERSION lines in kohastructure.sql
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '22

23 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30620 Bug ID: 30620 Summary: Add a warning close to /*!VERSION lines in kohastructure.sql Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org These first lines in kohastructure are just ignored by DBIx::RunSQL. They could serve a purpose however when running the file directly on the sql command line. So we should at least add a comment to warn people. On bug 26947 some of these settings are taken over in C4::Installer::load_db_schema. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 30366] New: Warn when running automatic_item_modification_by_age.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '22

23 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30366 Bug ID: 30366 Summary: Warn when running automatic_item_modification_by_age.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 25790 When using the ./misc/cronjobs/automatic_item_modification_by_age.pl -v after setting up rules under tools > Automatic item modifications by age the script outputs several lines of warnings: With patch from 22827: Use of uninitialized value in string eq at /kohadevbox/koha/C4/Items.pm line 1856. Master as of today: Use of uninitialized value in string eq at /kohadevbox/koha/C4/Items.pm line 1852. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25790 [Bug 25790] [OMNIBUS] warnings removal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 22379] New: ILS-DI Method "CancelHold" don't check CanReserveBeCanceledFromOpac
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '22

23 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22379 Bug ID: 22379 Summary: ILS-DI Method "CancelHold" don't check CanReserveBeCanceledFromOpac Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Requests to cancel a hold done through ILS-DI CancelHold method do not check same conditions as cancellation done through the OPAC interface. Here are the conditions (extract from C4/Reserves.pm) : Returns 1 if reserve can be cancelled by user from OPAC. First check if reserve belongs to user, next checks if reserve is not in transfer or waiting status -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 30143] New: OAI-PMH provider may end up in an eternal loop due to missing sort
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '22

23 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30143 Bug ID: 30143 Summary: OAI-PMH provider may end up in an eternal loop due to missing sort Change sponsored?: --- Product: Koha Version: 21.11 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: ere.maijala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org The OAI-PMH provider may end up in an eternal loop when processing deleted records due to the select statement missing sort (and limit). If records are not returned from the database in biblionumber order naturally, this omission may lead to the same records to be processed with each subsequent request, or records to be skipped. Fix coming up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20