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

[Bug 43394] DT - pagination is broken if pageLength is not an integer
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43394 Pedro Amorim (ammopt) <pedro.amorim(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |26.11.00 released in| | Status|Passed QA |Pushed to main -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43354] New: ILL request table search returns a 500 error
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43354 Bug ID: 43354 Summary: ILL request table search returns a 500 error Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: nugged(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com Depends on: 33544 Target Milestone: --- The global Search field above the ILL requests table returns a 500 error after the request detail fields were combined into one display column. Steps to reproduce: 1. Enable the ILLModule system preference. 2. Open a patron record. 3. Click "ILL requests history" in the menu on the left. 4. Enter any text in the Search field above the table. Expected result: The table is filtered without an error. Actual result: Koha displays a 500 Internal Server Error and the table does not refresh. Technical note: The combined Request details column has an empty DataTables data source and no related-object search mapping. Global search therefore generates a query for "me." instead of the ILL request extended attributes. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33544 [Bug 33544] Squash some ILL fields to alleviate request table overflow -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 43259] New: Add to group does not add to group
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43259 Bug ID: 43259 Summary: Add to group does not add to group Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Steps to reproduce: 1 - Create a basket 2 - Create a group basket. At this step or the process : /cgi-bin/koha/acqui/basketgroup.pl clicking on "Add to group" does not add the basket to the group It is broken since 25.11.00. In 24.11, in basketgroups.tt there was an array named "grouped", to which the row containing the chosen element was added. It was created using : grouped = $("#grouped").DataTable($.extend(true, {}, dataTablesDefaults, { and row was added using grouped.row.add( row ).draw(); On main : $("#grouped").kohaTable(dt_params); row is added the same way : grouped.row.add( row ).draw(); This results in a JS error : "Uncaught TypeError: grouped.row is not a function" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 43117] New: t/Form_MessagingPreferences.t does not use Test::NoWarnings
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43117 Bug ID: 43117 Summary: t/Form_MessagingPreferences.t does not use Test::NoWarnings Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 34776 Target Milestone: --- From commit 6cc683b518223479f0c427a8305071fbd9581b5e Bug 34776: Unit tests -use Test::NoWarnings; -use Test::More tests => 2; +use Test::More tests => 1; +use Test::MockModule; +#use Test::NoWarnings; Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34776 [Bug 34776] Patron messaging preferences are lost when an error occurs during new account creation -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 42993] New: Koha::Edifact::Transport should log transport failures via Koha::Logger
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42993 Bug ID: 42993 Summary: Koha::Edifact::Transport should log transport failures via Koha::Logger Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Koha::Edifact::Transport reports every transport failure (no transport configured, connect failure, directory-change failure, file-listing failure and per-file download/upload failure) with carp. Under misc/cronjobs/edi_cron.pl these go to STDERR, so on a normal cron run the messages are lost: EDI simply goes quiet with nothing in editrace.log to explain why. This routes those failures through Koha::Logger on the 'edi' interface (the same interface edi_cron.pl already uses) so they are recorded in the EDI log. The two ingest()-level data warnings (duplicate filename, unreadable file) are intentionally left as carp: one is asserted by the existing unit test and neither is a transport failure. No change to the transfer logic. Test plan: 1. prove t/db_dependent/Koha/Edifact/Transport.t 2. Point an EDI account at an unreachable transport and run misc/cronjobs/edi_cron.pl; confirm the failure is now written to the EDI log rather than only to STDERR. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 42653] New: ILL request with log entries from multiple backends causes 500 error
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42653 Bug ID: 42653 Summary: ILL request with log entries from multiple backends causes 500 error Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 42968] New: 505 MARC field label is missing in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42968 Bug ID: 42968 Summary: 505 MARC field label is missing in the staff interface Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- The staff interface displays the contents of the MARC 505 field but does not display the "Contents:" label that appears in the OPAC. This results in an inconsistency between the OPAC and staff interface and makes it less clear what the displayed information represents. To recreate: 1.Create or locate a bibliographic record with data in the MARC 505 field. 2.View the record in the OPAC. 3.Note that the 505 field is displayed with the "Contents:" label. 4.View the same record in the staff interface. 5.Notice that the 505 field is displayed without the "Contents:" label. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 42652] New: Add per-account option to allow restricted patrons to retain SIP inet access
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42652 Bug ID: 42652 Summary: Add per-account option to allow restricted patrons to retain SIP inet access Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org This patch adds a new per-account SIP2 configuration flag, `patron_restriction_blocks_inet`, that controls whether a patron with an account restriction (debarment) also has their SIP inet profile blocked. Currently, when a patron is restricted in Koha, the SIP inet field (FID_INET_PROFILE) is set to N. This means online services that use SIP for authentication â such as PC booking systems or printing services â also deny access to the restricted patron. Libraries that want to block a patron from borrowing items but still allow them to use digital services have no way to achieve this. With this flag set to 0/false on a SIP2 account, restricted patrons will receive Y for inet access, allowing them to authenticate to online services, while checkout privileges remain blocked as normal. The default (NULL or true) preserves existing behaviour: restrictions block both checkouts and inet access. Test plan: 1. Apply all patches and run the database update. 2. Go to Administration > SIP2 accounts and edit an account. 3. Confirm the new "Restrictions block internet access" toggle is visible. 4. Create a test patron and apply an account restriction to them. 5. With the toggle unset (default), authenticate the patron via SIP and confirm the patron status response shows charge privileges denied AND inet profile N. 6. Set the toggle to false/disabled for the account and re-authenticate. 7. Confirm the patron status response still shows charge privileges denied but inet profile is now Y. 8. Confirm a non-restricted patron is unaffected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 26866] New: Items table on additem should sort by cn_sort
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26866 Bug ID: 26866 Summary: Items table on additem should sort by cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: - create a bib - add three items with source of classification LCC, call numbers: -- JC43 .G6 1890 -- JC330 .F74 2000 -- JC480 .R63 2006 - on additem.pl, sort the items table by "Full call number" - notice items are order incorrectly, going 330, 43, 480 - use a report to pull the cn_sort values for your 3 items, confirm that ordering by cn_sort in your report correctly orders them 43, 330, 480 We should use cn_sort here to get them in the correct order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 38174] New: Self Checkout renders alert for each checkout in session instead of just most recent checkout
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38174 Bug ID: 38174 Summary: Self Checkout renders alert for each checkout in session instead of just most recent checkout Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org In self checkout, if a patron scans a stack of books one at a time, an additional blue alert-info box is rendered for each new checkout. When this list becomes long it can push the barcode input down so far that it goes off screen which can be confusing for patrons. When not using batch checkout, self checkout should only render an alert-info box for the most recent scan. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16