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

[Bug 38793] New: Transfer silently not canceled when TransfersBlockCirc = "don't block" and AutomaticConfirmTransfer = "do automatically confirm"
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38793 Bug ID: 38793 Summary: Transfer silently not canceled when TransfersBlockCirc = "don't block" and AutomaticConfirmTransfer = "do automatically confirm" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 0. Set TransfersBlockCirc = "don't block" AutomaticConfirmTransfer = "do automatically confirm" 1. Find or create an item that belongs to a branch other than the logged-in branch Like 39999000012118 in test data 2. Check in the item - this should trigger a Return to Home transfer 3. Click OK on the modal to confirm the transfer 4. Check in that item again 5. Cancel the transfer 6. Open the bib record for that item in a new tab 7. It's still in transit (that's wrong!) 8. Check in that item again 9. It still offers to cancel. (confirming the previous cancel attempt didn't work) Logs don't show any error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 21976] New: koha-reset-passwd must call Koha::AuthUtils::generate_password to deal with password restrictions
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21976 Bug ID: 21976 Summary: koha-reset-passwd must call Koha::AuthUtils::generate_password to deal with password restrictions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 18298 Like minPasswordLength and RequireStrongPassword Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18298 [Bug 18298] Allow enforcing password complexity -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 40521] New: Allow partial editing of fixed/control fields with MARC modification templates
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40521 Bug ID: 40521 Summary: Allow partial editing of fixed/control fields with MARC modification templates Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently you can only replace an entire string of a fixed length field using MARC modification templates. It would be a great enhancement to be able to update specific positions. For example, if I need to update the place of publication in the 008, I only want to change positions 15-17, not the whole string. Likewise, if in the leader/000 I need to change the position 6 type of record, I don't want to have to replace the entire string. As it is now, users have to the export the records to something like MARCedit, do the work, and then overlay. It would be wonderful to be able to do this all cataloging without leaving Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40283] New: Accessibility of the status message in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40283 Bug ID: 40283 Summary: Accessibility of the status message in the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: nina.martinez(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org The intent of this success criterion is to make users aware of important changes in content that are not given focus, and to do so in a way that doesn't unnecessarily interrupt their work. https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html To improve this, we can add role=”status” or role=”alert” in the message tag. Using the status role from the ARIA specification to notify Assistive Technologies (AT) when content has been updated with information about the user's or application's status. https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA22 The purpose of the role=”alert” is to notify Assistive Technologies (AT) when an input error occurs. The role=”alert”attribute makes it possible for an AT (such as a screen reader) to be notified when error messages -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 32306] New: Hold modifications don't log correctly
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32306 Bug ID: 32306 Summary: Hold modifications don't log correctly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org When one modifies holds from records holds page, these changes don't log into action_logs table correctly. Instead holds data before modifications is stored to action_logs. To test: 1. Find hold to modify. 2. If possible, locate this hold from action_logs table: SELECT * FROM action_logs WHERE module = "HOLDS" AND object = <reserve_id>; 3. Modify hold, change its pickup library from A to B. 4. Save changes. 5. Take a look at action_logs table. => Modification is saved, but holds pickup library is still A. 6. Modify hold again, e.g add expiration date. 7. Save. => Expiration date is empty, but pickup library is now B. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 31610] New: When creating a guarantee, patron messaging preferences should be copied to this account from the category
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31610 Bug ID: 31610 Summary: When creating a guarantee, patron messaging preferences should be copied to this account from the category Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When creating a guarantee, patron messaging preferences should be copied to this account from the category. Steps: Have a guarantor. Create a guarantee. Koha will use the CHILD patron category to assign this guarantee, but will not copy over the message preferences from this CHILD patron category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 25936] New: Notify users if their password has changed
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25936 Bug ID: 25936 Summary: Notify users if their password has changed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We should email/SMS users if their password has changed. We shouldn't include any information about the old or new password, but just alert them that it has been changed. This is useful in the event that someone has compromised an account and changed the password. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 36990] New: Move MarcEdit tutorials out of the manual, into the wiki
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36990 Bug ID: 36990 Summary: Move MarcEdit tutorials out of the manual, into the wiki 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In one of the docs meeting (april 2024?), we decided that the Koha manual should be used to describe how to use Koha, and not how to use other software. Integration examples should be in the Koha wiki. As the MarcEdit section at the end of the cataloging chapter (https://koha-community.org/manual/latest/en/html/cataloging.html#handling-o…) not only describes how to use another software, it is also possible wildly out of date >This tutorial was written with MARCEdit version 5.2.3769.41641 on Windows XP, instructions may be different if your version or operating system is different. MarcEdit is now at version 7 and Windows is... 11? (sorry, I don't use windows or follow its development) This should be moved to the wiki as an example of MarcEdit use with Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 39308] New: No space between preffered name and middle name in some places
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39308 Bug ID: 39308 Summary: No space between preffered name and middle name in some places Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons 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 a middle name. 2. ON the checkout page or details page notice it displays like this: 'EdnaMiddleName Acosta' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 38979] New: Standardize word spacing for Cardnumber and Borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38979 Bug ID: 38979 Summary: Standardize word spacing for Cardnumber and Borrowernumber 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org A discerning librarian of mine pointed out that the moremember.pl page shows "Card number" and "Borrowernumber". They asked for a space to be added to make the latter "Borrower number", which honestly makes a lot of sense. While I think that's a good starting point, I figured I'd raise this issue to cover all the different instances for both. $ grep -R "Card number" koha-tmpl/* | wc -l 36 $ grep -R "Cardnumber" koha-tmpl/* | wc -l 7 $ grep -R "Borrowernumber" koha-tmpl/* | wc -l 11 $ grep -R "Borrower number" koha-tmpl/* | wc -l 1 Chances are that there are more instances with lower cased initial letters, but cardnumber and borrowernumber are valid in links... It would probably be wise to add a coding guideline for this as well. -- You are receiving this mail because: You are watching all bug changes.

1 18