<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 10244 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 198, Issue 2<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Is the support of multiple LDAP servers in koha-conf.xml<br> planned? (Uwe Dierolf)<br> 2. iTiva messaging (Nick Clemens)<br> 3. Re: Need help with bug 26247 (Michael Hafen (TECH))<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 3 May 2022 16:08:02 +0200<br>From: Uwe Dierolf <uwe.dierolf@kit.edu><br>To: koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] Is the support of multiple LDAP servers in<br> koha-conf.xml planned?<br>Message-ID: <20220503140802.GM6785@ubka.uni-karlsruhe.de><br>Content-Type: text/plain; charset=iso-8859-1<br><br>Hi all,<br><br>at the moment C4::Auth_with_ldap supports only one ldap-server.<br>If the authentication against this ldap-server fails, koha tries to<br>use the credentials to authenticate by using the internal koha accounts.<br><br>In some cases it would be practical if we could use multiple blocks like so in the koha-conf.xml:<br><br> <ldapserver id="ldapserver-1" ...><br> </ldapserver><br> ....<br> <ldapserver id="ldapserver-2" ...><br> </ldapserver><br><br>and if koha would try to authenticate with the given credentials using<br>all ldapservers and at the end the internal koha accounts.<br><br>Best regards, Uwe <br><br>--------------------------------------------------------------------------<br>Uwe Dierolf<br>Karlsruher Institut für Technologie (KIT)<br>KIT-Bibliothek<br>Telefon: +49 721 608-46076<br>--------------------------------------------------------------------------<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 3 May 2022 10:33:26 -0400<br>From: Nick Clemens <nick@bywatersolutions.com><br>To: Koha Devel <koha-devel@lists.koha-community.org>, Koha<br> <koha@lists.katipo.co.nz><br>Subject: [Koha-devel] iTiva messaging<br>Message-ID:<br> <CAA_eX3PU5fxmYqO1Wv9As8n-JGYAYAsJ7WWScixG9LKht6f-fQ@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi All,<br><br>We just wanted to get a sense of how widespread use of iTiva is? We were<br>considering that it may be better as a plugin than a script within Koha<br><br>Thanks for any feedback,<br>Nick<br>-- <br>Nick Clemens<br>ByWater Solutions<br>bywatersolutions.com<br>Phone: (888) 900-8944<br>Pronouns: (he/him/his)<br>Timezone: Eastern<br>Follow us:<br><https://www.facebook.com/ByWaterSolutions/><br><https://www.instagram.com/bywatersolutions/><br><https://www.youtube.com/user/bywatersolutions><br><https://twitter.com/ByWaterSolution><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220503/22a55120/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 3 May 2022 10:06:28 -0600<br>From: "Michael Hafen (TECH)" <michael.hafen@washk12.org><br>To: Mark Alexander <marka@pobox.com><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Need help with bug 26247<br>Message-ID:<br> <CAAh7Ud=jxYNVsR637vq_CvXnexV7Yt22J-7Fs-gkNxeigHYMOA@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>On Mon, May 2, 2022 at 6:18 PM Mark Alexander <marka@pobox.com> wrote:<br><br>> Excerpts from Michael Hafen (TECH)'s message of 2022-05-02 15:12:41 -0600:<br>> > $(document).ready(function() {<br>> > $("#header_search #catalog_search input[name='q']").val("");<br>> > });<br>> ><br>> > in the IntranetUserJS system preference )<br>><br>> This doesn't work. The barcode is still in the searchbox after<br>> submitting the form.<br>><br>><br>That's weird. I have a vm running master as a dev install. I just tried<br>that bit of javascript in the syspref, and it worked for me. How<br>frustrating.<br>Have you tried a different browser?<br><br>-- <br>Michael Hafen<br>Washington County School District Technology Department<br>Systems Analyst<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220503/c6a82af1/attachment-0001.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 198, Issue 2<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>