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

[Bug 33047] New: Local cover image fetchers return 500 internal error when image not available
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33047 Bug ID: 33047 Summary: Local cover image fetchers return 500 internal error when image not available Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Because of an uncaught exception, both catalogue/image.pl and opac/opac-image.pl return 500 errors when asked to provide the image by biblionumber for a bib that does not exist. This is a bit untidy; if the bib does not exist, *image.pl should either return the default one-pixel image or perhaps a 404, but not the error page. This normally isn't a huge deal when the local cover images are displayed by the staff or public catalog, as both of those interfaces inherently only display bibs that are known to exist. However, since it is possible for external clients to want to get at local cover images (e.g., see https://github.com/vufind-org/vufind/pull/2444) better provision should be made if the client requests the local cover of a nonexisting bib (e.g., if the bib had been deleted since the last time that the external client got knowledge of it). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 33858] New: Date for pending offline circulation is unformatted
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33858 Bug ID: 33858 Summary: Date for pending offline circulation is unformatted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Following the test plan on bug 33838 (includes a koc test file) I noticed that the date in the pending offline circulations table is not formatted according to the DateFormat system preference. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 33781] New: Terminology: Item already issued to other borrower.
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33781 Bug ID: 33781 Summary: Terminology: Item already issued to other borrower. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-user.tt:156 Item already issued to other borrower. issued should be "checked out" -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 33667] New: 'Copy to all libraries' doesn't work on editing holidays
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33667 Bug ID: 33667 Summary: 'Copy to all libraries' doesn't work on editing holidays Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: michaela.sieber(a)kit.edu When editing an existing holiday and checking the "copy to all libraires" checkbox, the other calendars won't get updates. To test: A: * Add a new unique holiday to branch A * Check 'Copy to all libraries' checkbox * Save * Verify the entry shows on all calendars, within the calendar and in list on the right B: * Add another unique holiday to branch A * Don't check checkbox 'Copy to all libraries' * Save * Verify the holidays shows on all calendars as a green box (?) * Edit the holiday, now check 'copy to all libraries' * Verify nothing has changed in other calendars: only the green box, no holiday in list on the right * Edit again, make a change to description, check checkbox, save * Verify it's still not showing in the other calendars -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 18855] New: Fines cronjob can cause duplicate fines if run during active circulation
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18855 Bug ID: 18855 Summary: Fines cronjob can cause duplicate fines if run during active circulation 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On systems with a decent amount of fines it seems the fines cron can cause issues for patrons. The problem seems to be: 1 - Fines job runs and selects overdues 2 - Patron with an overdue returns books, fine is updated, item is checked in 3 - Fines job iterates to the item that was checked in during step 2, sees there is no accruing fine, generates a new accruing fine I am not sure what the best solution here is, possibly we should confirm the issue before generating the fine in the cronjob? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 33720] New: koha-upgrade-schema should restart memcached
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33720 Bug ID: 33720 Summary: koha-upgrade-schema should restart memcached Change sponsored?: --- Product: Koha Version: master Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Hello community, We have been caught out with a minor annoyance in the koha-upgrade-schema script (Debian package) - upon reloading a database from an SQL dump file (e.g. re-imaging a test server from a live system), the database upgrade appears to complete successfully, but in fact steps are missed. We believe this is because memcached is keeping the software version cached as a value, as a restart of memcached seems to resolve the issue. I attach a proposed solution; restarting memcached just before calling the updatedatabase.pl script. I hope this makes sense, can can be backported for 22.11.xx. Many thanks, Jake -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 23775] New: Claiming a serial issue doesn't create the next one
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23775 Bug ID: 23775 Summary: Claiming a serial issue doesn't create the next one Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com == test plan == 1. have a vendor with an email address for claiming late issues 2. have a subscription linked to this vendor - You can create a new one with arbitrary values 3. Go to "Serial collection" 4. click "Edit serials" 5. Status of the latest: change from Expected to Claimed 6. save 7. see that the next issue has been created 8. go to /cgi-bin/koha/serials/claims.pl 9. make a claim on the expected issue of the previously used serial 10. Then you see that the next issue hasn't been created -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 33872] New: Duplicated patron's registration date is set to expiration date of template patron
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33872 Bug ID: 33872 Summary: Duplicated patron's registration date is set to expiration date of template patron Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When duplicating a patron, the duplicated patron’s registration date automatically populates with the expiration date of the patron being duplicated. So, the registration date for the new patron is the expiration date of the original patron. This appears to be new behavior in 22.11 - I cannot replicate on 22.05. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 33778] New: Move t/Auth_with_shibboleth.t to db_dependent
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33778 Bug ID: 33778 Summary: Move t/Auth_with_shibboleth.t to db_dependent 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 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 33578] New: Cannot edit patron restriction types
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33578 Bug ID: 33578 Summary: Cannot edit patron restriction types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, martin.renvoize(a)ptfs-europe.com When editing an existing patron restriction type you'll always get an error on saving: Label is already in use Of course the label is already in use... for the restriction type I am just editing. To test: * Activate use of patron restriction types * Edit any of the system types * Save --> Notice error :( -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25