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

[Bug 36034] New: cas_ticket is set to serialized patron object in session
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36034 Bug ID: 36034 Summary: cas_ticket is set to serialized patron object in session Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org The fix for bug 34893 alters the return value type of checkpw, but does not adequately update the code everywhere where this is used. In particular, with shibboleth enabled the cas_ticket is sent to a patron object which gets serialized into the user session which quickly consumes a large amount of disk space on a busy system. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 22780] New: MarkLostItemsAsReturned - map to Lost-sttaus instead of context where the transaction took place
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22780 Bug ID: 22780 Summary: MarkLostItemsAsReturned - map to Lost-sttaus instead of context where the transaction took place 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: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Syspref MarkLostItemsAsReturned is mapped to the context where you make the transaction - Holds to pull list, longoverdue cronjob et.c. I can't see any logical reason for this! I think it would be better to map to Lost-statuses: Lost = don't mark as returned Longoverdue = don't mark as returned Lost and paid for = mark as returned et.c. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38772] New: Typo 'minPasswordPreference' system preference
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38772 Bug ID: 38772 Summary: Typo 'minPasswordPreference' system preference Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Typo in system preference 'minPasswordPreference' -> 'minPasswordLength' in opac/opac-password-recovery.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 38653] New: Obsolete call on system preference 'OPACLocalCoverImagesPriority'
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38653 Bug ID: 38653 Summary: Obsolete call on system preference 'OPACLocalCoverImagesPriority' Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org This is in opac/opac-search.pl a call on system preference OPACLocalCoverImagesPriority. This preference does not exists elsewhere and dates back to Koha 3.8 from Bug 1633 I propose to remove ;) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 38000] New: Redundant code import in search.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38000 Bug ID: 38000 Summary: Redundant code import in search.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 37848] New: "Run with template" options need formatting
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37848 Bug ID: 37848 Summary: "Run with template" options need formatting 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 171097 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=171097&action=e… Screenshot of the Run with template drop-down This seems to be the same problem as Bug 36157, but maybe related to the bootstrap upgrade? To replicate (copied from bug 36157): 1. Create a notice with the module of "Reports" -- add something to the "Print" section. Example from the other bug: [% FOREACH b IN data %] <div class="panel panel-default"> <div class="panel-heading">[% b.surname %], [% b.firstname %]</div> <div class="panel-body">Expiration: [% b.dateexpiry %]</div> <div class="panel-footer">ID: [% b.borrowernumber %]</div> </div> [% END %] 2. Create and run a saved report. Example from the other bug: SELECT * FROM borrowers 3. Click on the "Run with template" dropdown and hover the template title. I attached a screenshot of what it looks like in my ktd (Chrome on Ubuntu 22.04). -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 37265] New: Consideration of UniqueItemFields setting when receiving items in an order.
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37265 Bug ID: 37265 Summary: Consideration of UniqueItemFields setting when receiving items in an order. Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dudzikmichal(a)wp.pl QA Contact: testopia(a)bugs.koha-community.org When using the Koha acquisition module to receive items (basket receiving an order), Koha does not consideration of UniqueItemFields setting. The problem is that you can accidentally attach 3 items to an order with the same values. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 34346] New: Adding duplicate tag to a framework leads to error page, should give user readable error message
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34346 Bug ID: 34346 Summary: Adding duplicate tag to a framework leads to error page, should give user readable error message Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I tried adding a tag to the default framework and got a 500 error. It was because the tag already existed. Elsewhere in Koha, we get a user readable message saying something like "An error occurred when inserting this patron category. The patron category might already exist." To replicate: 1. In the staff interface, go to Administration > MARC bibliographic framework 2. Click the Actions button next to the default framework and choose MARC structure 3. Click New tag 4. Fill out the form to add an already existing tag number Tag: 699 Label for lib: Local subject Label for OPAC: Local subject 5. Click Save changes --> 500 error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 37535] New: Adding a debit via API will show the belated patron as the librarian that caused the debit
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37535 Bug ID: 37535 Summary: Adding a debit via API will show the belated patron as the librarian that caused the debit Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When POSTing { "amount": 1.17, "description": "some description", "internal_note": "internal_noteo", "type": "MANUAL", "user_id": 17 } to http://localhost:8081/api/v1/patrons/5/account/debits I would expect patron 5 to be debited by user_id 17. At least that is what the definition for debit says. But instead the belated patron is also shown as librarian in http://localhost:8081/cgi-bin/koha/members/accountline-details.pl?accountli…<ACCOUNTLINE FROM RESPONSE> When POSTing without user_id I would expect that the user_id is gained from the api user, but also the belated patron is shown as librarian. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 37404] New: Typo in intranetreadinghistory description
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '25

22 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37404 Bug ID: 37404 Summary: Typo in intranetreadinghistory description Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The description currently reads "Allow/Don't allow staff to access a patron's checkout (checkout history is still stored, regardless of staff being allowed access or not)." It should be "a patron's checkout history" rather than "a patron's checkout". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12