September 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

Critical error on Koha website
by Michael Kuhn 29 Oct '22

29 Oct '22

Hi When I'm trying to preview or release the current Koha newsletter I'm getting the following message: There has been a critical error on this website. I'm also getting this message when I try to access older newsletters, for example * https://koha-community.org/koha-community-newsletter-april-2022/ * https://koha-community.org/koha-community-newsletter-august-2022/ Can someone with the necessary rights and knowledge please remove this problem? Best wishes: Michael -- 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

2 3

Excess fields in Koha 22.05 file "patron_import.csv"
by Michael Kuhn 30 Sep '22

30 Sep '22

Hi When unloading the field names of Koha 22.05 table "borrowers" I get 79 field names (plus "borrowernumber"). But when in Koha 22.05 menu "Tools > Import patrons" I click the link "Starter CSV file" the unloaded file "patron_import.csv" does include 82 fields. When comparing the two outputs I see there are three more fields in file "patron_import.csv" than in table "borrowers": patron_attributes guarantor_relationship guarantor_id These three fields aren't included in https://schema.koha-community.org/22_05/tables/borrowers.html What is the explanation for these excess fields? Best wishes: Michael -- 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

2 1

Merging authority records can corrupt data
by Thomas Klausner 30 Sep '22

30 Sep '22

Hi! It seems that merging authorities with lots of linked biblios can lead to data corruption (at least in 21.05): The merging of the auth record itself seems to work, but the linking of the biblios from old to new auth record happens inside a normal synchrone web request. If this requests times out (because there might be a lot of biblio records to relink), some of the biblios still point to the old auth, which is already deleted. (At least this seems to be happening, based on the complaints we got from librarians) I guess the only fix is to handle authority merging via background jobs / job queue. Is this a known bug? I couldn't find anything about that in bugzilla? If yes, is there a timeframe when it will be fixed? If no, I will create a bug (though reproducing it will need some weird fixtures in the DB..). In any case, the Steiermärkische Landesbibliothek is keen to get this working, so I could give fixing it a try. But this will need some discussion, I assume? As I suppose this will be a bit more work than a single-line fix in a template, I'd like to have some backing by other Koha-devs, that this behaviour is indeed a bug, and that using background jobs is the correct way to fix it. Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

2 2

koha-create with remote mariadb server
by David Schmidt 30 Sep '22

30 Sep '22

im trying to create a koha instance configured for a remote mariadb server https://wiki.koha-community.org/wiki/Debian#Create_a_Koha_instance > remove /etc/mysql/koha-common.cnf > create a new file in its place containing the connection information for the server, in the form of a my.cnf file. what does that mean? the only my.cnf file that I can find on the system is /etc/mysql/my.cnf and that doesnt look right $ koha-create --dbhost 172.23.0.3 --database kohadb --request-db koha-demo $ vim koha-demo-db-request.txt $ koha-create --dbhost 172.23.0.3 --database kohadb --populate-db koha-demo Koha instance is empty, no staff user created. after that I still see the autogenerated password in /etc/koha/sites/koha-demo/koha-conf.xml and the mariadb database is empty after reading the koha-create source i have a feeling this --request-db/--populate-db stuff cant possibly work. --populate-db is trying to get the db passwort using getinstancemysqluser() but that function is a wrapper around xmlstarlet and i was just told by `koha-create --request-db` to write the new db password into this txt file. I will update the wiki after I figured this out cheers david

1 1

Bug 31654 - Hide non-public libraries from MastheadLibraryPulldown
by Thomas Klausner 30 Sep '22

30 Sep '22

Hi! I've just submitted a patch implementing Bug 31654 - Hide non-public libraries from MastheadLibraryPulldown It's quite simple (two lines in two files), and the sponsor (Steiermärkische Landesbibliothek) would be happy if the fix makes it into 22.11. So if there is anything I can do to make that happen, please advise :-) Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

1 0

Koha Community Newsletter: September 2022
by Koha Newsletter 30 Sep '22

30 Sep '22

The Koha Community Newsletter for September 2022 is here: https://koha-community.org/koha-community-newsletter-september-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 PS. Unfortunately the Wordpress template for the Koha Community website has considerably changed since the last newsletter (and not in a way that I would prefer). This is not only affecting all previous newsletters since 2010 but also previous release notes etc.

1 0

Koha support for Debian 9 ends
by Mason James 22 Sep '22

22 Sep '22

kia ora community, debian ended support for debian 9 (stretch) on June 30, 2022 https://wiki.debian.org/LTS https://www.debian.org/releases/stretch/ so, we recommend you upgrade any debian 9 Koha systems to debian 10 or 11 cheers, Mason

1 0

Elasticsearch not auto-updating after cataloguing
by Philippe Blouin 16 Sep '22

16 Sep '22

Hello kohaers! Simply put: our production servers installation work very fine, each change into a record is immediately reindexed into ES. BUT on laptop (ubuntu 20 or 22), the reindexing never occurs. We have to call rebuild_elasticsearch.pl manually so the search finds anything. The configuration refers to a remote ES server (instead of localhost like the prod servers), but I don't see how that would make a difference since that works once rebuilt. Any clue on what I'm missing would be greatly appreciated. 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>

3 4