Bug 40147 - Datatables export options broken for list of pending charges in staff interface
Summary: Datatables export options broken for list of pending charges in staff interface
Status: RESOLVED DUPLICATE of bug 38964
Alias: None
Product: Koha
Classification: Unclassified
Component: Templates (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-16 10:04 UTC by Katrin Fischer
Modified: 2025-07-15 08:39 UTC (History)
4 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2025-06-16 10:04:07 UTC
Exporting the list of pending charges for a patron results in a JS error:

Uncaught TypeError: t.aoFooter[(intermediate value)][e] is undefined

To test:
* Make sure you have some pending/open charges on the patron account
* Go to Patron account > Accounting > Make a payment tab
* Click on any of the export options in the table header
* Verify that the "spinner" doesn't go away and nothing happens
Comment 1 Owen Leonard 2025-06-23 12:58:01 UTC
I can't seem to reproduce this problem.
Comment 2 Benjamin Daeuber 2025-06-27 18:43:04 UTC
I can confirm this is happening in 24.11. The export option opens, but once you click on it the spinner starts and the file never downloads.
Comment 3 Benjamin Daeuber 2025-06-27 18:43:36 UTC Comment hidden (obsolete)
Comment 4 Owen Leonard 2025-06-30 14:20:40 UTC
I can now confirm in 24.11 too. I'm pretty sure this is another symptom of Bug 38964
Comment 5 Jonathan Druart 2025-07-15 08:38:03 UTC
I do recreate the problem on 24.11.x, however if I cherry-pick 92c65166512c6d0a294df115fdc577e6d16f2923 the problem is fixed.
Comment 6 Jonathan Druart 2025-07-15 08:39:32 UTC

*** This bug has been marked as a duplicate of bug 38964 ***