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

[Bug 36115] New: Improve documentation for Return-Path (branches.branchreturnpath)
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36115 Bug ID: 36115 Summary: Improve documentation for Return-Path (branches.branchreturnpath) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org I am not sure if the code or the documentation is the problem here, but let's start with the documentation. For reference, the manual says this today: Email: the email address field is not required, but it should be filled for every library in your system - Note: Be sure to enter a library email address to make sure that notices are sent to and from the right address - Note: If no email address is entered here, the address in the KohaAdminEmailAddress system preference will be used to send notices from this library Reply-To: you can enter a different ‘Reply-To’ email address. This is the email address that all replies will go to. - Note: If no email address is entered here, the address in the ReplytoDefault system preference will be used to receive replies to this library Return-Path: you can enter a different ‘Return-Path’ email address. This is the email address that all bounced messages will go to. - Note: If no email address is entered here, the address in the ReturnpathDefault system preference will be used to receive bounced messages from this library. https://koha-community.org/manual/latest/en/html/administration.html#adding… Mu scenario is as follows: We host Koha for a number of libraries that want to send messages to their patrons by email. For some libraries we can't send email through their SMTP for different reasons. So we set up a noreply address with a domain that we control, so that we can use that as the sender of the emails, and we can do our best to set up SPF, DKIM etc for it, so it won't be seen as spam by services such as Gmail. Based on the description above, I set it up like this: Email = noreply Reply-To = real library email Return-Path = real library email But it turns out that when postfix was processing the email, and passing it on to our SMTP server, it was seeing the "real library email" from the Return-Path setting as the "from" address, not the "noreply" address that we wanted it to see. So the question is: - Is the code wrong in using the Return-Path address as the "from" address? - Or is the documentation wrong in saying that the Return-Path is just for bounced messages? See also: Bug 28729 - Return-path header not set in emails -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 36273] New: ILL - Refactor $op in ill-requests.pl
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36273 Bug ID: 36273 Summary: ILL - Refactor $op in ill-requests.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: pedro.amorim(a)ptfs-europe.com Depends on: 36241, 36243, 36245, 36249 With bug 34478, presenting a form page should be a GET request without 'cud-' in the op URL parameter. Additionally, a form that creates, updates or deletes some object should be a POST with the 'cud-' prefix. ill-requests.pl did not do this distinction originally, and still doesn't. It instead works around 'cud-' in the $op to preserve existing functionality. It should be refactored to better distinguish between a GET $op and a POST $op. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36241 [Bug 36241] ILL Batches are broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36243 [Bug 36243] ILL "Edit request" action is broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36245 [Bug 36245] ILL - Custom backend form action is broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36249 [Bug 36249] ILL - "Request from partners" action is broken -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 20678] New: Save draft records without committing them to the catalogue
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20678 Bug ID: 20678 Summary: Save draft records without committing them to the catalogue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl One of our clients has requested the functionality to be able to save a MARC record as a draft so they can return to continue cataloguing it later. This will be achieved by saving the record to the 'reservoir' in much the same way that staged records are stored in the 'import_*' tables but not in the biblio table. The functionality has been achieved in the first patch I will attach, and unit tests for this will come later. -- You are receiving this mail because: You are watching all bug changes.

1 54

[Bug 37715] New: It should be possible to enable/disable each authentication method on the OPAC and staff client
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37715 Bug ID: 37715 Summary: It should be possible to enable/disable each authentication method on the OPAC and staff client 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When setting up identity provides (OAuth/OpenID) you can enable or disable the provider for the OPAC/Staff client We have the preferences OPACShibOnly and staffShibOnly which will limit everything to Shib It would be nice to instead have a switch for each: OpacEnableLocalLogin OpacEnableCASLogin OpacEnableShibLogin OpacEnableLDAPLogin and staff equivalents additionally - when using identity providers they always add the line: <p>If you do not have an external account, but do have a local account, you can still log in: </p> This needs a class at minimum, but should likely be removed and allow the library to specify the text in loginInstructions html customization -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 11583] Add WYSIWYG editor for HTML notices/letters
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '25

14 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11583 --- Comment #28 from David Cook <dcook(a)prosentient.com.au> --- Bumped into an issue with the WELCOME notice. The following line: <a href='[% Koha.Preference('OPACBaseURL') %]'>catalog</a> Gets turned into the following: <a href="/cgi-bin/koha/tools/<span class="tmpl-tag template" contenteditable="false" data-original="IEtvaGEuUHJlZmVyZW5jZSgnT1BBQ0Jhc2VVUkwnKSA=">[% Koha.Preference(" opacbaseurl="" span="">catalog</a> It's because with the WYSIWYG I convert [% %] and <<>> syntax into spans. so they're rendered in the WYSIWYG as HTML but stored as plain text. But that doesn't work when embedding the [% %] syntax in the HTML. -- Of course, that might be a reasonable limitation. Just noting it for now. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31498] New: Allow for custom primary contact method values
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31498 Bug ID: 31498 Summary: Allow for custom primary contact method values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 The values in the primary_contact_method dropdown on patron creation/edit are hard coded. Some libraries would like to include custom options in that dropdown. Maybe via Authorized Values? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 36185] New: Add option to enforce time limit on suspended holds
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36185 Bug ID: 36185 Summary: Add option to enforce time limit on suspended holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently when you suspend a hold in Koha, you have the choice of adding a suspend until date. If the date is left blank the hold is suspended indefinitely, even if DefaultHoldExpiration system preferences are configured. When the hold is unsuspended after the hold expiration date, it is canceled. Being able to limit the amount of time a hold can be suspended would make the holds timeline clearer to patrons. It would also make determining how many copies are needed to fill holds. This could take the form of a system preference that adds the date limitation into the staff interface. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 14182] Suspended holds should show in separate list
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14182 Michelle Spinney <mspinney(a)clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mspinney(a)clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14182] Suspended holds should show in separate list
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14182 Brendan Lawlor <blawlor(a)clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blawlor(a)clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39245] New: Preferred name should give option to replace more than first name
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39245 Bug ID: 39245 Summary: Preferred name should give option to replace more than first name Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have a patron, for example only: Johnathan David Smith. He goes by JD. But the preferred name only replaces the first name. There should be an option to also exclude the middle name. Right now the preferred name shows the patron name as JD David Smith. Should only show JD Smith. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8