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

[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

[Bug 34989] New: Subscription cannot be added if a control field is set up in "Additional Fields" parameter
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34989 Bug ID: 34989 Summary: Subscription cannot be added if a control field is set up in "Additional Fields" parameter Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: anke.bruns(a)gwdg.de QA Contact: testopia(a)bugs.koha-community.org Subscriptions can't be created because of an HTTP 500 and the following message in the plack error log: "Control fields (generally, just tags below 010) do not have subfields, use data() at /usr/share/koha/lib/Koha/Object/Mixin/AdditionalFields.pm line 68." The workaround by Joubu (many thanks!) in the Koha chat was to look whether in Administration > Additional fields > Table 'subscription' (/cgi-bin/koha/admin/additional-fields.pl?tablename=subscription) a MARC field was present that was a control field (ie. without $ field/subfield separator). We indeed had a 001 configured there with MARC field mode "Get value from MARC record" and Searchable=Yes Removing this solved the problem, but perhaps subscriptions should also work if a control field is configured in the place mentioned above? Another thing is that we are not completely sure if the error was produced when we upgraded from 22.05 or if it was present there as well with the additional field set. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 10047] Cataloguing search maybe useless?
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10047 Catrina Berka <catrina(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |catrina(a)bywatersolutions.co | |m -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39974] New: "OpacMoreSearches" HTML customization generates invalid HTML
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '25

13 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39974 Bug ID: 39974 Summary: "OpacMoreSearches" HTML customization generates invalid HTML Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org OpacMoreSearches is supposed to be one or more <li> elements. However, when you save it in HTML customizations, it'll add a <ul></ul> tags around the <li> elements you define. Moreover, when you look at the HTML, you notice how OpacMoreSearches injects a <div> into a <ul>: <ul class="nav" id="moresearches"> <li class="nav-item"></li> <div id="OpacMoreSearches"> <div class="default_item"> <div class="default_body"> <ul> <li><a>New content</a></li> </ul> </div> </div> </div> </ul> While a lot of places where we use HTML customizations can validly inject a <div>, this isn't one of them. We might want to add a way for HTML customizations to just inject content directly without using wrappers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3