August 2024 - 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 23 Jun '25

23 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 23 Jun '25

23 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 37265] New: Consideration of UniqueItemFields setting when receiving items in an order.
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 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 23 Jun '25

23 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 23 Jun '25

23 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 23 Jun '25

23 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

[Bug 37271] New: Recall status should be 'requested' in overdue_recalls.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37271 Bug ID: 37271 Summary: Recall status should be 'requested' in overdue_recalls.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, tomascohen(a)gmail.com Depends on: 19532 In "Bug 19532: Make recalls.status an ENUM" one-letter statuses were replaced by their verbal equivalents. But in overdue_recalls.pl remained "R". As a result, recalls never overdue. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 [Bug 19532] Recalls for Koha -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 37289] New: t/db_dependent/api/v1/authorised_values.t is failing under specific circumstances
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37289 Bug ID: 37289 Summary: t/db_dependent/api/v1/authorised_values.t is failing under specific circumstances Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org t/db_dependent/api/v1/authorised_values.t not ok 1 - list_av_from_category() tests Discussion on Mattermost pointed to this being related to a sequence issue. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 37277] New: Identifiers need a space between the ISBN (Print) and ISBN (Online) in ERM
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37277 Bug ID: 37277 Summary: Identifiers need a space between the ISBN (Print) and ISBN (Online) in ERM Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Created attachment 168623 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=168623&action=e… Identifiers run together To replicate: 1. Enable ERM 2. Go to Local Titles 3. Add a new title and add an identifier for both Print and Online. 4. Submit In the table with the list of titles see that the ISBN (Print) and ISBN (Online) run together. See attached example. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 37108] New: cash register statistics wizard is wrongly sorting payment by manager_id branchcode
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37108 Bug ID: 37108 Summary: cash register statistics wizard is wrongly sorting payment by manager_id branchcode Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: marie-luce.laflamme(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The Cash Register Statistics wizard in Koha is currently sorting payments based on the "manager_id" branchcode rather than the "accountlines.branchcode". This means that if staff switch to a different branch while working, Koha will unfortunately record all transactions under the branchcode associated with the staff account, not the branch they are currently logged into. I'm wondering if the SQL query behind the Cash Register Statistics wizard is using the recently added "accountlines.branchcode". See the test plan in the following comment and -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16