November 2023 - Koha-bugs - lists.koha-community.org

[Bug 34462] New: Bug 25299 seems to have been reintroduced in more recent versions.
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34462 Bug ID: 34462 Summary: Bug 25299 seems to have been reintroduced in more recent versions. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the details screen of a patron record, if the patron is due to expire the alert at the top of the screen reads: Expiration: Patron's card will expire soon. Patron's card expires on The date is missing from this alert. This was originally fixed in Bug 25299, but seems to have been reintroduced. I can replicate this at 21.11 and 22.11. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 34271] New: Remove a few Logger statements from REST API
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34271 Bug ID: 34271 Summary: Remove a few Logger statements from REST API 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org See 22678 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 34204] New: Koha user needs to be able to login
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34204 Bug ID: 34204 Summary: Koha user needs to be able to login Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Found in bookworm: root@kohadevbox:koha$ koha-shell kohadev This account is currently not available. This is because /etc/passwd has /usr/sbin/nologin as shell, which is coming from the --disabled-login param we passed to adduser in koha-create. Looks like a bug has been fixed in adduser, because we didn't have this behavior in bullseye. We should certainly remove this parameter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 35042] New: Members.t: should not set datelastseen to NULL everywhere
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35042 Bug ID: 35042 Summary: Members.t: should not set datelastseen to NULL everywhere Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org It can be tempting to remove all records from a table or just set one column to NULL in a whole table to get a test working quickly. But we should better avoid that, or replace it by something less drastic (if reasonably possible). An example from Members.t: $dbh->do(q|UPDATE borrowers SET lastseen=NULL|); Surely you should not run such tests on a production db. But when someone forgets a rollback here or there, you might have some troubled data on your test system, and often needless. Note that I still often see test branches or item types appear in my test data after spending some time on a test db with master (running some tests). -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 34901] New: Item-level holds can show inaccurate transit status on the patron details page
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34901 Bug ID: 34901 Summary: Item-level holds can show inaccurate transit status on the patron details page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Hold requests Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a patron has an item-level hold, and that same item happens to be in transit or waiting for a different patron's hold, the patron details page will label the item-level hold as in transit. Since the item-level hold has not been found yet, it should have a blank status. To reproduce: 1. Place a record-level hold for Patron A, for pickup at a library other than the logged-in library 2. Check in an item --> Note that the item is now in transit for the hold 3. Place an item-level hold for Patron B on that same item 4. Go to the details page for Patron B, and click on their Holds tab --> The status column now says the hold is in transit, although it is actually Patron A's hold that is in transit 5. Switch the logged in library to match the pickup location for Patron A's hold 6. Check the item in again --> Note that Patron A's hold is now Waiting 7. Return to the details page for Patron B --> The status column says the hold is "not yet transferred" -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 34800] New: Update contributor openhub links
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34800 Bug ID: 34800 Summary: Update contributor openhub links Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 27249] New: Using the calendar to 'close' a branch can create an infinite loop during renewals
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27249 Bug ID: 27249 Summary: Using the calendar to 'close' a branch can create an infinite loop during renewals 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When calculating due date using holidays we don't account for the case where everyday is a holiday until the end of time To recreate: 1 - Set OverdueNoticeCalendar to 'Use calendar' and useDaysMode to 'Use the calendar to push' 2 - Browse to Tools->Calendar 3 - Set every day of the week to "Holiday repeated every same day of the week" 4 - Issue an item to a patron 5 - Check the box and select 'Renew selected items' 6 - Watch the spinner spin...and spin...and spin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 35317] New: Koha Offline Circulation Tool (KOCT) does not work in Firefox private mode
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35317 Bug ID: 35317 Summary: Koha Offline Circulation Tool (KOCT) does not work in Firefox private mode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The KOCT plugin doesn't work if you are using Firefox in private mode. To replicate: install the KOCT plugin in your firefox browser, set "Run in private windows" to "Allow", then open a new window in private mode, and click on the plugin. Under "Transactions", the plugin displays the following error message: "Unable to open database: InvalidStateError: A mutation operation was attempted on a database that did not allow mutations. Error code: undefined." An easy fix is just to not allow the plugin to be used in private mode (that is, set "Run in private windows" to "Don't allow" while you are configuring the add-on). We should at least add info about that to the manual. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 35315] New: Change Koha::Item->update_item_location() to Koha::Item->location_update_trigger()
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '23

12 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35315 Bug ID: 35315 Summary: Change Koha::Item->update_item_location() to Koha::Item->location_update_trigger() 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As per https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21159#c87 the method name added by bug 21159 should be renamed to location_update_trigger() -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15157] Cronjob to automatically restrict patrons with pending/unpaid charges
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '23

11 Nov '23

1 0