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

Signoff request
by Marcel de Rooy 16 Apr '24

16 Apr '24

Hello all, I need help on the following bugs (signoffs), all related to acquisition, although some marked as architectural: 36002 Koha Acquisit m.de.rooy(a)rijksmuseum.nl Need --- enh Get rid of aqorders.purchaseordernumber 2024-02-06 36018 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh Improve consistency in Acquisition/Order(s) regarding active/current orders 2024-03-25 (rebased) 35994 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh New acquisition status method to see if biblio record is still in acquisition 13:04:46 (changed title) Still apply on master today. Would be nice to see them getting further. 35994 has dependencies. Thanks, Marcel

1 0

REMINDER: Development IRC meeting on the 17th of April 2024
by Paul Derscheid 16 Apr '24

16 Apr '24

Hi all, We have a Development IRC/Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_17_April_2024 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I…> Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. If you are lead or supporter of a roadmap project, we will be happy to get an update on progress. See you there! Paul

1 0

Error 500 when searching in Koha 23.11.0
by Michael Kuhn 15 Apr '24

15 Apr '24

Hi I have updated our database from koha 21.11.10 to the current Koha 23.11.04. When searching the catalogue I get a result list, but when clicking a single hit I get an error 500. In file "plack-error.log" I have found the following line which could be the reason: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'issue.renewals_count' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 317 In fact there is no table "issue" in Koha 23.11, the correct name of this table is "issues" (see https://schema.koha-community.org/23_11/tables/issues.html) I have searched in Bugzilla but couldn't find a respective bug. But I found the sequence "issue.renewals_count" in https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152 so there may be some relation to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 Does anyone know how I can solve this problem with the 500 error? Best wishes: Michael Kuhn -- 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

3 6

Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL
by David Cook 15 Apr '24

15 Apr '24

I’m just finishing up the next version of the plugin which finds problem bib records, problem item records, and lets you fix 1 bib record and its X problem item records at a time. I’ll be putting it up online sometime in the next couple weeks. (I’m away a lot these couple of weeks, so tough to give a firm time.) But I’m about to use it to find problem item records in one of my systems… David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Tomas Cohen Arazi <tomascohen(a)theke.io> Sent: Sunday, 14 April 2024 2:49 AM To: Magnus Enger <magnus(a)libriotech.no> Cc: David Cook <dcook(a)prosentient.com.au>; koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL Yeah, dump it somewhere and we send pull requests to add missing bits El El vie, 12 abr 2024 a la(s) 9:50 a. m., Magnus Enger via Koha-devel <koha-devel(a)lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > escribió: Den 12.04.2024 08:24, skrev David Cook: > Not yet. At some point I need to get better at sharing Koha plugins more widely. Just dump it to Github or similar, and set the version to 0.0.1. ;-) Release early, release often. Best regards, Magnus _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/

1 0

Koha CSRF protection
by Nick Clemens 13 Apr '24

13 Apr '24

Hello all! We have pushed the CSRF work from 34478 and related bugs today. We know there are more follow-ups needed, and have filed a series of bugs under an omnibus: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 We have a framapad where issues can be reported/found: https://annuel.framapad.org/p/koha_34478_remaining And we have bugs for each of the sections of the document. We need all developers to submit patches when they encounter issues, and for other users testing master to report found issues on the pad. Testers can report issues on the pad as well. There is a new coding guideline - all POSTs to forms in Koha will need to include a csrf token: https://wiki.koha-community.org/wiki/Coding_Guidelines#Security This has been a big work, many thanks to all involved, and there is still work to be done, but this is an important fix that we must do. You can reach out to me on IRC (kidclamp) or via email and I will do my best to help anyone contribute. Thanks, Nick -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution>

5 7

Call for news - Newsletter April 2024
by Koha Newsletter 13 Apr '24

13 Apr '24

Hi I'm collecting news for the April 2024 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. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Re: [Koha-devel] [Koha] Error 500 when searching in Koha 23.11.0
by Michael Kuhn 12 Apr '24

12 Apr '24

