January 2026 - Koha-bugs - lists.koha-community.org

[Bug 39389] New: Cannot use dataTables export function on checkout table in members/moremember.pl
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39389 Bug ID: 39389 Summary: Cannot use dataTables export function on checkout table in members/moremember.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com To recreate: 1. Find a patron with some checkouts 2. Go to members/moremember.pl?borrowernumber=X where x is the borrowernumber 3. Load the checkout table 4. Click 'Export' and choose any option. Uncaught TypeError: t.aoFooter[(intermediate value)][e] is undefined -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 38964] New: Fix column span in footer of staff interface account payment page
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38964 Bug ID: 38964 Summary: Fix column span in footer of staff interface account payment page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 33137 The footer of the table of charges on the account payment page has incorrect column spans, resulting in the rows having incorrect alignment. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33137 [Bug 33137] Make sure columns on transactions and 'pay fines' tab are matching up -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 38633] New: Calendar - Weekly closures are ignored when setting a yearly repeating holiday
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38633 Bug ID: 38633 Summary: Calendar - Weekly closures are ignored when setting a yearly repeating holiday Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.evans(a)ukhsa.gov.uk QA Contact: testopia(a)bugs.koha-community.org There seems to be an issue in Koha when setting up a yearly repeating holiday in a range. Currently running Koha 23.11.10 I had not noticed this issue in previous versions - we would have been running 22.11 when I last set up a repeating closure range. We set in the calendar a yearly closure period from 20 December to 6 January each year. This year 21/22 December and also 28/29 December are weekends when the library is already closed. However if I look at the 2025 or 2026 calendars, those dates which are weekends in 2024 are showing as open if they are on a weekday in 2025 or 2026. They should be closed as they are still within the date range of the yearly repeating closure. On testing it appears that, if weekly repeatable holidays are set, Koha ignores those days in the holidays on a range (presumably because they are already marked as closed). You can see this clearly because they do not appear in the list of dates on the right. This does become an issue when you are using holidays on a range repeatable yearly. Our temporary workaround was to remove all of the repeating holidays. Then add in the Christmas/ New year closure range and the add back in the weekly Saturday and Sunday closures. It appears to be necessary to set the yearly repeatable holidays on a range first, and to add the weekly repeatable holidays afterwards. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 39712] New: Query parameters break the manual mappings in vue modules
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39712 Bug ID: 39712 Summary: Query parameters break the manual mappings in vue modules Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, philip.orr(a)lmscloud.de If a url in a vue module contains query parameters the mapping for the manual fails and redirects to the homepage when 'Help' is clicked To reproduce navigate to the agreements page in ERM and create at least one. On the list page, use the filters so that you have query parameters in the page URL. Click the 'Help' button - you just get the manual home page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 22415] New: Koha::EDI should not use Log::Log4perl directly
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22415 Bug ID: 22415 Summary: Koha::EDI should not use Log::Log4perl directly 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We have Koha::Logger for instantiating Log4perl loggers now.. it should be used here too. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 38423] New: EDIFACT invoice files should skip orders that cannot be receipted rather than failing to complete
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38423 Bug ID: 38423 Summary: EDIFACT invoice files should skip orders that cannot be receipted rather than failing to complete Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When loading an EDIFACT invoice file, if the process finds a problematic order (usually a cancelled order or a deleted bibliographic or item record) the load process gets stuck and displays as 'Processing' in the EDFACT messages page. This usually means that the remainder of the orders in the file have to be manually receipted by library staff as vendors are reluctant to re-process part invoices. It would be preferable if the process could skip, and report any problem orders but complete all other receipts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 40205] New: "Default checkout, hold and return policy" cannot be unset
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40205 Bug ID: 40205 Summary: "Default checkout, hold and return policy" cannot be unset Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Rules in the "Default checkout, hold and return policy" section of the circulation rules can no longer be deleted/unset. To test: - Go to administration > circulation rules - Enter a value in one of the fields of the "Default checkout, hold and return policy" section - Save - Verify the value you entered was stored and is shown on the page - Click on the button "unset" - Confirm the confirmation question - Verify the value still shows, the rule was left unchanged The expected behavior is that the rule would be deleted and in the first column of the table it should say "Not set" as for a new installation. This was confirmed to be working correctly in 22.11. Broken in 24.11 Working correctly in main. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 41260] New: Running holds reminder cronjob with both triggered and holidays parameter may leave hold reminders unformed
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41260 Bug ID: 41260 Summary: Running holds reminder cronjob with both triggered and holidays parameter may leave hold reminders unformed Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz If one runs cronjob holds_reminder.pl with both triggered and holidays parameter, reminders are not formed for holds which waiting date is same as library's closing date. This happens because triggered parameter changes crons functionality to handle only holds which waiting date is exactly the same one as variable $waiting_since. If date in holds waiting date is bypassed by above conditions reminder is never formed. To reproduce: 1. Find hold which waiting date is 2 days from day you're testing this or update one holds waitingdate value directly from database. 2. Set day which is same as the holds waiting date as closing day from that library's calendar where hold is waiting in. 3. Run perl holds_reminder.pl -v -days 2 --triggered -holidays -c => Note that no reminder is formed for the hold. 4. Wait for one day and run the cron again. => Note that no reminder is formed for the hold. 5. Now run cron without triggered parameter. => Reminder id formed. Triggered parameter is supposed to prevent spamming patrons with hold reminders, but it shouldn't prevent libraries from sending out reminders in cases where hold just happens to have waiting date on a closing date. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41269] New: Patrons subpermissions should be fetched with borrowernumber instead of userid
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41269 Bug ID: 41269 Summary: Patrons subpermissions should be fetched with borrowernumber instead of userid Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In Koha-Suomi libraries we use cardnumbers as userids. This is done with a database trigger which sets cardnumber as userid when user is saved to database. Mostly this works well, but occasionally we have faced problems with patrons seemingly having no subpermissions. Patrons subpermissions are fetched from database with method get_user_subpermissions based on their userid. So even if they are saved in database they are not displayed in Koha's UI if userid is missing. While this isn't a major problem it can be confusing for staff members if they have accidentally created a patron without cardnumber/userid and then try to save permissions for them which seemingly are not saved. Also full permissions for patrons are still displayed normally so for consistency it would be logical to use borrowernumber to fetch subpermissions instead of userid. Method get_user_subpermissions is used in two places, member-flags.pl to fetch subpermissions and about.pl to check that SCO patron doesn't have extra permissions. As far as I can see changing it to use patrons borrowernumber shouldn't have any dramatic side effects. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 34631] New: Independentbranches : Non-superuser should not be able to write Additional contents for other branches
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34631 Bug ID: 34631 Summary: Independentbranches : Non-superuser should not be able to write Additional contents for other branches 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When syspref Independentbranches is enabled Non-superuser should not be able to write Additional contents for other branches To reproduce: 1- Connect to staff interface as superlibrarian 2- Enable IndependentBranches preference 3- Go to Tools -> HTML customizations 4- Crete an additional content for all libraries 5- Create or edit a borrower 5-1- Set permission for the borrower - catalogue - edit_additional_contents 4- Log in to the staff interface with the non-superlibrarian staff user 5- Go to Tools -> HTML customizations --> you can delete or edit the additional contents created by superlibrarian for All libraries 6- Click on New entry --> you can add additional content for other branches -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 94