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

[Bug 23837] New: detail.pl contains a lot of whitespace in the td.status cell
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '23

19 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23837 Bug ID: 23837 Summary: detail.pl contains a lot of whitespace in the td.status cell Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When looking at the code, I am seeing this: Waiting at Athol Library since 10/15/2019. Hold for: Not sure why all the whitespace (spaces/new lines/indentation) is there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 28556] New: Make guarantor information available in notices
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28556 Bug ID: 28556 Summary: Make guarantor information available in notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Since the change to accommodate multiple guarantees per borrower, it is impossible to get the garantor's information in notices. It is customary here to send things to the parent as C/O (care of), especially if it's by the mail. I was wondering if it was possible to make the guarantor information available in notices. Thanks! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 33239] New: Add the ability to run borrowers-force-messaging-defaults.pl only on a specified message name
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33239 Bug ID: 33239 Summary: Add the ability to run borrowers-force-messaging-defaults.pl only on a specified message name Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It would be helpful to run misc/maintenance/borrowers-force-messaging-defaults.pl with a speficied message name. So apply default category value only on some message (like Item_due) and keep patron choice for the others. Values of message name can be found in : https://git.koha-community.org/Koha-community/Koha/src/branch/master/instal… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 Lisette Scheer <lisette.scheer(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette.scheer@bywatersolut | |ions.com --- Comment #10 from Lisette Scheer <lisette.scheer(a)bywatersolutions.com> --- I agree that documentation is an essential part of this process. This is definitely something I'd love to see get moving again. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 28995] New: Add --added_after to writeoff_debts.pl
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28995 Bug ID: 28995 Summary: Add --added_after to writeoff_debts.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 27049 writeoff_debts.pl currently supports --added_before to make it work on fines added before a given date. It would be nice if we could also tell it to work on fines added after a given date, with --added_after. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27049 [Bug 27049] Add a script to bulk writeoff debts -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 27736] New: When an unauthenticated user goes to report a problem, the problempage URL will be lost
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27736 Bug ID: 27736 Summary: When an unauthenticated user goes to report a problem, the problempage URL will be lost Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org When an unauthenticated user goes to report a problem, they're first prompted to login, then they have to click the "report a problem" link a second time and now the value of the $referer variable is going to be opac-user.pl and not the original page. Steps to recreate: - enter a KohaAdminEmailAddress and set OPACReportProblem to Allow - as an unauthenticated user visit any page other than your account (opac-user.pl) e.g. search results (opac-search.pl) or a bib detail (opac-detail.pl) - select the "report a problem" link at the bottom - you're interrupted by the user login process, complete your authentication - you land on the user account page opac-user.pl - if you select "report a problem" again now, the "problempage" value on the form will be some form of "/cgi-bin/koha/opac-user.pl..." and not the original page you attempted to report There is a work around—users can return to where they originally had the problem and click "report a problem" there, but that's not intuitive nor user friendly. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 35171] New: runreport.pl cronjob should optionally send an email when the report has no results
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35171 Bug ID: 35171 Summary: runreport.pl cronjob should optionally send an email when the report has no results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Some libraries would like to know that a report was run overnight, even if there were no results. We should allow this as an optional feature. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 33050] New: More args for misc/cronjobs/runreport.pl
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33050 Bug ID: 33050 Summary: More args for misc/cronjobs/runreport.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Add to script misc/cronjobs/runreport.pl args for CSV : separator and quote -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 35549] New: Housebound patron holds should trigger a staff notice for delivery
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35549 Bug ID: 35549 Summary: Housebound patron holds should trigger a staff notice for delivery Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a hold is trapped for a housebound patron, there is no way for the staff to know that item should be scheduled for delivery. There are probably several ways to indicate delivery is needed, so discussion might be needed for the best approach. 1. A pop-up message to staff to set this item aside for delivery. 2. A Housebound module button/tool in the staff interface. Within could be a holds management button. This could further filled out with delivery scheduling, etc. 3. Add a holds for housebound tab in the holds awaiting pickup screen. 4. A special hold slip for housebound patrons. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 23935] New: Sharing on Social Media looks wrong
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '23

18 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23935 Bug ID: 23935 Summary: Sharing on Social Media looks wrong Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org When I tried sharing a record on Facebook, while I was writing the post, it showed the cover, but looked like it was including information from the login panel. Then when it was posted, it didn't include the cover or the login info. It did include the record title, but the image was the catalog banner/logo. Something isn't quite right with the social media posting. At least with Facebook. -- You are receiving this mail because: You are watching all bug changes.

1 3