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

Call for news: March 2020 Koha Newsletter
by Koha Newsletter 14 Mar '20

14 Mar '20

I'm collecting news for the March newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

String Freeze Notice
by Joy Nelson 13 Mar '20

13 Mar '20

Greetings! Just a quick note that string freeze will go into effect on 3/15/2020 for the maintenance branches. Maintenance releases scheduled for the 24th. -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

REST API not working in koha-testing-docker?
by dcook＠prosentient.com.au 13 Mar '20

13 Mar '20

Hi all, I'm finally getting around to playing with the REST API, but it's not quite working as expected. In koha-testing-docker (with the latest koha-testing-docker git repo and Docker images as of this writing), I'm getting the following in the browser: 1. 200 OK a. http://localhost:8080/api/v1/.html b. http://localhost:8080/api/v1/ or http://localhost:8080/api/v1/.json 2. 500 Internal Server error (with no obvious messages in the server logs other than a missing "Routing to a callback") a. http://localhost:8080/api/v1/items b. http://localhost:8080/api/v1/patrons c. http://localhost:8080/api/v1/libraries If I use "curl" or a Perl script, then I get a 401 error instead of a 500 error. (Although in Koha 19.11, I can get JSON results in either the browser or with curl for those endpoints, but that's a whole other matter.) RESTBasicAuth = 1 means I can use the API via curl, but still nothing via the browser. Which is fine I guess in practice but it's not really what you'd expect. I often use browser requests to test out GET requests for APIs. I don't really get how RESTPublicAPI works either. If it's disabled, it says '{"error":"Configuration prevents the usage of this endpoint by unprivileged users"}', but that doesn't seem accurate, since disabling that system preference blocks the /public APIs in general, right? Even if you use a privileged user, it still doesn't work. Actually, even with RESTPublicAPI enabled, I can't get the /public endpoints to work. I get errors like this '{"error":"Authorization failure. Missing required permission(s).","required_permissions":null}'. This email is getting a bit long and I think I have a million other API problems, so I might just work through one by one and open Bugzilla tickets as I go. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

5 10

Email::MesageID module and koha-testing-docker
by Jon Knight 12 Mar '20

12 Mar '20

