August 2022 - Koha-devel - lists.koha-community.org

How to make self-referential URLs in Koha
by dcook＠prosentient.com.au 30 Jan '23

30 Jan '23

Hi all, With some recent code, I've been using creating self-referential URL in Koha using CGI->url(), and passing it as a value. With CGI, the URL is correct (ie starting with /cgi-bin/koha). With Plack, it's not, because the OPAC is mounted as "/opac". I worked around this by rewriting the self-referential URL in my code, but I was wondering if anyone else had any thoughts on this. I've noticed there are a few places in Koha where we use CGI->url() and I'm guessing we may have unexpected bugs in Plack-enabled Koha as a result. Of course, one workaround would be to have /opac and /intranet aliases or URL rewriting in Apache, so that the self-referential URLs created by Plack still end up resolving. I wonder if that's the easiest path forward. In the past, I have wondered if we could get rid of "/cgi-bin/koha" as a path prefix all together (especially as cgi-bin scares security tools), but it's so deeply embedded in Koha at this point that it seems a huge task to replace it. Anyway, just throwing that out there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

6 8

Koha releases are available 🎁
by Mason James 16 Jan '23

16 Jan '23

kia ora community, the latest Koha packages and tarballs are ready release notes are here... https://koha-community.org/koha-21-11-03-released https://koha-community.org/koha-21-05-11-released https://koha-community.org/koha-20-11-15-released https://koha-community.org/koha-19-11-26-released cheers, Mason

2 2

Enable libraries to moderate OPAC self-registrations
by Alex Buckley 14 Sep '22

14 Sep '22

