October 2024 - Koha-bugs - lists.koha-community.org

[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 36752] New: Include "charged items" in the SIP2 Patron Info response
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36752 Bug ID: 36752 Summary: Include "charged items" in the SIP2 Patron Info response Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org If you set Y (at the right position) in the 63 summary request, the 64 should contain "charged items", i.e. the items that you have on loan. The code for handle_patron_info just contains a TODO here :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[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 24679] New: Allow to apply a MARC modification template in export tool
by bugzilla-daemon＠bugs.koha-community.org 26 May '26

26 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24679 Bug ID: 24679 Summary: Allow to apply a MARC modification template in export tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Tools Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 30

[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 19501] New: New list category to restrict specific lists to staff & hide from OPAC
by bugzilla-daemon＠bugs.koha-community.org 26 May '26

26 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19501 Bug ID: 19501 Summary: New list category to restrict specific lists to staff & hide from OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We are creating various lists of titles that need to be hidden from view in the OPAC for the time being but other staff members need to see them. At the moment the options are Public or Private so this won't do what we require. We would like an additional list category selection of Staff so that those lists are then visible in the staff client (& presumably also to anyone who logs into the OPAC with a staff permissions login) but are not publicly visible in the OPAC. The intention is that multiple staff members may need to add items to some of these lists. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 36022] New: Add default recipient phone number country code syspref for SMS::Send driver
by bugzilla-daemon＠bugs.koha-community.org 25 May '26

25 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36022 Bug ID: 36022 Summary: Add default recipient phone number country code syspref for SMS::Send driver 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If using an international SMS::Driver it would be convenient if you could set a default country code for patron smsalertnumbers that do not include a country code, especially since Koha allows input in both formats. This will allow the user to set a default country code that will be prepended to all non interational phone numbers for the SMS::Driver->send_sms "to" parameter. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 28884] New: ElasticSearch: Question mark in title search returns no results
by bugzilla-daemon＠bugs.koha-community.org 25 May '26

25 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28884 Bug ID: 28884 Summary: ElasticSearch: Question mark in title search returns no results Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)equinoxinitiative.org When searching for a title with a question mark, Who's Afraid of Virginia Woolf? for example, Koha returns no results with ElasticSearch. Removing the question mark or escaping it retrieves results, as does enclosing the entire title with the question mark in quotes. Since ? is a wildcard for ElasticSearch, this may be expected behavior (I'm not sure that it is or isn't), but explaining to patrons that they need to change their search behavior can be a big ask for libraries. Not sure what the best option is. Perhaps a system preference to automatically escape ? and not treat it as a wildcard for those libraries who would prefer that? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59