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

[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 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

[Bug 29746] New: Add a handy Koha::Boolean class
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29746 Bug ID: 29746 Summary: Add a handy Koha::Boolean class 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 The idea is to provide an OO class that can carry a boolean value, and also useful messages for feedback. An example usage: sub safe_to_delete { my ( $self ) = @_; my $result = Koha::Boolean->new; my $can = 1; if ( condition_1 ) { $can = 0; $result->add_message({ message => 'has_debt' }); } ... if ( condition_n ) { $can = 0; $result->add_message({ message => 'has_guarantees' }); } return $result->set_value($can); } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 34076] New: [ALTERNATE] [DOCS] Automated screenshots using Cypress.io testing framework
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34076 Bug ID: 34076 Summary: [ALTERNATE] [DOCS] Automated screenshots using Cypress.io testing framework Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Documentation Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org See also bug 29716 for another implementation but the idea is the same. We want to use cypress to generate the screenshots of the manual. See also for a previous discussion - https://lists.katipo.co.nz/pipermail/koha/2018-January/049807.html -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 29712] New: [DOCS] [Omnibus] Content development guide
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29712 Bug ID: 29712 Summary: [DOCS] [Omnibus] Content development guide Change sponsored?: --- Product: Koha Version: master Hardware: All URL: https://wiki.koha-community.org/wiki/Documentation_-_C ontent_Development_Guide OS: All Status: ASSIGNED Severity: enhancement Priority: P3 Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Omnibus bug for the creation of a content development guide for the documentation team. It will include: * a style guide: guidelines for writing clear and concise content, including grammar and word lists * an information model: structures and guidelines to help us write different types of content consistently * a content strategy: a plan outlining how we develop content, including the types of information products we create, the tools we use, and the processes we follow -- You are receiving this mail because: You are watching all bug changes.

1 15