Kia ora/Hello Koha community, I am currently working on reviving bug 25090 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25090> ( Moderate OPAC self-registrations before a patron account is created ). *New proposed functionality:* Step 1: The library enables both the new 'PatronSelfRegistrationModeration' syspref and the existing 'OpacResetPassword'syspref. Step 2: When a user submits an OPAC self-registration their Koha patron account is not created immediately - i.e. they cannot yet log into the OPAC. Step 3: A pending registration link appears at the bottom of the staff client home page (like what's currently done with new purchase suggestions, or OPAC patron modification requests). Step 4: Librarians can click on the link to go to a page to approve or decline the registration. Step 4a: If approved the user is sent an email notice, containing their Koha username and an OPAC reset password link. Step 4b: If declined the user is sent a different email notice. *The rationale for adding this feature:* You can currently limit the circulation of self-registered patrons - by using the PatronSelfRegistrationDefaultCategory syspref and creating circulation rule(s) for that category. However, users only need an OPAC login (without the ability to circulate) to access electronic content providers (integrated with Koha via STunnel/SIP2). Some electronic content providers charge libraries based on their usage. Meaning it might not be optimal having anyone from around the world self-registering for a library OPAC login and accessing electronic content from some providers, therefore, incurring extra costs for the library. Bug 25090 was originally developed in the early days of the pandemic to ensure new self-registering OPAC users accessing 3rd party databases were coming from acceptable locations i.e. they were members of the organisation the library is in. More details can be found here: https://www.catalyst.net.nz/blog/mental-health-education-resource-library-n… *Questions I would like to hear your thoughts on please:* Q1: Are you in favour of this as a new feature in Koha? Q2: Would you prefer a new database table be added for self-registrations awaiting approval, or should I use the borrowers_modifications table - as is used by OPAC patron modification requests? Q3: How would you envisage this self-registration moderation feature fitting in with the existing PatronSelfRegistrationVerifyByEmailand PatronSelfRegistrationDefaultCategory sysprefs? Any thoughts much appreciated. Kind regards, Alex

5 16

Koha Community Newsletter: August 2022
by Koha Newsletter 29 Aug '22

29 Aug '22

The Koha Community Newsletter for August 2022 is here: https://koha-community.org/koha-community-newsletter-august-2022/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Difficulties with JSON::Validator after upgrading to 22.05
by Philippe Blouin 26 Aug '22

26 Aug '22

Hi folks! Got a really weird error in my logs right now: "is_bool" is not exported by the JSON::Validator::Util module "is_num" is not exported by the JSON::Validator::Util module "str2data" is not exported by theJSON::Validator::Util module Can't continue after import errors at /usr/share/perl5/JSON/Validator/Schema.pm line 7. BEGIN failed--compilation aborted at /usr/share/perl5/JSON/Validator/Schema.pm line 7. Compilation failed in require at /usr/share/perl5/Mojo/Base.pm line 134. BEGIN failed--compilation aborted at /usr/share/perl5/JSON/Validator/Schema/Draft4.pm line 2. Compilation failed in require at /usr/share/perl5/Mojo/Base.pm line 134. BEGIN failed--compilation aborted at /usr/share/perl5/JSON/Validator/Schema/OpenAPIv2.pm line 2. Compilation failed in require at /inlibro/git/koha-v22-dev-blou/Koha/REST/V1.pm line 25. BEGIN failed--compilation aborted at /inlibro/git/koha-v22-dev-blou/Koha/REST/V1.pm line 25. Compilation failed in require at (eval 22) line 1. Which ruins most table displays. The error is weird in many ways, including the fact that /usr/share/perl5/JSON/Validator/Util.pm DOES export is_bool and friend in its header. cpan tells me I have the latest version, etc... I have Ubuntu 20.04, which I'm upgrading now to 22.04, but I don't expect much to change there considering the error. Any suggestion? Best regards, -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

2 3

Re: [Koha-devel] Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 23 Aug '22

23 Aug '22

Awesome! Thanks, Kyle! I would love to get this into 22.11. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Kyle Hall <kyle(a)bywatersolutions.com> Sent: Friday, 19 August 2022 1:14 AM To: dcook(a)prosentient.com.au Cc: koha-devel(a)lists.koha-community.org; Tomas Cohen Arazi <tomascohen(a)theke.io>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Mojolicious controllers for Koha plugins Excellent! Tested and signed off on everything :) Kyle On Thu, Aug 18, 2022 at 3:04 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Thanks, Kyle! Leveraging some past work, I was able to put something together fairly quickly. I’ve posted it to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 It has two dependent bug reports but I’ve posted patches for them too, and they’re fairly straightforward. It should be very easy to test, so hopefully you can have a look and let me know what you think. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Kyle Hall <kyle(a)bywatersolutions.com <mailto:kyle@bywatersolutions.com> > Sent: Tuesday, 16 August 2022 9:27 PM To: dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> Cc: koha-devel(a)lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> ; Tomas Cohen Arazi <tomascohen(a)theke.io <mailto:tomascohen@theke.io> >; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com <mailto:martin.renvoize@ptfs-europe.com> > Subject: Re: Mojolicious controllers for Koha plugins That sounds great to me David! I'll 100% assist you with testing and qa! On Tue, Aug 16, 2022 at 3:42 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it’s probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It’s the reason Koha uses CGI instead of Plack for export.pl <http://export.pl> While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can’t do that for Koha plugins themselves. This is a topic that I’ve touched on before, and there are challenges when it comes to Authentication and Templates, but they’re solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 “Build Mojolicious controller replacement for export.pl <http://export.pl> ” https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 “Build Mojolicious controller replacement for tools-home.pl <http://tools-home.pl> ” We could just start by supporting “tool” and “report” with the Mojolicious controllers, and that would just mean plugins-home.pl <http://plugins-home.pl> detecting that there is Mojolicious support in that plugin, and then building a URL to “/staff/plugins/run” instead of “/cgi-bin/koha/plugins/run.pl <http://run.pl> ” for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I’d be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we’d also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too… Anyways, please give it some consideration, and ask me if you have any questions. I’ll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations… David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha? -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha?

2 2

Re: [Koha-devel] [Koha] Circulation Rules: Parent and Child Item Type
by Ms. Naveen Ali 22 Aug '22

22 Aug '22

Thank you very much Caroline for the response and Katrin for the confirmation. Is it possible to batch update multiple circulation rules of one library? The problem I am facing is that I have around 60+ item types for which lending rule (with hard due date) has to be updated every semester. I just need to update the hard due date. It would be very convenient if I could do it in one go. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi. ----- Original Message ----- From: "Katrin Fischer" <katrin.fischer.83(a)web.de> To: koha(a)lists.katipo.co.nz Sent: Thursday, 18 August, 2022 3:58:03 PM Subject: Re: [Koha] Circulation Rules: Parent and Child Item Type > > As far as I know, the rule for the parent type only applies to > children for the "checkouts allowed" rule. This may have changed > since, but when the parent/child item types were introduced, it was > like this. I believe this is still correct! Katrin _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Re: [Koha-devel] Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 18 Aug '22