I was going to do a spot of Koha "signing off" today whilst waiting for some other work to arrive and decided to try firing up the koha-testing-docker (https://gitlab.com/koha-community/koha-testing-docker.git) Docker image as the bug I was going to test needed command line interaction (for web based testing I usually use the sandboxes as its quicker and easier). Unfortunately I've come unstuck because I keep getting: koha_1 | Something went wrong rebuilding biblio indexes for kohadev koha_1 | Can't locate Email/MessageID.pm in @INC (you may need to install the Email::MessageID module) (@INC contains: /kohadevbox/koha /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base /var/lib/koha/kohadev/plugins) at /kohadevbox/koha/Koha/Email.pm line 22. koha_1 | BEGIN failed--compilation aborted at /kohadevbox/koha/Koha/Email.pm line 22. koha_1 | Compilation failed in require at /kohadevbox/koha/C4/Letters.pm line 38. ...followed by lots of similar lines and a failed Koha install. I've tried pulling a fresh koha-testing-docker git install onto my laptop and setting/exporting the CPAN=1 environment variable to get CPAN dependencies updated but it still happens. I can `kshell` into the docker container and install the module manually, but of course its blown away the next time I do a `ku` or `kp` command to bring up a new container instance. Kind of puts a dampener on doing sign-offs, so does anyone else have the same issue and/or any hints on how to fix it? Jon

2 2

Koha plugin development reference, Reg;
by Anuj Singh 11 Mar '20

11 Mar '20

Dear Koha Developers, Please suggest me how can I develop koha plugin. I'm very new in Koha Development, please help me to start from the beginning. I tried to search on https://wiki.koha-community.org/wiki/Koha_plugin_development_reference URL but sufficient documentation is not available. Also, I request to suggest me some useful resources and learning material for the same. Thanks & Regards --Anuj

3 2

hackfest cancelled
by Paul Poulain 10 Mar '20

10 Mar '20

Hello all, In case you were still wondering "should I go to the hackfest this year ?", I'll answer for you : I've decided to cancel the hackfest. Too sad, but everyone is better at home, taking care of his family. See you soon !!! -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

4 3

Javascript errors in OPAC
by dcook＠prosentient.com.au 05 Mar '20

05 Mar '20

Hi all (and especially Owen), I'm noticing some odd Javascript errors in the OPAC in 19.11 and master. Steps to reproduce: 1. Go to the OPAC and open the F12 dev tools. 2. Click on "Log in to your account" 3. Note the following in your console logs jquery-3.4.1.min_19.1200030.js:2 Uncaught Error: Syntax error, unrecognized expression: /cgi-bin/koha/opac-user.pl at Function.se.error (jquery-3.4.1.min_19.1200030.js:2) at se.tokenize (jquery-3.4.1.min_19.1200030.js:2) at se.select (jquery-3.4.1.min_19.1200030.js:2) at Function.se (jquery-3.4.1.min_19.1200030.js:2) at Function.s.find (jquery-migrate-3.1.0.min_19.1200030.js:2) at k.fn.init.find (jquery-3.4.1.min_19.1200030.js:2) at s.fn.init.k.fn.init (jquery-3.4.1.min_19.1200030.js:2) at new s.fn.init (jquery-migrate-3.1.0.min_19.1200030.js:2) at k (jquery-3.4.1.min_19.1200030.js:2) at HTMLAnchorElement.<anonymous> (bootstrap.min_19.1200030.js:6) Using the Chrome tools, I was able to pretty print the Javascript, so now I see the following: Uncaught Error: Syntax error, unrecognized expression: /cgi-bin/koha/opac-user.pl at Function.se.error (jquery-3.4.1.min_19.1200030.js:formatted:546) at se.tokenize (jquery-3.4.1.min_19.1200030.js:formatted:969) at se.select (jquery-3.4.1.min_19.1200030.js:formatted:1024) at Function.se (jquery-3.4.1.min_19.1200030.js:formatted:289) at Function.s.find (jquery-migrate-3.1.0.min_19.1200030.js:2) at k.fn.init.find (jquery-3.4.1.min_19.1200030.js:formatted:1138) at s.fn.init.k.fn.init (jquery-3.4.1.min_19.1200030.js:formatted:1159) at new s.fn.init (jquery-migrate-3.1.0.min_19.1200030.js:2) at k (jquery-3.4.1.min_19.1200030.js:formatted:50) at HTMLAnchorElement.<anonymous> (bootstrap.min_19.1200030.js:formatted:535) It kind of looks to me like some sort of incompatibility between Bootstrap 2.3.1 and Jquery 3.4.1? I've put breakpoints up and down this code but it's not jumping out at me exactly what's happening except that maybe it's trying to use the href attribute as a selector and it's not working. but why it would even try in the first place confuses me. It looks like a Bootstrap-level thing, which is why I'm thinking maybe older versions of Jquery worked a bit differently? Anyway I've already stayed way too late at work today. Maybe someone smarter than me can figure this one out. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 3

Holds Queue vs Holds to Pull
by dcook＠prosentient.com.au 04 Mar '20

04 Mar '20

Hi all, What is the purpose of the "Holds Queue" page? As far as I can tell, it duplicates "Holds to Pull" but requires a separate cronjob and extra database tables and so on. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 3

Re: [Koha-devel] Minimal docker images for Koha
by Agustin Moyano 03 Mar '20

03 Mar '20

Sorry.. seems I send it only to Julian.. here goes again El sáb., 29 de febrero de 2020 19:15, Agustin Moyano <agustinmoyano(a)theke.io> escribió: > Hi Julian, great work!! > > I've also been working (interruptedly) for a couple of months on a docker > version of Koha. > > I focused on having as soon as possible a fully functional docker version > of Koha, and didn't worry too much about doing things the docker way.. It's > comforting to know you weren't tempted by de dark side of the force! > > I thought of having first a production ready docker much like > koha-testing-docker, and later split services into different containers. > That's why I really, really loved your implementation of plack.psgi. URL > rewrite in psgi brings independence day from Apache much closer! \o/. > > Just some thoughts: > > - Should you base your image on Debian buster? on > https://wiki.koha-community.org/wiki/Koha_on_Debian says "Note: Debian > 10 (Buster) is currently not recommended or supported, work is in progress > to rectify this situation." > - Even if there's no need for reverse proxy, I wouldn't discard having > one on a separate container.. web servers like apache or nginx deal much > better with attacks than exposing the service on it's own (First hand > experience with a Java/Tomcat service I made once) ( > https://security.stackexchange.com/questions/209111/security-benefits-of-re… > ) > > But overall, great job! > > PS: If you'd like to take a peek of what I've done, here's the repo: > https://gitlab.com/thekesolutions/koha-docker >

4 7

Saying farewell to QueryParser
by Renvoize, Martin 03 Mar '20

03 Mar '20

Hi All, As discussed at the development meeting on the 19th February <https://meetings.koha-community.org/2020/development_irc_meeting_19_februar…> we have decided to remove the QueryParser option and code from Koha. This decision was not taken lightly, but with the move towards Elasticsearch and the lack of follow-through support for continued bug fixing and improvements in the QueryParser code we decided to reduce out maintenance debt and remove it. We used HEA to try to ascertain if anyone had been using the option and it appears to have little to zero adoption (and at the time of writing, had a number of bad bugs which meant using it was advised against for some time). Jonathan D has worked hard to produce a patch quickly to do this work and I intend to push this later today to reduce the risk of repetitive rebase requirements. So, join me in saying farewell to QueryParser, a nice idea never fully realised. Many thanks as ever to the koha development team, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 1