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

[Bug 36191] New: Logs format should be consistent
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36191 Bug ID: 36191 Summary: Logs format should be consistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Koha logs are hard for tracking things. The main problem is they are inconsistent: api-error.log: [2022/07/06 12:01:26] indexer-error.log: 20240201 18:50:39 indexer-output.log -> NO DATE intranet-error.log.1 -> [Wed Feb 21 00:05:46.156462 2024] plack-api-error.log -> [2024/02/25 03:47:47] plack-error.log -> NO DATE plack-intranet-error.log -> [2024/02/25 15:17:15] plack.log -> 159.65.246.210 - - [25/Feb/2024:00:00:05 -0300] plack-opac-error.log -> [2024/02/25 00:12:27] sip.log -> NO DATE worker-error.log -> 20240201 18:50:29 worker-output.log -> no tiene fecha z3950-error.log -> [2024/01/23 15:21:58] z3950.log -> NO DATE zebra-error.log -> 20220222 16:10:50 zebra-output.log -> 22:15:17-18/09 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 16329] New: Koha::Logger->sql(). Unified interface to log SQL statements OR use DBIx::Log4perl
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16329 Bug ID: 16329 Summary: Koha::Logger->sql(). Unified interface to log SQL statements OR use DBIx::Log4perl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Instead of whenever needing to log SQL statements, making a custom logging output/function, introduce a centralized subroutine to handle all sql-statement logging. How the SQL-statements should be logged remains to be seen, but currently simply presenting very simple formatting we can discuss about. SQL libraries (DBI, DBIx) also allow logging SQL-statements but lack the fine-grained control Log4perl offers. Or maybe Log4perl can be integrated better to DBI / DBIx with this: https://metacpan.org/pod/DBIx::Log4perl Because I am not a huge fan of DBIx and also integrating that to Koha::Object is a lot of work, will not pursue that track further. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 16304] New: Koha::Logger, lazy load loggers so environment can be properly set.
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16304 Bug ID: 16304 Summary: Koha::Logger, lazy load loggers so environment can be properly set. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org If you instantiate Koha::Loggers before having set the C4::Context->interface, their interface defaults to 'opac'. This is rather undesired especially for 'commandline' scripts such as cronjobs. A solution to this is to lazyLoad loggers when they are really needed. LazyLoading might also have a performance boost when using packages that initialize a package-level logger but which never gets used. see t/Koha/Logger.t on how to replicate this issue, but here is a nutshell of how to replicate this issue: @@ file A.pm package A; use Koha::Logger; my $logger = Koha::Logger->get({category => __PACKAGE__}); #interface unknown sub doStuff { $logger->error('My interface is always "opac"'); } @@ script run.pl use C4::Context; C4::Context->interface('commandline'); use A; A::doStuff(); #error is logged using the "opac"-interface instead #of the "commandline"-interface -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 39320] New: Create a 'landing page' for ERM
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39320 Bug ID: 39320 Summary: Create a 'landing page' for ERM Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: ERM Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew.auld(a)ptfs-europe.com, jeremy.evans(a)ukhsa.gov.uk, jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 38201 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38201 [Bug 38201] VueJS architecture rethink -- You are receiving this mail because: You are watching all bug changes.

1 276

[Bug 36164] New: Bring more consistency to our module landing pages
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36164 Bug ID: 36164 Summary: Bring more consistency to our module landing pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha's modules have a variety of landing page designs. We should try to move to a more consistent approach across landing pages. This bug serves as a collector for such work. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 35750] New: Add DataTables responsive plugin to staff interface
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35750 Bug ID: 35750 Summary: Add DataTables responsive plugin to staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The OPAC has the DataTables responsive plugin to deal with tables on smaller screen sizes. The staff interface should have the same. The holdings table is a good example of a table that does work well with smaller screens. To recreate: 1. Go to detail page and look at the holdings table 2. At about 1000px or less you will start to see the table run off the screen 3. Look at the holdings table on an OPAC detail page. The table responds to screen size. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 31916] New: It would be nice to make the paging in datatables and search results consistent
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31916 Bug ID: 31916 Summary: It would be nice to make the paging in datatables and search results consistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The paging UI is nice in the catalog search results.. it would be great to clone that styling to the general datatables paging? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 40199] New: Datatables search for eUsage/ERM report results is broken
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40199 Bug ID: 40199 Summary: Datatables search for eUsage/ERM report results is broken Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, michaela.sieber(a)kit.edu, pedro.amorim(a)openfifth.co.uk When using the search input field on top of a eUsage report result, the search gets stuck in "Processing". This is basically the same error as bug 40198, but for another page of the ERM module. To test: - Activate the ERMModule via the system preference - Add at least one data provider - Add at least one report It doesn't matter if you have no data, the empty results table shows the error as well. - Select the report on the "Saved reports" tab - In the (empty) results table, type anything in the general search field on top - Confirm that the "Processing" appears, but doesn't go away Error from console: Uncaught TypeError: col.data is undefined Confirmed in main and in 24.11. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 34358] New: Generalise library selection filter for datatables
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34358 Bug ID: 34358 Summary: Generalise library selection filter for datatables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We add a custom library select option to the patron search results datatable. We should really generalise this away from the patron-search includes so it could be used on other ajax driven datatables with the header row filters enabled. We should support both 'data-filter="libraries"' at the table heading line definition and 'filter: "libraries"' in the datatable column settings definition level. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 38295] New: Standardize "select all" behaviours
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38295 Bug ID: 38295 Summary: Standardize "select all" behaviours 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Sometimes it selects all the visible checkboxes, sometimes all the checkboxes from the tables (even the non-visible ones). What is the expected behaviours? Should we be consistent or does it make sense to have different behaviours depending on the context? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8