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

[Bug 37251] New: Default values should be applied when cataloging using the advanced cataloging editor (rancor)
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37251 Bug ID: 37251 Summary: Default values should be applied when cataloging using the advanced cataloging editor (rancor) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 36272] New: Exporting too many items from item search to barcode file gives "Request-URI Too Long"
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 Bug ID: 36272 Summary: Exporting too many items from item search to barcode file gives "Request-URI Too Long" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org To reproduce in KTD: - Login to the staff client - Go to "Item search" - Click on "Search" without adding any limitations - Change to "Show [All] entries" - this should show about 961 items - Click on "Select visible rows" - Click on "Export selected results (961) to" and choose "Barcode file" - This should result in this error: Request-URI Too Long The requested URL's length exceeds the capacity limit for this server. The URL of the page that shows the error looks like this: http://localhost:8081/cgi-bin/koha/catalogue/item-export.pl?format=barcodes… etc etc The solution is probably to do a POST, not a GET? Similar to bug 32278, but in a different area. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 36455] New: Default the hold queue link to your logged in library
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36455 Bug ID: 36455 Summary: Default the hold queue link to your logged in library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reduce clicks for library staff, defaulting the hold queue link on circulation home to the logged in library would be helpful, either as an option or as the default behavior with the option to run it for a different branch from the queue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 39305] New: About page must warn if Plack is not running
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39305 Bug ID: 39305 Summary: About page must warn if Plack is not running Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com CSRF protection is only working if Koha is running under Plack. The about page is not showing any errors if plack is not running. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 41209] New: Add the ability to choose an authentication method for patron or patron category
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41209 Bug ID: 41209 Summary: Add the ability to choose an authentication method for patron or patron category Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Created attachment 189218 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189218&action=e… How Moodle allows admin to choose an authentication method Right now when opacuserlogin is activated, all methods of authentication are available for patrons on the OPAC. So if a library decides to change authentication method (from manual to SSO, for example), they need to either hide the manual login boxes with Javascript or make sure to change the password previewsly used for the manual authentication. Otherwise, the patrons would be able to login with either one of the methods. It would be great if we could force an authentification method at least in each of the patron categories or even at the patron level. By choosing a an authentication method for a patron or category, that method would be the only one available on the OPAC for that patron or category. This would : - be less of a headeache for libraries that decide to change the authentification method. - be less confusing for patrons that want to login on Koha by only seeing what is available for them - be more secure than login bozes being hidden by javascript code (not an IT analyst here but i've been told this il a less secure way to manage it). See the attachment for the propose form (the screencapture was taken from Moodle) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[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