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

[Bug 35656] New: Autorenewal notices can resend content that has already been relayed to the patron
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35656 Bug ID: 35656 Summary: Autorenewal notices can resend content that has already been relayed to the patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Enable AutoRenewalNotices 2. Choose a patron and make sure they have an email address and messaging prefs set to revieve an AUTO_RENEWAL_DGST 3. Set Circ rules so automatic_reneal is on 4. Check out several items (item 1, item 2, and item 3) to your chosen patron, and make sure they are within range of auto renewing via circ rule "No renewal before" 5. Put item 1, item 2, and item 3 on hold for someone else. 6. Run the autorenewal script. 7. Patron receives message that item 1, item 2, and item 3 will not be renewed because they are on hold for someone else. 8. Checkout item 4, making sure it is within range of auto renewing via circ rule "No renewal before". 9. Run the script, item 4 will successfully auto renew. However the notice always states that item 1, item 2, and item 3 on hold for someone else. Since the patron has already receievd a notice that item 1, item 2, and item 3 are on hold for someone else they do not want to be told again. The 2nd notice ( step 6 ) should only notifiy the patron that item 4 has been renewed. Currently, if 1 item changes in status we will resend info. about ALL renewals, even if patron has been notified. The autorenewal script should only send information on items that have changed in status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 31450] New: HTML customizations and News will not display on OPAC
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31450 Bug ID: 31450 Summary: HTML customizations and News will not display on OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: -Create some HTML Customizations and some News item that are set to display on the OPAC. -Go to the OPAC and notice none of these display. Possibly from Bug 15326? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 36531] New: Koha should serve text/javascript compressed, like application/javascript is
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36531 Bug ID: 36531 Summary: Koha should serve text/javascript compressed, like application/javascript is Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: phil(a)chetcolibrary.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 36463 Discovered via bug 36463, while we compress application/javascript, which is how we serve static .js files (though that may well be OS-dependent, coming from /etc/mime.types), we don't compress text/javascript, which is what output_with_http_headers produces when you ask for 'js'. That's actually currently the correct choice, since in May 2022 RFC 9239 obsoleted RFC 4329 which from 2006 to 2022 said that application/javascript was correct. Not many things seem to actually use output_with_http_headers for js (and most of them seem to actually mean json rather than js), but one huge one does: the initial load of svc/cataloguing/framework for the advanced cataloging editor loads an uncompressed 1.9MB of js (json, but because it's loaded through RequireJS, it winds up loaded as js rather than json, and serving it as json would produce an annoying browser warning) which compressed is a lovely 176KB. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36463 [Bug 36463] We should compress our JSON responses (gzip deflate mod_deflate application/json) -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 36873] New: Koha::Objects->delete should accept parameters and pass them through
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36873 Bug ID: 36873 Summary: Koha::Objects->delete should accept parameters and pass them through Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Taking `Koha::Item->delete` as an example, it accepts many parameters. Calling `Koha::Items->delete` will find out there's a `delete()` method defined in `Koha::Item` and loop through all items, calling that particular method. It would be handy if we could pass on some parameters. As an example, the following sequence: ```perl $biblio->items->delete; DelBiblio( $biblio->id); ``` would trigger reindexing the record for each item, and then when actually deleting the biblio. With the current codebase, to avoid it, we could instead do: ```perl foreach my $item ($biblio->items->as_list) { $item->delete( { skip_record_index } ); } DelBiblio( $biblio->id); ``` But it would be great if we could just write: ```perl $biblio->items->delete( { skip_record_index => 1 } ); DelBiblio( $biblio->id ); ``` -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 33641] New: We should record return branch in old checkouts (oldissues)
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33641 Bug ID: 33641 Summary: We should record return branch in old checkouts (oldissues) 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org See bug 33010 - the intention is to list the checkouts returned at current branch, but we only store this info in statistics. It would be handy to keep this info in the issue/oldissues tables -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 37509] New: (Bug 32693 follow-up) Elasticsearch status info missing from 'Server information'
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37509 Bug ID: 37509 Summary: (Bug 32693 follow-up) Elasticsearch status info missing from 'Server information' Change sponsored?: --- Product: Koha Version: unspecified 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: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com Depends on: 32693 After applying bug 32693 the Elasticsearch checks are performed only for 'System information' tab (About Koha section). As the result, information about Elasticsearch status is missing from the main tab (Server information). Only misleading empty "Version: | Nodes: | Status: not running" info is shown. The Elasticsearch checks should be (as a whole or in relevant fragments) performed both for "about" and "sysinfo" $tab(s). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32693 [Bug 32693] The 'About Koha' page loads slowly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 36098] New: Create Koha::Session module
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36098 Bug ID: 36098 Summary: Create Koha::Session module Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org There are times where you need to interact with Koha sessions, but you can't or don't want to load C4::Auth. I propose creating a minimal Koha::Session module, which will initially only have 1 method for fetching a session object, but over time can be built up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 36503] New: Add a plugin hook to modify patrons after authentication
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36503 Bug ID: 36503 Summary: Add a plugin hook to modify patrons after authentication Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: raphael.straub(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org This plugin hook allows to change patron data or define the patron based on the authenticated user. We use this hook to map the authenticated user to a patron record we migrated from the former ILS based on data from the identity provider. In Koha we use OIDC/Shibboleth for authentication but we don't have the EPPN in the former ILS and therefore not in the migrated patron record. We have written a plugin that takes the card number from the identity provider, searches a matching patron record in Koha and adds the EPPN to this patron. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 72

[Bug 37062] New: REST API endpoint expansion for table saved_sql
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37062 Bug ID: 37062 Summary: REST API endpoint expansion for table saved_sql Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: rudy.hinojosa(a)lifeafter.solutions CC: tomascohen(a)gmail.com I'd like to request a CRUD endpoint expansion for table saved_sql. I'm working on a report project that would greatly enhance the end user experience for robust reporting through Jasper. My project is called Koha-Jasper This program will allow a user to import a custom report PAK and automatically build a report for the end user via an API call. I'm currently using a direct sql call, but I don't want this to be the standard way to communicate to the table. More information on this project: https://lightwavelibrary.com/jasper/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31211] New: Check slips and notices for valid Template Toolkit and report errors
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31211 Bug ID: 31211 Summary: Check slips and notices for valid Template Toolkit and report errors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful for Koha to run a basic TT validation test and report back errors. That way if somebody misses an END tag or something of that nature, it will be easy to find and fix. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20