- Koha - lists.katipo.co.nz

Adding an encryption_key to koha-conf.xml
by Mike Lake 30 Jun '22

30 Jun '22

Hi All Just upgraded tonight from Koha 21.11.05.000 to 22.05.00-1 That all went fine. The About Koha page now says: "Warning: You are missing the <encryption_key> entry in your koha-conf.xml file. Please generate a key." I can see a place for this is the koha-conf-site.xml.in file (and a suggestion to use pwgen 32) but how do you process this to the koha-conf.xml files for each site? The "pwgen 32" suggests this should be 32 characters and is itself just something that no one should be able to guess. So I can can just put anything in there that is long and complex? I could not find anything about this is the docs or wiki or recent emails, just the patch for it in the github repo via Google. Thanks Mike

4 7

Delete patron via REST API - Missing property - Status 500
by zefanja 30 Jun '22

30 Jun '22

Hello, I want to delete patrons with the REST API. If the patron has no checkouts, everything works fine. But when the patron has checkouts, I get this as response from my HTTP DELETE request: {"errors":[{"message":"Missing property.","path":"\/errors"}],"status":500} The API docs say that it should return a 409 status with errors → has_checkouts https://api.koha-community.org/#operation/deletePatron Any ideas? I send the requests to this url: https://our-library-intra.com/api/v1/patrons/23 Regards, Stephan

2 2

Koha 22.05.02 released
by Lucas Gass 29 Jun '22

29 Jun '22

Hello! The Koha community is proud to announce the release of Koha 22.05.02! Koha 22.05.02 is a maintenance release including 5 enhancements and 48 bugfixes. The full release notes can be found here: https://koha-community.org/koha-22-05-02-release/ Debian packages should be available shortly! -- Lucas Gass Web Developer

1 0

koha-US July 2022 Events & Meetings
by Jennifer Marlatt 29 Jun '22

29 Jun '22

koha-US online meetings and events are free and open to all. See our calendar for a full list: http://koha-us.org/calendar/. For Google Calendar users, add our events calendar to your list for easy access to meeting times and links: https://calendar.google.com/calendar/u/1?cid=a29oYS11cy5vcmdfZG1xb2pkczE5Zn… *Meetings* Board Meeting - Wednesday, July 6 @ 8:30a PT / 11:30a ET / 15:30 UTC General Meeting - Wednesday, July 13 @ 8:30a PT / 11:30a ET / 15:30 UTC *Special Interest Groups* Circulation - Tuesday, July 5 @ 10:00a PT / 1:00p ET / 17:00 UTC Cataloging - Thursday, July 7 @ 8:00a PT / 11:00a ET / 15:00 UTC System Administration - Tuesday, July 12 @ 8:00a PT / 11:00p ET / 15:00 UTC Acquisitions - Tuesday, July 19 @ 9:00a PT / 12:00p ET / 16:00 UTC Web Development - Thursday, July 21 @ 10:00a PT / 1:00p ET / 17:00 UTC Demonstration Instance - Tuesday, July 26 @ 8:00a PT / 11:00a ET / 15:00 UTC Consortia - Thursday, July 28 @ 9:00a PT / 12:00p ET / 16:00 UTC Visit http://koha-us.org/special-interest-groups/ to learn more and sign up for topic-specific mailing lists. Most meetings and events are recorded and made available at https://www.youtube.com/kohaus Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0

After Koha update and auto_increment_fix database won't start
by Isabel Pineda 29 Jun '22

29 Jun '22

Hi. I have just updated Koha from 21.11.06 to 21.11.09. After that I got a warning on the "About Koha" page that some tables have problems with auto_increment, there was a link to this page: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix I followed the instructions on this page, but when I tried to restart mysql, MariaDB wouldn't start. The error message says: job for mariadb.service failed because the control process exited with error code I looked for solutions, but the only ones that I found included to remove all data from the database directory, and I don't want to do this. Is there any other solution? Thank you very much Isabel Pineda

4 4

Koha 21.05.16 released
by Victor Grousset/tuxayo 28 Jun '22

28 Jun '22

Hello! :) The Koha Community is happy to announce the release of Koha 21.05.16 The full release notes can be found at: https://koha-community.org/koha-21-05-16-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

