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

Time to translate: string freeze to prepare Koha 19.11.18 has begun
by Victor Grousset/tuxayo 14 May '21

14 May '21

Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for around the 24th/25th. **If you missed it the upcoming 21.05 release is translatable now.** This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05, 20.11 and 21.05. Otherwise your work will be lost for future versions. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo

1 0

Time to translate: string freeze to prepare 20.11.06 release
by Fridolin SOMERS 14 May '21

14 May '21

Hi, String freeze is into effect today 🥶 The 20.11.x maintenance branch is preparing for 20.11.06 release 📦 The release is scheduled for around the 25. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Note that nl-NL translation for 20.11 was very low, I've ask them to be reinitialized with merge of files from 19.11. Translation is now around 70%. Keep in mind that translation must be done with priority on higher version 🔥 Happy translating 🌎🌍🌏 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

Call for news - Newsletter May 2021
by Michael Kuhn 13 May '21

13 May '21

Hi I'm collecting news for the May 2021 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. 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 to be announced are fine, e. g. Kohacon. * For past events, one month back is the cut-off. 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! Michael Kuhn Editor, Koha Community Newsletter -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

master not handling errors correctly
by dcook＠prosentient.com.au 12 May '21

12 May '21

Hi all, I was working on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325, when I noticed some really weird things going on with Koha's HTTP errors. Look at http://localhost:8081/mojo. While Koha will say it's a 404, it's actually sending back a 200 response. That's not good. (With Bug 28325 I'm having even weirder problems where mounting a new PSGI app within an existing one seems to trigger both a 200 and a 404 within Plack but only return a 200. I don't have the time/energy to deal with that though.) David Cook 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

Help needed to test a bug, knowledge required: running automated tests
by Victor Grousset/tuxayo 11 May '21

11 May '21

Hi :) Here is a bug that I tested and checked for QA. Now a test from someone else is needed. Here is the ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200 Here is the test plan: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200#c16 If you have any questions[1] I'll gladly guide you via email or chat (nickname: tuxayo) [1] including setting up a Koha environment from scratch. Cheers, -- Victor Grousset/tuxayo

1 0

API tests broken on master
by Jonathan Druart 11 May '21

11 May '21

Hi, Some of the REST API tests are failing on master, if it's blocking for you you can revert bug 28272 from your local branch. Cheers, Jonathan

1 1

TT loop count VS size
by Fridolin SOMERS 10 May '21

10 May '21

Hi community, I've been on a mindblowing search on a template error :D I was thinking that "loop.count" was wrong for testing if loop is not empty, the method is "loop.size". See doc http://template-toolkit.org/docs/manual/Directives.html#section_FOREACH Looks like we use both actually : > git grep 'IF.*\.count ' origin/master | wc -l 602 > git grep 'IF.*\.size ' origin/master | wc -l 1636 So using count seems to work because it starts with 1. But in my opinion it is a wrong call. We can see for example : <a href="#images">Images ([% localimages.count || 0 | html %])</a> This is wrong no ? Should be create a coding guideline ? -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

4 5

Help needed to test an i-tiva bug (no prior knowledge required)
by Victor Grousset/tuxayo 08 May '21

08 May '21

Hi :) Here is a bug that I tested and checked for QA. Now a test from someone else is needed. Here is the ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27562 Here is the test plan: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27562#c4 Here are instructions to setup i-tiva: https://wiki.koha-community.org/wiki/External_Integration#i-tiva I'll gladly guide you via email or tchat (nickname: tuxayo) Cheers, -- Victor Grousset/tuxayo

1 0

Embedding JSON data in HTML
by dcook＠prosentient.com.au 06 May '21

06 May '21

Hi all, I was just reflecting on bugs like https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26942 and reviewing https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script when I saw the following method for embedding JSON in HTML:  <script id="data" type="application/json">{"userId":1234,"userName":"John Doe","memberSince":"2000-01-01T00:00:00.000Z"}</script>  <script> const userInfo = JSON.parse(document.getElementById("data").text); console.log("User information: %o", userInfo); </script> I thought that was neat. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 1

Why is config ($KOHA_CONF) stored in memcached ?
by Julian Maurice 04 May '21

04 May '21

Hi all, Maybe it's a dumb question, but I don't understand why the config is stored in memcached as: - memcached server address is in this config, so we need to read $KOHA_CONF file first in order to connect to memcached server - config is kept in memory forever ($C4::Context::context), so we shouldn't need the cache once starman has started. If you add a warning in Koha::Config::read_from_file, you'll see that the file is read 3 times per worker, even when the config already exist in cache (it's read 4 times when the cache is empty). It's read each time we call Koha::Cache->new (+ in C4::Context->new if the cache is empty) Shouldn't we read the file only in C4::Context->new (without using cache), and make Koha::Cache use C4::Context->config instead ? -- Julian Maurice BibLibre

3 5