Hi Ketan Kulkarni You wrote: > There's a command to upgrade koha db schema. You need to run that > command. > > Following is an example. Here, 'library' is the name of the instance. > You will need to replace that with the name of your instance. > ===============================// > > Upgrade Database Schema > Database schema of old Koha should upgrade to new one. Apply following > commands in a terminal, > > sudo koha-upgrade-schema library > > Rebuild the Zebra Index. > > Apply following command in a terminal, > > sudo koha-rebuild-zebra -v -f library > ================================ I have already run these commands (upgrade and reindexing) - they both finished without an error. I do have a running Koha 23.11 instance and acn log in. But as written when I search for something and then click a single hit in the results list the error 500 appears... Any other ideas? 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 > There's a command to upgrade koha db schema. You need to run that command. > > Following is an example. Here, 'library' is the name of the instance. > You will need to replace that with the name of your instance. > ===============================// > > Upgrade Database Schema > Database schema of old Koha should upgrade to new one. Apply following > commands in a terminal, > > sudo koha-upgrade-schema library > > Rebuild the Zebra Index. > > Apply following command in a terminal, > > sudo koha-rebuild-zebra -v -f library > ================================ > > On Fri, 12 Apr 2024, 20:04 Michael Kuhn, <mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch>> wrote: > > Hi Ketan Kulkarni > > Thanks for your answer! Youw rote: > > > Compare the database structure with the published schema of the > > version. > > How could I do that? There are hundreds of tables with many more > hundreds of fields. > > Is there a way how to extract the database structure from > https://schema.koha-community.org/23_11/ > <https://schema.koha-community.org/23_11/> and also from a running > database? > > > My guess is that the db upgrade has not gone through cleanly. > > 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 > <mailto:mik@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> > > > > > On Fri, 12 Apr 2024, 17:42 Michael Kuhn, <mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch> > > <mailto:mik@adminkuhn.ch <mailto:mik@adminkuhn.ch>>> wrote: > > > > Hi > > > > I have updated our database from koha 21.11.10 to the current > Koha > > 23.11.04. > > > > When searching the catalogue I get a result list, but when > clicking a > > single hit I get an error 500. In file "plack-error.log" I > have found > > the following line which could be the reason: > > > > DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: > > DBD::mysql::st > > execute failed: Unknown column 'issue.renewals_count' in 'field > > list' at > > /usr/share/koha/lib/Koha/Objects.pm line 317 > > > > In fact there is no table "issue" in Koha 23.11, the correct > name of > > this table is "issues" (see > > https://schema.koha-community.org/23_11/tables/issues.html > <https://schema.koha-community.org/23_11/tables/issues.html> > > <https://schema.koha-community.org/23_11/tables/issues.html > <https://schema.koha-community.org/23_11/tables/issues.html>>). > > > > I have searched in Bugzilla but couldn't find a respective > bug. But I > > found the sequence "issue.renewals_count" in > > > https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152 > <https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152> > > > <https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152 <https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152>> so > > there may be some relation to > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275> > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275>> > > > > Does anyone know how I can solve this problem with the 500 error? > > > > Best wishes: Michael Kuhn > > -- > > 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 > <mailto:mik@adminkuhn.ch> > > <mailto:mik@adminkuhn.ch <mailto:mik@adminkuhn.ch>> · W > www.adminkuhn.ch <http://www.adminkuhn.ch> <http://www.adminkuhn.ch > <http://www.adminkuhn.ch>> > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > <http://koha-community.org> <http://koha-community.org > <http://koha-community.org>> > > Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > <mailto:Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>> > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha> > > <https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha>> > > > >

1 0

Finding invalid XML characters in Koha data via SQL
by David Cook 12 Apr '24

12 Apr '24

Hi all, I just wanted to share a (MariaDB) SQL report that I wrote for finding bib records with invalid XML characters: select biblionumber from biblio_metadata where metadata REGEXP '[^\\x{0009}\\x{000A}\\x{000D}\\x{0020}-\\x{D7FF}\\x{E000}-\\x{FFFD}\\x{1000 0}-\\x{10FFFF}]+'; Newer versions of Koha strip invalid character from the XML so that you can fix your records. I figure this report is very valuable when coupled with that functionality. In fact, I just advised a library today to use them together to fix up some bad data in their catalogue. -- On a related note, I've noticed that you can have a record with good bib XML but invalid item XML, and you won't notice until your record fails to be indexed. So I'm planning on writing a report for that too. I'm thinking it might be good to add these reports to core Koha, so that people can find and fix their own metadata problems. What do people think? David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

4 8

Update to Koha 23.11.04 fails
by Michael Kuhn 12 Apr '24

12 Apr '24

Hi Today I tried to update a Koha 21.11.10 database to Koha 23.11.04 but the update process failed at the following point: Upgrade to 23.06.00.068 [22:55:59]: Bug 23798 - Convert OpacMaintenanceNotice system preference to additional contents ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db selectrow_array failed: Unknown column 'id' in 'field list' at /usr/share/koha/lib/C4/Installer.pm line 741 I couldn't find anything regarding this error in Bugzilla, but maybe it is related to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23798#c12 which shows a similar error regarding an "Unknown column 'title'". How should I proceed? 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 2

Bug 36586 - Self-checkouts will get CSRF errors if left inactive for 8 hours
by David Cook 11 Apr '24

11 Apr '24

Hi all, We recently noticed that self-checkouts will generate CSRF errors when left unattended for over 8 hours (the lifetime of the CSRF token). Our solution is to use a timer to refresh the page every 8 hours or so, but open to other ideas. This will potentially affect Vue.js driven pages that don't reload the whole page. Although maybe Jonathan has already come up with a solution for that. I'm not sure. David Cook Senior 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