RV: After Koha update and auto_increment_fix database won't start
by Isabel Pineda 28 Jun '22

28 Jun '22

Hi Mason. There is no file in the folder /etc/mysql/mariadb.conf.d I cannot find the file "50-server.cnf" anywhere. In the folder /etc/mysql/conf.d I can see the files "mariadb.cnf", "mysql.cnf", "mysqld_safe_syslog.cnf" and "mysqldump.cnf". Should I add the line to one of these files? Thank you Isabel -----Mensaje original----- De: Mason James <mtj(a)kohaaloha.com> Enviado el: martes, 28 de junio de 2022 09:20 Para: Isabel Pineda <isabel.pineda(a)ds.edu.sv>; Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> CC: koha(a)lists.katipo.co.nz Asunto: Re: [Koha] After Koha update and auto_increment_fix database won't start try adding to line to the following file... then restart /etc/mysql/mariadb.conf.d/50-server.cnf > I followed the instructions in > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Current_S > olution Probably I did something wrong when I added the line > init-file=/var/lib/mysql/init-file_koha_fix.sql > at /etc/mysql/my.cnf. The instruction says to find the [mysqld] section in the file, but in my my.cnf file there is only one line that says: > !includedir /etc/mysql/conf.d

1 0

Are there any french speaking users from Africa, Canada or anywhere else than France here?
by Victor Grousset/tuxayo 27 Jun '22

27 Jun '22

Hi :) I need to reach french speaking users from anywhere in the world to organize sessions of patch testing (signoff). In France we have a user group [1] so it's easy to reach the local community. But what about the rest of the french speaking world? Let me know if you have any leads. Cheers, [1] https://koha-fr.org and they have a mailing list https://groupes.renater.fr/sympa/info/koha.infos -- Victor Grousset/tuxayo

2 1

System preference "AutoRenewalNotices"
by Michael Kuhn 27 Jun '22

27 Jun '22

Hi After updating to Koha 21.11.06 the system is sending us the following e-mail every day: ### START ### /etc/cron.daily/koha-common: The "AutoRenewalNotices" syspref is set to 'Follow the cron switch'. The send_notices switch for this script is deprecated, you should either set the preference to 'Never send emails' or 'Follow patron messaging preferences' The "EnhancedMessagingPreferences" syspref is off. Therefore, it is unlikely that this script will actually produce any messages to be sent. To change this, edit the "EnhancedMessagingPreferences" syspref. ### END ### In fact we have already set the value of system preference "AutoRenewalNotices" to "never" after the first such e-mail: select variable, value from systempreferences where variable="AutoRenewalNotices"; +--------------------+-------+ | variable | value | +--------------------+-------+ | AutoRenewalNotices | never | +--------------------+-------+ Also, in fact system preference "EnhancedMessagingPreferences" is on (not off): select variable, value from systempreferences where variable="EnhancedMessagingPreferences"; +------------------------------+-------+ | variable | value | +------------------------------+-------+ | EnhancedMessagingPreferences | 1 | +------------------------------+-------+ How can we get rid of these annoying e-mails? 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

1 1

Koha Sql Report Help
by Shafrizan Affendi 26 Jun '22

26 Jun '22

Hi, Recently I upgraded my Koha from ver 18 to 22.05. Some of my sql report are not working anymore. For example to show a fine collection by staff id. Here is my previous sql. SELECT @rownum:=@rownum+1 No, student.borrowernumber, student.cardnumber AS Student_ID, student.surname AS Student_Name, format(db.amount,2) As Amount, accounttype, date(db.timestamp) as Date, time(db.timestamp) As Time, db.manager_id AS Staff_ID, staff.surname AS Staff_Name, db.note As Nota FROM (SELECT @rownum:=0) r, action_logs a, accountlines db INNER JOIN borrowers student ON db.borrowernumber = student.borrowernumber INNER JOIN borrowers staff ON db.manager_id = staff.borrowernumber WHERE date(db.timestamp) BETWEEN <<Between (YYYY-MM-dd)|date>> AND <<and (YYYY-MM-DD|date>> AND module='fines' AND accounttype='pay' GROUP BY db.timestamp ORDER BY db.timestamp I did read about the changes regarding table accountype but still not quite understand. Anyone can help me to correct this sql? Really appreciate your help Thanks in advance

2 1