<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 7109 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 202, Issue 23<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Bug 31654 - Hide non-public libraries from<br> MastheadLibraryPulldown (Thomas Klausner)<br> 2. Merging authority records can corrupt data (Thomas Klausner)<br> 3. Re: koha-create with remote mariadb server (David Schmidt)<br> 4. Re: Merging authority records can corrupt data (Pedro Amorim)<br> 5. Re: Critical error on Koha website (Liz Rea)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 30 Sep 2022 13:50:27 +0200<br>From: Thomas Klausner <domm@plix.at><br>To: Koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] Bug 31654 - Hide non-public libraries from<br> MastheadLibraryPulldown<br>Message-ID: <20220930115027.GB1853016@plix.at><br>Content-Type: text/plain; charset=utf-8<br><br>Hi!<br><br>I've just submitted a patch implementing Bug 31654 - Hide non-public libraries from MastheadLibraryPulldown<br><br>It's quite simple (two lines in two files), and the sponsor <br>(Steiermärkische Landesbibliothek) would be happy if the fix makes it <br>into 22.11. So if there is anything I can do to make that happen, please <br>advise :-)<br><br>Greetings,<br>domm<br><br>-- <br>#!/usr/bin/perl https://domm.plix.at<br>for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br><br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 30 Sep 2022 14:19:13 +0200<br>From: Thomas Klausner <domm@plix.at><br>To: Koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] Merging authority records can corrupt data<br>Message-ID: <20220930121913.GC1853016@plix.at><br>Content-Type: text/plain; charset=utf-8<br><br>Hi!<br><br>It seems that merging authorities with lots of linked biblios can lead <br>to data corruption (at least in 21.05):<br><br>The merging of the auth record itself seems to work, but the linking of <br>the biblios from old to new auth record happens inside a normal <br>synchrone web request. If this requests times out (because there might <br>be a lot of biblio records to relink), some of the biblios still point <br>to the old auth, which is already deleted. (At least this seems to be <br>happening, based on the complaints we got from librarians)<br><br>I guess the only fix is to handle authority merging via background jobs <br>/ job queue.<br><br>Is this a known bug? I couldn't find anything about that in bugzilla?<br>If yes, is there a timeframe when it will be fixed?<br>If no, I will create a bug (though reproducing it will need some weird <br>fixtures in the DB..).<br><br>In any case, the Steiermärkische Landesbibliothek is keen to get this <br>working, so I could give fixing it a try. But this will need some <br>discussion, I assume? As I suppose this will be a bit more work than a <br>single-line fix in a template, I'd like to have some backing by other <br>Koha-devs, that this behaviour is indeed a bug, and that using <br>background jobs is the correct way to fix it.<br><br>Greetings,<br>domm<br><br>-- <br>#!/usr/bin/perl https://domm.plix.at<br>for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br><br><br>------------------------------<br><br>Message: 3<br>Date: Fri, 30 Sep 2022 15:46:09 +0200<br>From: "David Schmidt" <mail@davidschmidt.at><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] koha-create with remote mariadb server<br>Message-ID: <a989a3bf-7e99-4c94-a4ea-31acbda91067@app.fastmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>with the help from koha irc and lots of try&error&code-reading I figured some things out<br><br>### on your database server:<br><br>apt update && apt install -y mariadb-server<br>sed -i -e 's/^bind-address\s*=\s*127\.0\.0\.1$/bind-address = */' /etc/mysql/mariadb.conf.d/50-server.cnf<br>/etc/init.d/mariadb restart<br>mysql -e "CREATE DATABASE koha_demo;"<br>mysql -e "CREATE USER 'koha_demo'@'%' IDENTIFIED BY 'kohadbpw';"<br>mysql -e "GRANT ALL PRIVILEGES on koha_demo.* TO koha_demo;"<br>mysql -e "FLUSH PRIVILEGES;"<br><br>### on your koha server<br>apt update && apt install -y wget gnupg<br>wget -q -O- https://debian.koha-community.org/koha/gpg.asc | apt-key add -<br>echo 'deb http://debian.koha-community.org/koha 22.05 main' | tee /etc/apt/sources.list.d/koha.list<br>apt update<br>apt install koha-common -y<br><br>a2enmod rewrite<br>a2enmod cgi<br>service apache2 restart<br><br>mv /etc/mysql/koha-common.cnf /etc/mysql/koha-common.cnf.bak<br>echo "[client]<br>host = mariadb<br>user = koha_demo<br>password = kohadbpw" > /etc/mysql/koha-common.cnf<br><br>sed -i -e 's/^DOMAIN="\.myDNSname\.org"$/DOMAIN=".koha-support.eu"/' /etc/koha/koha-sites.conf<br>sed -i -e 's/^OPACSUFFIX=""$/OPACSUFFIX="-opac"/' /etc/koha/koha-sites.conf<br><br>#instance:username:password:dbname:dbhost<br>echo "koha-demo:koha_demo:kohadbpw:koha_demo:mariadb" > koha_db_passwdfile.txt<br><br>koha-create --passwdfile=koha_db_passwdfile.txt --use-db koha-demo<br><br>On Thu, 29 Sep 2022, at 6:47 PM, David Schmidt wrote:<br>> im trying to create a koha instance configured for a remote mariadb server<br>> <br>> https://wiki.koha-community.org/wiki/Debian#Create_a_Koha_instance<br>> <br>> > remove /etc/mysql/koha-common.cnf<br>> > create a new file in its place containing the connection<br>> information for the server, in the form of a my.cnf file.<br>> <br>> 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<br>> <br>> <br>> $ koha-create --dbhost 172.23.0.3 --database kohadb --request-db koha-demo<br>> $ vim koha-demo-db-request.txt<br>> $ koha-create --dbhost 172.23.0.3 --database kohadb --populate-db koha-demo<br>> Koha instance is empty, no staff user created.<br>> <br>> after that I still see the autogenerated password in /etc/koha/sites/koha-demo/koha-conf.xml and the mariadb database is empty<br>> <br>> 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.<br>> <br>> I will update the wiki after I figured this out<br>> <br>> cheers<br>> david<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>> <br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220930/79473b20/attachment-0001.htm><br><br>------------------------------<br><br>Message: 4<br>Date: Fri, 30 Sep 2022 14:11:13 +0000<br>From: Pedro Amorim <pjamorim91@gmail.com><br>To: Koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Merging authority records can corrupt data<br>Message-ID:<br> <CALWP7TLQjE9p2rbc05FqAxnW5afe2-dqEf4xa9nzq6HSM0QHVg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Thomas,<br><br>Not sure if this will help but what is the value of the<br>*AuthorityMergeLimit* sys pref?<br>I think the default value is 50 and any authority being merged with more<br>than 50 linked biblios will be processed by the<br>*misc/migration_tools/merge_authority.pl<br><http://merge_authority.pl>* cronjob (which runs daily by default if I'm<br>not mistaken).<br>If the problem you're experiencing is indeed related to having lots of<br>linked biblios, maybe lowering this value (or setting it if empty) might<br>help?<br><br>In the past I reported an issue with subsequent authority merging (that get<br>queued to be processed by the cronjob):<br>https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22437<br><br>But I believe this has been fixed.<br><br><br>On Fri, 30 Sept 2022 at 12:19, Thomas Klausner <domm@plix.at> wrote:<br><br>> Hi!<br>><br>> It seems that merging authorities with lots of linked biblios can lead<br>> to data corruption (at least in 21.05):<br>><br>> The merging of the auth record itself seems to work, but the linking of<br>> the biblios from old to new auth record happens inside a normal<br>> synchrone web request. If this requests times out (because there might<br>> be a lot of biblio records to relink), some of the biblios still point<br>> to the old auth, which is already deleted. (At least this seems to be<br>> happening, based on the complaints we got from librarians)<br>><br>> I guess the only fix is to handle authority merging via background jobs<br>> / job queue.<br>><br>> Is this a known bug? I couldn't find anything about that in bugzilla?<br>> If yes, is there a timeframe when it will be fixed?<br>> If no, I will create a bug (though reproducing it will need some weird<br>> fixtures in the DB..).<br>><br>> In any case, the Steiermärkische Landesbibliothek is keen to get this<br>> working, so I could give fixing it a try. But this will need some<br>> discussion, I assume? As I suppose this will be a bit more work than a<br>> single-line fix in a template, I'd like to have some backing by other<br>> Koha-devs, that this behaviour is indeed a bug, and that using<br>> background jobs is the correct way to fix it.<br>><br>> Greetings,<br>> domm<br>><br>> --<br>> #!/usr/bin/perl https://domm.plix.at<br>> for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220930/994950ee/attachment-0001.htm><br><br>------------------------------<br><br>Message: 5<br>Date: Fri, 30 Sep 2022 09:32:33 -0500<br>From: Liz Rea <wizzyrea@gmail.com><br>To: Michael Kuhn <mik@adminkuhn.ch><br>Cc: Koha <koha@lists.katipo.co.nz>, Koha-devel<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Critical error on Koha website<br>Message-ID:<br> <CAD+xdkR5WqqsF6szspT81J935_G8L_-sVw+d8deSRHD4ATQ8bw@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi friends,<br><br>This was related to an update to Wordpress and the theme we use. Have<br>sorted out those issues and things are seeming better now, if you'd please<br>test!<br><br>Cheers,<br>Liz<br><br>On Thu, Sep 29, 2022 at 2:51 PM Michael Kuhn <mik@adminkuhn.ch> wrote:<br><br>> Hi<br>><br>> When I'm trying to preview or release the current Koha newsletter I'm<br>> getting the following message:<br>><br>> There has been a critical error on this website.<br>><br>> I'm also getting this message when I try to access older newsletters,<br>> for example<br>><br>> * https://koha-community.org/koha-community-newsletter-april-2022/<br>> * https://koha-community.org/koha-community-newsletter-august-2022/<br>><br>> Can someone with the necessary rights and knowledge please remove this<br>> problem?<br>><br>> Best wishes: Michael<br>> --<br>> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis<br>> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz<br>> T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220930/0450c17f/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 202, Issue 23<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>