18 Aug '22

Thanks, Kyle! Leveraging some past work, I was able to put something together fairly quickly. I’ve posted it to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 It has two dependent bug reports but I’ve posted patches for them too, and they’re fairly straightforward. It should be very easy to test, so hopefully you can have a look and let me know what you think. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Kyle Hall <kyle(a)bywatersolutions.com> Sent: Tuesday, 16 August 2022 9:27 PM To: dcook(a)prosentient.com.au Cc: koha-devel(a)lists.koha-community.org; Tomas Cohen Arazi <tomascohen(a)theke.io>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Mojolicious controllers for Koha plugins That sounds great to me David! I'll 100% assist you with testing and qa! On Tue, Aug 16, 2022 at 3:42 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it’s probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It’s the reason Koha uses CGI instead of Plack for export.pl <http://export.pl> While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can’t do that for Koha plugins themselves. This is a topic that I’ve touched on before, and there are challenges when it comes to Authentication and Templates, but they’re solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 “Build Mojolicious controller replacement for export.pl <http://export.pl> ” https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 “Build Mojolicious controller replacement for tools-home.pl <http://tools-home.pl> ” We could just start by supporting “tool” and “report” with the Mojolicious controllers, and that would just mean plugins-home.pl <http://plugins-home.pl> detecting that there is Mojolicious support in that plugin, and then building a URL to “/staff/plugins/run” instead of “/cgi-bin/koha/plugins/run.pl <http://run.pl> ” for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I’d be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we’d also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too… Anyways, please give it some consideration, and ask me if you have any questions. I’ll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations… David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha?

1 0

Re: [Koha-devel] Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 17 Aug '22

17 Aug '22

Thanks, Kyle! I’ll look at updating the patches from Bug 28325 and post new work for this at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Kyle Hall <kyle(a)bywatersolutions.com> Sent: Tuesday, 16 August 2022 9:27 PM To: dcook(a)prosentient.com.au Cc: koha-devel(a)lists.koha-community.org; Tomas Cohen Arazi <tomascohen(a)theke.io>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Mojolicious controllers for Koha plugins That sounds great to me David! I'll 100% assist you with testing and qa! On Tue, Aug 16, 2022 at 3:42 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it’s probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It’s the reason Koha uses CGI instead of Plack for export.pl <http://export.pl> While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can’t do that for Koha plugins themselves. This is a topic that I’ve touched on before, and there are challenges when it comes to Authentication and Templates, but they’re solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 “Build Mojolicious controller replacement for export.pl <http://export.pl> ” https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 “Build Mojolicious controller replacement for tools-home.pl <http://tools-home.pl> ” We could just start by supporting “tool” and “report” with the Mojolicious controllers, and that would just mean plugins-home.pl <http://plugins-home.pl> detecting that there is Mojolicious support in that plugin, and then building a URL to “/staff/plugins/run” instead of “/cgi-bin/koha/plugins/run.pl <http://run.pl> ” for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I’d be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we’d also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too… Anyways, please give it some consideration, and ask me if you have any questions. I’ll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations… David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha?

1 0

Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 16 Aug '22

16 Aug '22

Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it's probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It's the reason Koha uses CGI instead of Plack for export.pl While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can't do that for Koha plugins themselves. This is a topic that I've touched on before, and there are challenges when it comes to Authentication and Templates, but they're solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 "Build Mojolicious controller replacement for export.pl" https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 "Build Mojolicious controller replacement for tools-home.pl" We could just start by supporting "tool" and "report" with the Mojolicious controllers, and that would just mean plugins-home.pl detecting that there is Mojolicious support in that plugin, and then building a URL to "/staff/plugins/run" instead of "/cgi-bin/koha/plugins/run.pl" for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I'd be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we'd also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too. Anyways, please give it some consideration, and ask me if you have any questions. I'll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0