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

[Bug 29238] New: Cataloging cron jobs are not logged
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29238 Bug ID: 29238 Summary: Cataloging cron jobs are not logged 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: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz After a few cron jobs related to authority records (misc/migration_tools/remove_unused_authorities.pl, misc/link_bibs_to_authorities.pl) were set up to run on our instance, I went to check the Log Viewer tool but couldn't tell that they were configured. I was told that only newer cron jobs actually appear in the logs, and on inspecting those two I saw that they lacked the call to `cronlogaction()` which our circulation-related cronjobs have. It'd be helpful to know if/when these jobs ran. I realize this is a bit debatable because those two scripts don't reside in misc/cronjobs and right now the only scripts that call `cronlogaction()` are in that directory. Is it appropriate to add that logging to these scripts? We do run them on a schedule, it's important to our authority records workflow. This is the complete list of ones I'd like to add logging to: - misc/link_bibs_to_authorities.pl - misc/cronjobs/merge_authorities.pl - misc/migration_tools/remove_unused_authorities.pl A side note: there are several scripts in misc/cronjobs, like merge_authorities.pl, that are not logged and probably should be, but that is a larger bug and I'd like to focus on these first since they're relevant to us. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 27305] New: RSS feed for due dates
by bugzilla-daemon＠bugs.koha-community.org 29 May '26

29 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27305 Bug ID: 27305 Summary: RSS feed for due dates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicobako(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As a user, when I browse the books that I am currently borrowing from the library, I can download the due dates as an ical file. This is wonderful, but it would be really nice to be able to have an RSS feed (a url link) to this calendar. That way I can sync the due dates to my personal calendar, like Gmail, for example. I can add an RSS feed to my personal calendar, and it will automagically populate my personal calendar with the due dates. Thank you in advance! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 23665] New: Add option in Patron Extended Attributes to have a checkbox instead of options
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23665 Bug ID: 23665 Summary: Add option in Patron Extended Attributes to have a checkbox instead of options 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: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be helpful for some libraries to add an option to have a checkbox rather than an authorized value or input box so when people are opting in to something or have signed a waiver/did the class required to use the 3-d printer etc, we can just check a box rather than using a drop down. There was some discussion about this at koha-US conference this week. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28732] New: Order and claim emails don't work well with repeatable information
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28732 Bug ID: 28732 Summary: Order and claim emails don't work well with repeatable information Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org There is an issue with how the repeatable part of the notice is figured out. This sets some strict limits to how you can write the notice template. It appears that the repeat will happen from first to the last placeholder from an acq table used in the notice. The <order> tags don't appear to be used at all. Test plan: - Create a basket with more than one order line - Set up a notice called ACQORDER for sending order emails (templats below) - Make sure the vendor has an email set and all checkboxes in the contact are checked - Make sure your system can send emails - Click button "send order e-mail" on the basket summary page ------------------------------------------------ ACQORDER TEMPLATE 1: [%- USE Price -%] Dear... <order>Title: <<biblio.title>> Author: <<biblio.author>> Edition: <<biblioitems.editionstatement>> Year: <<biblio.copyrightdate>> ISBN: <<biblioitems.isbn>> Units: <<aqorders.quantity>> Price: [% <<aqorders.listprice>> | $Price %] EUR </order> Thank you! RESULT: Dear and Thank you only appear once. OK. Dear... Title: ... Author: ... Edition: 1. Auflage, Originalausgabe Year: ISBN: 9783839225837 Units: 1 Price: 13.99 EUR Title: ... Author: Edition: Year: 2020 ISBN: Units: 1 Price: 13.00 EUR Thank you! ------------------------------------------------ ACQORDER TEMPLATE 2: Only addition/change is the second line. [%- USE Price -%] <h2>Order: <<aqbasket.basketname>></h2> Dear... <order>Title: <<biblio.title>> Author: <<biblio.author>> Edition: <<biblioitems.editionstatement>> Year: <<biblio.copyrightdate>> ISBN: <<biblioitems.isbn>> Units: <<aqorders.quantity>> Price: [% <<aqorders.listprice>> | $Price %] EUR </order> </hr> Thank you! RESULT: Order:... and Dear... lines are repeated. For information from the basket this doesn't make sense. If you add a field from the branches table, this doesn't appear to cause any additional repeats. Order: 28.4.2021 Dear... Title: ... Author: ... Edition: 1. Auflage, Originalausgabe Year: ISBN: 9783839225837 Units: 1 Price: 13.99 EUR Order: 28.4.2021 Dear... Title: ... Author: Edition: Year: 2020 ISBN: Units: 1 Price: 13.00 EUR Thank you! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29923] New: Do not generate overpayment refund from writeoff of fine
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29923 Bug ID: 29923 Summary: Do not generate overpayment refund from writeoff of fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - turn finesmode on 2 - set circ rule a circ rule to charge fines 3 - perform a checkout that follows your circ rule, setting the due date in the past 4 - run the fines cron and confirm that it generates an accruing fine for your patron 5 - write off that fine 6 - edit your circ rule to remove the fine amount and interval 7 - check your item in 8 - see your patron now has a credit in the amount of the writeoff The overpayment credit should only be generated if we've taken payment on the fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 27826] New: Self checkout dies on '?' as a barcode
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27826 Bug ID: 27826 Summary: Self checkout dies on '?' as a barcode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Assign an item '?' as a barcode 2 - Check the item out to a patron 3 - Enable and visit the self checkout: http://localhost:8080/cgi-bin/koha/sco/sco-main.pl 4 - Try to load the patron with the item issued 5 - Boom! Error below: Template process failed: undef error - Quantifier follows nothing in regex; marked by <-- HERE in m/? <-- HERE / at /usr/lib/x86_64-linux-gnu/perl5/5.24/Template/VMethods.pm line 191. at /kohadevbox/koha/C4/Templates.pm line 122 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 24832] New: superlibrarian should have tools to delete notices
by bugzilla-daemon＠bugs.koha-community.org 27 May '26

