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

[Bug 42929] New: Cannot add borrowers.primary_message_contact in the HOLD_SLIP
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42929 Bug ID: 42929 Summary: Cannot add borrowers.primary_message_contact in the HOLD_SLIP Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: marie-luce.laflamme(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- At the moment, Koha only displays borrowers.primary_message_contact in the hold confirmation popup which was introduced by this bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37860. However, this field is not available for use in the HOLD_SLIP template, making it impossible to print patron's preferred message contact method on the slip. It would be nice if borrowers.primary_message_contact could also be available in the hold slip template. This could be a small enhancement that would make the printed hold slip more consistent with the information already shown in the interface. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 42853] New: OPAC self check-in does not resolve mis-routed transfers
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42853 Bug ID: 42853 Summary: OPAC self check-in does not resolve mis-routed transfers Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 42851 Target Milestone: --- Split off from bug 42851. When an in-transit item is checked in via the OPAC self check-in (SCI) interface at a branch that is NOT the transfer's tobranch, the WrongTransfer message from AddReturn is ignored entirely (opac/sci/sci-main.pl:81 only reads $success). The original in-transit branchtransfers row is orphaned and shows forever on the "Transfers to receive" report. Proposed approach: - Same transfer resolution as the SIP2 case (bug 42851 child): complete the original transfer recording the actual location, open a new transfer from the check-in branch to the original tobranch, and re-link holds. - Additionally surface a screen message so the patron/staff route the item to the exceptions bin rather than the normal returns shelf. Test plan: 1. Transfer an item from A to B (in transit). 2. Check it in at branch C via OPAC self check-in. 3. Before: branchtransfers row A->B stays open forever, no message. 4. After: transfer resolved + new C->B transfer created, exceptions-bin message shown. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42851 [Bug 42851] [OMNIBUS] Items left stuck in transit when checked in outside the staff returns page -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 40713] New: cookieConsent: key should have an expiration date
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40713 Bug ID: 40713 Summary: cookieConsent: key should have an expiration date Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Currently, the created localStorage key cookieConsent does not expire. This needs adjustment in view of following information: "The GDPR does not specify a fixed time limit for cookie expiry; instead, the duration must be proportionate to the cookie's purpose and never exceed 12 months according to the ePrivacy Directive, which requires consent renewal at least annually, and potentially more frequently based on your local Data Protection Authority's (DPA) guidelines, like the six-month recommendations from the Irish DPC and French CNIL." -- See e.g. https://gdpr.eu/cookies/ "If you use a cookie to store a record that a user has given consent to the use of cookies, you should ask the user to reaffirm their consent no longer than six months [*] after you have stored this consent state. (Footnote: While the legislation does not prescribe a specific lifespan for such cookies, based on a first-principles analysis by the DPC, we consider this to be the appropriate default outer timeframe for storing the user’s consent state. A controller would need to objectively and on a case-by-case basis justify storage for a longer period.)" -- Data Protection Commission [Ireland] Since localStorage has no expiration mechanism itself, we could simply add e.g. a unix timestamp as value here. Since the key now contains empty string and is tested for null to check status. This check would become: does the key exist and is its value still in future? A reject removes the key or clears it. Would it be possible to add the expiry period to a preference or enclosed in CookieConsentedJS somehow? -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 41722] New: Argument "" isn't numeric in numeric gt (>)... warnings in opac-detail.tt
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41722 Bug ID: 41722 Summary: Argument "" isn't numeric in numeric gt (>)... warnings in opac-detail.tt Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org The warning: [WARN] Argument "" isn't numeric in numeric gt (>) at /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-detail.tt line 1578. appears in the plack-opac-error.log. It is quite strange because warning only appears when opac-detail.pl is used for very first time to show record. To reproduce: 1a. Use a fresh KTD or 1b. edit opac-detail.tt (save an insignificant change, like add a space) and restart plack. 2. Observe plack-opac-error.log. 3. Go to any bibliographic record with items in OPAC., e.g. search for "Perl template toolkit". ==> Warnings should appear in plack-opac-error.log ==> (as many as there are items). 4. Restart plack 5. Back to OPAC and refresh view of bibliographic record. ==> No warnings appear. 5. Repeat 1b., 4. and 5. ==> Warnings appear. It seems that check of existens "item_level_holds" is needed before using it in IF condition, but I can't find why warning appers in log only once, not every time when "item_level_holds" is checked in IF. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 41756] New: RSS feed validation
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41756 Bug ID: 41756 Summary: RSS feed validation Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nicolas.hunstein(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When I perform a search in Koha, click on the RSS feed button, copy the generated string and then validate it on the page: https://www.rssboard.org/rss-validator/, I get the message: "It looks like this is a web page, not a feed. I looked for a feed associated with this page, but couldn't find one. Please enter the address of your feed to validate." Could this please be fixed? We suspect that there is a problem with the content type. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 41291] New: Add ability to have multiple self registration forms
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41291 Bug ID: 41291 Summary: Add ability to have multiple self registration forms Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries require multiple self registration forms with different visible fields and different required fields. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 40712] New: cookieConsent: Accepting essential cookies is unneeded/misleading
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40712 Bug ID: 40712 Summary: cookieConsent: Accepting essential cookies is unneeded/misleading Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org It feels a bit strange to Accept essential cookies. If you dont accept, they work anyway. And if you can accept, you would expect a reject either. But you cant reject them: they are essential and the code just uses them. If there are no additional non-essential cookies, it feels like the bar just needs a OK button to dismiss a message that there are only essential cookies. (This dismissal is not an accept.) "Under GDPR, essential (or strictly necessary) cookies are exempt from requiring user consent because they are fundamental for basic website functionality." -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 42854] New: OPAC self-checkout does not handle items that are in transit
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42854 Bug ID: 42854 Summary: OPAC self-checkout does not handle items that are in transit Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 42851 Target Milestone: --- Split off from bug 42851. opac/sco/sco-main.pl:180 calls AddReturn and only inspects $success; it does not consider that the item may be in transit. The transfer-on-checkout logic in C4/Circulation.pm:1754-1771 force-closes a transfer when an item is issued via the staff client, but the SCO path needs explicit, considered handling. Open questions to resolve on this bug: - Should we BLOCK self-checkout of an item that is in transit? - If we allow the checkout, we must still do something sensible with the transfer, because there is still an expectation the item eventually reaches the original destination branch. Test plan: 1. Transfer an item from A to B (in transit). 2. Attempt to self-check-out the item at branch C via OPAC SCO. 3. Define and verify the agreed behaviour (block, or allow + handle the open transfer). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42851 [Bug 42851] [OMNIBUS] Items left stuck in transit when checked in outside the staff returns page -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 42541] New: Add order and serial controls before moving items
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '26

03 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42541 Bug ID: 42541 Summary: Add order and serial controls before moving items Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Hello, Following on from patch 6532, I have added checks for orders and serials to confirm the move after a modal has been displayed if an order or serial number is linked. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 42779] New: Editing suggestion Fund defaults to None when field previously set.
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42779 Bug ID: 42779 Summary: Editing suggestion Fund defaults to None when field previously set. Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: sam.sowanick(a)corvallisoregon.gov QA Contact: testopia(a)bugs.koha-community.org When editing an existing suggestion the Fund field defaults to none even if fund was previously set. This can lead to removing fund information from the suggestion if not reset by the Staff Member. Testing 1) create suggestion and set fund. Save and note fund is set in Suggestions list page. 2) edit suggestion. Note fund field is defaulted away from the previously set fund. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18