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

[Bug 39984] New: Recall notices use the email template to generate SMS notices
by bugzilla-daemon＠bugs.koha-community.org 23 May '25

23 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39984 Bug ID: 39984 Summary: Recall notices use the email template to generate SMS notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 23781 Found when testing bug 36020 and replicated on main - the recall notices RETURN_RECALLED_ITEM and PICKUP_RECALLED_ITEM both ignore the SMS notice template, and send the email notice template even when SMS is called for. To reproduce: 1. Enable UseRecalls syspref and set corresponding circulation rules: - Recalls allowed - Recalls per record - On shelf recalls allowed - set to "If any unavailable" - Recall due date interval - Recall pickup period 2. Set SMSSendDriver syspref to "Email" 3. Go to Tools > Notices and Slips 4. Edit the notice templates for RETURN_RECALLED_ITEM and PICKUP_RECALLED_ITEM: - Make sure both notices have templates defined for email and SMS notices - Make sure the email template is different from the SMS template 5. Find or create two patron accounts - Patron A and Patron B 6. Edit the following fields on both patron accounts: - Make sure an email address is defined - Under Patron Messaging Preferences, enable all Email and SMS notices (no digests) - Under Patron Messaging Preferences, enter a phone number for SMS 7. Check out an item to Patron A 8. Log into the OPAC as Patron B 9. Search for the item you checked out in step 5 10. Place a recall on that item 11. In the staff interface, check that item in and confirm the recall 12. Check the Notices tab on Patron A's account => You should see two new notices to return a recalled item - one email notice and one SMS notice 13. Look at the previews for the two notices => They are the same! :( 14. Check the Notices tab on Patron A's account => You should see two new notices to pick up a recalled item - one email notice and one SMS notice 15. Look at the previews for the two notices => They are the same! :( Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23781 [Bug 23781] Recalls notices and messaging preferences -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 39983] New: Return 405 (Method not allowed) when a route is called with the wrong method
by bugzilla-daemon＠bugs.koha-community.org 23 May '25

23 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39983 Bug ID: 39983 Summary: Return 405 (Method not allowed) when a route is called with the wrong method Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: tadeusz(a)sosnierz.com, tomascohen(a)gmail.com We just did a bit of debugging and the problem turned out to be that the wrong method was used (GET vs. POST) and this resulted in a 404. It might be a nice improvement if we returned 405 instead to give a better clue about the error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 39412] New: Ordering from staged records with item tags does not remove item tags
by bugzilla-daemon＠bugs.koha-community.org 23 May '25

23 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39412 Bug ID: 39412 Summary: Ordering from staged records with item tags does not remove item tags Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Export some records from Koha 2 - Set MarcItemFieldsToOrder: homebranch: 952$a holdingbranch: 952$b loc: 952$c price: 952$g|952$v itype: 952$y 3 - Stage your exported files for import - don't match and don't check for items 4 - Add to basket from the staged file 5 - Disable matching when adding orders 6 - Save the orders 7 - View the MARC of the new records from the interface 8 - Note marc has 952 fields 9 - You can view in the database in the biblio_metadata table as well: SELECT biblionumber, ExtractValue(metadata, 'count(//datafield[@tag="952"]/subfield[@code="9"])' ) AS counter FROM biblio_metadata WHERE ExtractValue(metadata, 'count(//datafield[@tag="952"]/subfield[@code="a"])' ) > 0 AND ExtractValue(metadata, '//datafield[@tag="952"]/subfield[@code="9"]' )='' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 39978] New: Allow assigning catalogue concern at creation
by bugzilla-daemon＠bugs.koha-community.org 23 May '25

23 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39978 Bug ID: 39978 Summary: Allow assigning catalogue concern at creation Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating a catalogue concern from the staff interface, it could be nice to allow the user to assign the concern while creating it. It would help simplify the process by removing the need to create the concern, then to manage it to assign it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39979] New: Reserves 'collect at' to default to patron home library from Koha reserves form
by bugzilla-daemon＠bugs.koha-community.org 23 May '25

23 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39979 Bug ID: 39979 Summary: Reserves 'collect at' to default to patron home library from Koha reserves form 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: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 182762 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=182762&action=e… 'collect at' default to the first library on the list as opposed to the patron's home library On the Reserves request form, the 'collect at' drop down for 'next available copy' will default to the first library in the drop down list. Instead, we want this to default to be the patron's home library. This would save time for staff as they would not have to search for the correct library from the list and only change this if the patron indicates they want to collect from a different site. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 39965] New: Disable the output of email and phone number from "Patron" in the circulation overdues report
by bugzilla-daemon＠bugs.koha-community.org 23 May '25

23 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39965 Bug ID: 39965 Summary: Disable the output of email and phone number from "Patron" in the circulation overdues report Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org How can I disable the output of email and phone number from "Patron" in the report? https://lists.katipo.co.nz/public/koha/2025-May/061408.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 37603] New: Protect static files served by Apache
by bugzilla-daemon＠bugs.koha-community.org 22 May '25

22 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37603 Bug ID: 37603 Summary: Protect static files served by Apache Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org There are times where it would be great to generate a large file in the background and then alert the user when it's ready to download. The problem at the moment is that proxying with Plack::App::CGIBin can lead to timeouts, and serving directly with Apache means no authentication/authorization checks. This morning I realised though that we could actually use mod_perl to write a Perl-based auth handler for Apache. (It looks like Nginx has a ngx_http_perl_module equivalent as well.) It would mean bolting on another dependency, but it's an interesting idea... Of course, an alternative would be to just go with something like bug 31380. That would be serving a static file via Starman, so it wouldn't be as efficient as Apache, but it wouldn't timeout like Plack::App::CGIBin... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39975] New: OpacMoreSearches HTML customization is mangled by TinyMCE
by bugzilla-daemon＠bugs.koha-community.org 22 May '25

22 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39975 Bug ID: 39975 Summary: OpacMoreSearches HTML customization is mangled by TinyMCE Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org OpacMoreSearches is supposed to be one or more <li> elements. However, when you save it in HTML customizations, it'll add a <ul></ul> tags around the <li> elements you define. This causes a poor display due to padding added by user agent stylesheets to <ul> elements. With this particular HTML customization, I think we'd want to prevent TinyMCE from doing a HTML cleanup. However, there are probably other HTML customizations where we want to keep that cleanup. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39969] New: Show a single (line-based image) barcode of a selected item under cataloguing/additem.pl
by bugzilla-daemon＠bugs.koha-community.org 22 May '25

22 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39969 Bug ID: 39969 Summary: Show a single (line-based image) barcode of a selected item under cataloguing/additem.pl Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org There could be use cases where one would like to show the barcode image that is generated from ONE, previously created item in the cataloguing/additem page. One such case would be to send this ONE barcode image to a label printer without having to go over all the required steps to generate a batch of ONE barcode, create a PDF and print it. This extra functionality is easy to implement using the -already present- action submenu and the -also already present- /svc/barcode?barcode=XXX endpoint, by adding a few simple lines of code in the /modules/cataloguing/additem.tt template. Alternatively, one could generate such a popup with an onmouseover event when hovering over the barcode number. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 39968] New: Exporting data from datatables can fail for generated file names
by bugzilla-daemon＠bugs.koha-community.org 22 May '25

22 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39968 Bug ID: 39968 Summary: Exporting data from datatables can fail for generated file names Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface 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 This was reported by a library exporting the acquisition details from the tab on the staff interface detail page. The title for the record was indeed very long, resulting in a problem saving the file on a Windows computer. Suggestion: If we want to keep using the title for the file name, we should limit it to a sane number of characters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1