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

Give a try to RabbitMQ (background jobs rewrite) - POC!
by Jonathan Druart 26 Feb '20

26 Feb '20

Hi devs, I have submited a proof of concept (POC) on bug 22417 (Delegate background jobs execution). The idea would be to isolate our background jobs code (the one in the .pl) into module then use RabbitMQ to process them. More stuffs on the bug! https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 Cheers, Jonathan

4 4

mariadb versions and koha
by Laurent Ducos 06 Nov '19

06 Nov '19

Hello We are currently using version 10.0 of mariadb with koha. We are planning a upgrade. Have you noticed problems with versions 10.1 10.2, 10.3 or 10.4? -- Laurent Ducos Administrateur système et réseaux chez BibLibre IT system and network administrator at BibLibre

6 7

Duplicated holds notices
by Nick Clemens 14 Oct '19

14 Oct '19

Hi All, We have been getting several reports of duplicated holds notices on a few systems. We cannot find any issues in the code that would duplciate this, there are not duplicated transports or anything in the data we can find. We have noticed that some of the modals have a submit button, and then js to submit the form, however, Kyle attempted to add 'preventDoubleFormSubmit()' to the page and that has not helped $(document).ready(function() { if (window.location.href.indexOf("circ/ returns.pl") > -1) { $('form').preventDoubleFormSubmit(); } }); Has anyone else experienced this? -Nick -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern

2 3

Removing data from hea.koha-community.org
by dcook＠prosentient.com.au 14 Oct '19

14 Oct '19

Hi all, Do we have any process for removing data from hea.koha-community.org? For instance, say that a library permanently closes, or just no longer wants to be listed? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 1

Koha, centOS, Apache, starman => random timeout !
by Paul Poulain 07 Oct '19

07 Oct '19

Hello, We have a library running Koha (17.11) on his own centOS (virtual) server, with Apache as webserver. Everything is working smoothly, except that, from time to time (about once a day), it's not working anymore, any page returns: "Proxy error, Error reading from remote server" The logs shows nothing except a strange: [Wed Jul 10 17:17:35.732798 2019] [proxy_http:error] [pid 322] (70007)The timeout specified has expired: [client 1.2.3.4:32988] AH01102: error reading status line from remote server localhost:5000, referer: https://xxx.xxx.xxx.fr/cgi-bin/koha/catalogue/detail.pl?biblionumber=78504&… [Wed Jul 10 17:17:35.732861 2019] [proxy:error] [pid 322] [client 1.2.3.4:32988] AH00898: Error reading from remote server returned by /cgi-bin/koha/catalogue/search.pl, referer: https://xxx.xxx.xxx.fr/cgi-bin/koha/catalogue/detail.pl?biblionumber=78504&… <https://admin.panam.culture.fr/cgi-bin/koha/catalogue/detail.pl?biblionumbe…> What is stranger : after a few minutes, without any action on the server, everything is back, and working well. did anyone face such a problem ? any idea welcomed ! -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 1

A case against some uses of C4::Context->userenv
by Tomas Cohen Arazi 30 Sep '19

30 Sep '19

Hi all, I've been looking at the 'Claims returned' work (awesome!) [1] and I've noticed a pattern we should, in my opinion, start avoiding and reverting. It is quite common to find uses of C4::Context->userenv in the Koha::* namespace, either as a plain requirement (if the borrowernumber is not set we bail out) or just as a fallback. I think it is wrong to expect such environment status in our logic. It complicates things in various ways. [2] It is done this way because: - We come from the CGI era, in which it made perfect sense - Cookie auth is well established on the UI - When migrating from C4:* into Koha:* it is easier to just keep the current behavior and then evolve. I propose we leave them out, and add as a parameter whatever we are expecting to find in the userenv hashref. That way we could use this new libs in the API (which is not cookie-only). Looking forward to hear your opinions [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 [2] CLI scripts are using Koha::* libraries, and we then need to 'emulate' that userenv or even add code to detect we don't have a userenv. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

5 4

kohastructure.sql : columns with COLLATE
by Fridolin SOMERS 30 Sep '19

30 Sep '19

Hi I'm working on DB structure compare. I note that in installer/data/mysql/kohastructure.sql, a few columns define CHARACTER SET and/or COLLATE, with same values as table. Is this usefull or should we remove it ? $ grep 'COLLATE' installer/data/mysql/kohastructure.sql | grep -v ENGIN | grep 'utf8mb4_unicode_ci' `category_name` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `font` char(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'TR', `text_justify` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'L', `auto_renew_error` varchar(32) COLLATE utf8mb4_unicode_ci DEFAULT NULL, -- automatic renewal error `auto_renew_error` varchar(32) COLLATE utf8mb4_unicode_ci DEFAULT NULL, -- automatic renewal error `suppliers_report` MEDIUMTEXT COLLATE utf8mb4_unicode_ci, -- reports received from suppliers entity varchar(16) COLLATE utf8mb4_unicode_ci NOT NULL, code varchar(64) COLLATE utf8mb4_unicode_ci NOT NULL, lang varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL, -- could be a foreign key translation MEDIUMTEXT COLLATE utf8mb4_unicode_ci, `branchcode` varchar(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

5 4

Koha Newsletter: September 2019
by Koha Newsletter 29 Sep '19

29 Sep '19

The Koha Community Newsletter for September 2019 is here: https://koha-community.org/koha-community-newsletter-september-2019/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Koha and Wikidata
by Stefano Bargioni 25 Sep '19

25 Sep '19

Hi, is there somebody with experience in MediaWiki::Bot or MediaWiki::API? I'd like to evaluate the interaction with Wikidata from/to Koha, for authority records. Thx. Stefano

3 2

Koha 19.05.01 release
by Fridolin SOMERS 24 Sep '19

24 Sep '19

The Koha community is proud to announce the release of Koha 19.05.01. This is a maintenance release with 1 security bugfix. The full release notes are available at https://koha-community.org/koha-19-05-01-release/ Debian packages are available. After maintaining 17.11.x I'm proud to continue with actual stable version. I'm then looking forward to see "Koha 20". Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

3 5