27 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24832 Bug ID: 24832 Summary: superlibrarian should have tools to delete 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be helpful if the superlibrarian had the ability to delete one, some, or all of the notices in a user account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17617] New: Confirmation e-mail to patron when hold is placed
by bugzilla-daemon＠bugs.koha-community.org 26 May '26

26 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17617 Bug ID: 17617 Summary: Confirmation e-mail to patron when hold is placed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If an item is purchased from an online shop, the patron will receive a confirmation e-mail of their order. We would like to see something similar in Koha when a hold is placed. We think this would be useful to confirm some key points, for example: - confirm the hold has been added to the system - confirm the title details of the requested item - confirm the collection library - confirm the fee which will be charged for fulfilling the hold - confirm the fee which will be charged if the hold is not collected - explain how to cancel the hold if it's no longer required - explain how to make changes to the hold if any details (e.g. change collection library from AAA to BBB) alter - explain how the patron will be notified when the item is ready for collection There is already a system preference: emailLibrarianWhenHoldIsPlaced - which enables Koha to e-mail the library staff whenever a patron places a hold. Could the code behind this be adapted to e-mail patrons instead, perhaps? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 15792] New: Double-clicking the 'renew' button on circulation.pl will double-charge account management fee
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15792 Bug ID: 15792 Summary: Double-clicking the 'renew' button on circulation.pl will double-charge account management fee Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com PREREQUISITES 1) Create an account type that has an enrollment fee, and create a borrower of that type. 2) Write off any account management fees charged to that borrower by the account creation. STEPS TO RE-CREATE 1) Change borrower's dateexpiry to make the borrower expired. 2) Paste borrower's card number into 'Check out' bar 3) A warning will appear saying that the borrower's account has expired, including a 'Renew' link. 4) Double-click the link 5) Check the borrower's fines. You will see two account management fees in a row. distinct from the fee that was written off just after the patron was created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 21555] New: Merging Patrons allows for all patrons to be selected
by bugzilla-daemon＠bugs.koha-community.org 23 May '26

23 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21555 Bug ID: 21555 Summary: Merging Patrons allows for all patrons to be selected Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The feature of merging patrons (bug #9302 ) did include a fail safe, according to the bug, if/when using this feature, the option of "selecting all" patrons from a search was chosen, then the option to merge could not be used. When testing this feature, if a few patrons were chosen and then "select all" is chosen, the merge feature is still available to use. If no patrons are chosen and then "select all" is chosen, merge option is not available. Test: how it currently works 1. Search for Patrons by Last Name by Letter 2. From this list, choose patron a, patron b, patron c 3. See that merge patron option available 4. Now select all patrons - merge patron option still available Test: (how it should work) 1. Search for patrons by last name by letter 2.From this list choose patron a, patron b, patron c 3. See that merge patron option avail 4. Now "select all" patrons 3. See that merge patron option not available (greyed out) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14