From katrin.fischer.83 at web.de Sat Jan 1 14:00:38 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sat, 1 Jan 2022 14:00:38 +0100 Subject: [Koha-devel] KohaCon22 proposals changes suggestions In-Reply-To: References: Message-ID: Hi all, +1 Maybe we could go a step further and lift the continent rotation restriction for any online only proposals. Meaning that an online conference won't remove your continent from the list of eligible continents to hold an in-person conference in the following year. Katrin On 29.12.21 09:39, Fridolin SOMERS wrote: > Hi, > > We are getting close to end date for KohaCon22 proposals, January 8. > > Unfortunately there is actually no proposal : > https://wiki.koha-community.org/wiki/KohaCon22_Proposals > > This as been discussed in last dev meeting. > https://wiki.koha-community.org/wiki/Development_IRC_meeting_22_December_2021 > > > The world situation on Covid-19 virus is not helping, we hope it will > be better soon. > > First we suggest to extend end date to mid-February. > > Second we suggest to allow proposals outside eligible continents, > keeping priority to actual ones. > We may have full-online proposals, we will see. > > If no oppositions on those changes, I will announce this beginning > January. > > Best regards, > From victor at tuxayo.net Sun Jan 2 22:05:55 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Sun, 2 Jan 2022 22:05:55 +0100 Subject: [Koha-devel] Call for volunteers to work on ElasticSearch 7 support (ES6 will be EOL on February 8) Message-ID: <571e4e75-83b9-2a37-e44b-b96b025ffdf2@tuxayo.net> Hi :) After ES6's EOL, if another vulnerability if found in Log4J for example, Koha instances using ES won't be able to patch it. Here is the omnibus ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25439 There are *at least* a 1/3 of them that look quite easy. Cheers, -- Victor Grousset/tuxayo From wainuiwitikapark at catalyst.net.nz Wed Jan 5 06:59:01 2022 From: wainuiwitikapark at catalyst.net.nz (Wainui Witika-Park) Date: Wed, 5 Jan 2022 18:59:01 +1300 Subject: [Koha-devel] Koha 19.11.24 released Message-ID: Hello everyone! The Koha community is proud to announce the release of version 19.11.24. The full release notes can be found at: https://koha-community.org/koha-19-11-24-released/ Thank you to everyone involved! Cheers, Wainui Witika-Park (she/her) From fridolin.somers at biblibre.com Wed Jan 5 23:57:12 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 5 Jan 2022 12:57:12 -1000 Subject: [Koha-devel] Dev meeting 5 January 2022 report Message-ID: <9b715b07-b2d6-1b80-362d-0d7f6ed5fc14@biblibre.com> Hi, Here is Dev meeting 5 January 2022 report : https://wiki.koha-community.org/wiki/Development_IRC_meeting_5_January_2022 Next dev meeting : https://wiki.koha-community.org/wiki/Development_IRC_meeting_19_January_2022 There is also a general meeting soon : https://wiki.koha-community.org/wiki/General_IRC_meeting_12_January_2022 See you around :D Best regards, -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From corellianimports at aol.com Thu Jan 6 02:26:12 2022 From: corellianimports at aol.com (Jason Poulin) Date: Wed, 5 Jan 2022 20:26:12 -0500 Subject: [Koha-devel] Dev meeting 5 January 2022 report In-Reply-To: <9b715b07-b2d6-1b80-362d-0d7f6ed5fc14@biblibre.com> References: <9b715b07-b2d6-1b80-362d-0d7f6ed5fc14@biblibre.com> Message-ID: <61EB5A58-0BDE-4669-9229-DF83B0749AD9@aol.com> Hi can someone take me off this list please I don’t know how I got on it thank you > On Jan 5, 2022, at 5:57 PM, Fridolin SOMERS wrote: > > Hi, > > Here is Dev meeting 5 January 2022 report : > https://wiki.koha-community.org/wiki/Development_IRC_meeting_5_January_2022 > > Next dev meeting : > https://wiki.koha-community.org/wiki/Development_IRC_meeting_19_January_2022 > > There is also a general meeting soon : > https://wiki.koha-community.org/wiki/General_IRC_meeting_12_January_2022 > > See you around :D > > Best regards, > > -- > Fridolin SOMERS > Software and system maintainer 🦄 > BibLibre, France > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From katrin.fischer.83 at web.de Thu Jan 6 14:35:35 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 6 Jan 2022 14:35:35 +0100 Subject: [Koha-devel] Dev meeting 5 January 2022 report In-Reply-To: <61EB5A58-0BDE-4669-9229-DF83B0749AD9@aol.com> References: <9b715b07-b2d6-1b80-362d-0d7f6ed5fc14@biblibre.com> <61EB5A58-0BDE-4669-9229-DF83B0749AD9@aol.com> Message-ID: Hi Jason, if you haven't received a reply yet from the list admin, you can unsubscribe yourself using the last option on this form: https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel Hope this helps, Katrin On 06.01.22 02:26, Jason Poulin wrote: > Hi can someone take me off this list please I don’t know how I got on it thank you > >> On Jan 5, 2022, at 5:57 PM, Fridolin SOMERS wrote: >> >> Hi, >> >> Here is Dev meeting 5 January 2022 report : >> https://wiki.koha-community.org/wiki/Development_IRC_meeting_5_January_2022 >> >> Next dev meeting : >> https://wiki.koha-community.org/wiki/Development_IRC_meeting_19_January_2022 >> >> There is also a general meeting soon : >> https://wiki.koha-community.org/wiki/General_IRC_meeting_12_January_2022 >> >> See you around :D >> >> Best regards, >> >> -- >> Fridolin SOMERS >> Software and system maintainer 🦄 >> BibLibre, France >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From tomascohen at gmail.com Thu Jan 6 16:19:45 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 6 Jan 2022 12:19:45 -0300 Subject: [Koha-devel] New class: Koha::Result::Boolean Message-ID: Hi all, happy 2022 :-D I wanted to mention that a bug that introduces Koha::Result::Boolean has been pushed [1]. This class provides a way to return an object, that evaluates to a boolean in (Perl's) bool context but also carries reasons for the result. It has been used in a couple places, like bug 29765 [2] and bug 29788 [3] (which still needs the QA step). [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29746 [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29765 [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29788 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu Jan 6 17:21:21 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 6 Jan 2022 13:21:21 -0300 Subject: [Koha-devel] Resultsets vs. list context Message-ID: Hi, let me tell you a short and (technical but) interesting story. Most of you might know about this, but I found it could be useful to know and/or to refresh. DBIC has a nice property that our Koha::Objects inherited (obviously): you can chain calls like this: Koha::Patrons->search( $filter_1 )->search( $filter_2 )->search( $filter_3 )->...; We recently agreed (not sure there is a coding guideline) that if we wanted to provide high-level methods to encapsulate such filters, we would call those methods 'filter_by_*' unless the context suggests a better name. So we could, in theory do something like: my $cool_old_books = Koha::Biblios->search( $some_initial_filter ) ->filter_by_older_than({ years => 30 }) ->filter_by_coolness(); So far, so good :-D But then, we have another (cool) method in Koha::Objects: _new_from_dbic. This method allows us to, given a DBIC relationship, convert the linked resultset into the proper Koha::Object(s)-based class. For example: my $patron_checkouts = $patron->checkouts; in this case, the actual code is pretty simple thanks to _new_from_dbic: sub checkouts { my ($self) = @_; my $checkouts = $self->_result->issues; return Koha::Checkouts->_new_from_dbic( $checkouts ); } Methods like ->search behave consistently to what DBIC does, and as such, they honor list context. This is: my $scalar = Koha::Patrons->search(filter); my @list = Koha::Patrons->search($filter); will do what you think: $scalar will be an object, representing a resultset, and @list will be the actually fetched list of results from the search, as a list. But there's a catch. And we need to be aware of that and there is an ongoing discussion about it: _new_from_dbic doesn't honor list context [1]. This means when you code, you need to go look if the method you're calling is _new_from_dbic-based, or ->search based [2]. This is not cool. @checkouts = $patron->checkouts; # doesn't do what you expect! @checkouts = $patron->checkouts->filter_by_overdue; # this does if ->search based. Our codebase is full of places in which we either call ->as_list in our resultsets (because something exploded if we didn't, for example): my @checkouts = $patron->checkouts->as_list; or in which we explicitly call `scalar the_thing' so we are sure things are evaluated in scalar context because we want the resultset instead (for example, when passing params to a template): $template->param( checkouts => scalar $patron->checkouts ); I proposed we make ->_new_from_dbic and ->empty honor list context and hence making our methods consistent (can be seen by the referenced bugs). But we found a nasty problem: calling methods in Template::Toolkit internally assigns them to a global stash which is implemented as a hash (a.k.a. list context :-D). So, you will find that 'some' things are calculated on the controller (.pl) scripts and then passed to the templates (to overcome this), and some others are calculated directly in the templates. Now you know the reason we've introduced those things over the years in the codebase. So, making _new_from_dbic honor list context, opens a big can of worms in the template front. We explored the idea of using a different Template::Toolkit stash, that honors scalar context, but the author has marked it as experimental, and it would still require changing many things in the templates. The tradeoff doesn't lean towards that path. The conclusion so far is that we should drop support for list context. Hence, my suggestion as developer and QA team member is: TL;DR Make use of ->as_list when you have a resultset really need list context like in: foreach my $item ( @{$items->as_list} ) { ... } grep { filter($_) } @{@libraries->as_list} my @biblios = $biblios->as_list; and so on. This will save you some headaches (in some cases) and will make your code survive this upcoming change. We should start enforcing this in the QA step as well, so adjust your code for this. Once we remove wantarray, things will explode on their own. Best regards [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28883 [2] There is also Koha::Objects->empty, actually. That presents the same problem as _new_from_dbic. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28871 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From corellianimports at aol.com Fri Jan 7 17:19:40 2022 From: corellianimports at aol.com (Jason Poulin) Date: Fri, 7 Jan 2022 11:19:40 -0500 Subject: [Koha-devel] New class: Koha::Result::Boolean In-Reply-To: References: Message-ID: Can someone take me off this list please > On Jan 7, 2022, at 10:52 AM, Tomas Cohen Arazi wrote: > >  > Hi all, happy 2022 :-D > > I wanted to mention that a bug that introduces Koha::Result::Boolean has been pushed [1]. This class provides a way to return an object, that evaluates to a boolean in (Perl's) bool context but also carries reasons for the result. > > It has been used in a couple places, like bug 29765 [2] and bug 29788 [3] (which still needs the QA step). > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29746 > [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29765 > [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29788 > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at hofstetter.at Sun Jan 9 17:14:40 2022 From: mark at hofstetter.at (Mark Hofstetter) Date: Sun, 9 Jan 2022 17:14:40 +0100 Subject: [Koha-devel] Listing as a Koha Support provider - https://koha-support.eu/ Message-ID: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> Hi, we are the HKS3 (Hofstetter, Klausner & Schmidt) OG and started providing support for koha about 1,5 years ago - and would like to be listed as "Koha Support provider" Company Name: HKS3 Contact Person: Mark Hofstetter Contact email: office at koha-support.eu Website: https://koha-support.eu/ Telephone: +43 676 7345660 this week our biggest project so far went live this weekend at: https://katalog.landesbibliothek.steiermark.at/ ( around 600k records) we are long time perl and database developers and want to (and already did) participate in the great & very welcoming koha-community some (and future) contributions https://github.com/HKS3/ cheers & thanks Mark From dcook at prosentient.com.au Mon Jan 10 02:32:05 2022 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 10 Jan 2022 12:32:05 +1100 Subject: [Koha-devel] Resultsets vs. list context In-Reply-To: References: Message-ID: <018501d805c1$e07683c0$a1638b40$@prosentient.com.au> That was really interesting. Sounds like a good call to me. I’ve never really been a fan of ‘wantarray’ black magic anyway. 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: Koha-devel On Behalf Of Tomas Cohen Arazi Sent: Friday, 7 January 2022 3:21 AM To: koha-devel Subject: [Koha-devel] Resultsets vs. list context Hi, let me tell you a short and (technical but) interesting story. Most of you might know about this, but I found it could be useful to know and/or to refresh. DBIC has a nice property that our Koha::Objects inherited (obviously): you can chain calls like this: Koha::Patrons->search( $filter_1 )->search( $filter_2 )->search( $filter_3 )->...; We recently agreed (not sure there is a coding guideline) that if we wanted to provide high-level methods to encapsulate such filters, we would call those methods 'filter_by_*' unless the context suggests a better name. So we could, in theory do something like: my $cool_old_books = Koha::Biblios->search( $some_initial_filter ) ->filter_by_older_than({ years => 30 }) ->filter_by_coolness(); So far, so good :-D But then, we have another (cool) method in Koha::Objects: _new_from_dbic. This method allows us to, given a DBIC relationship, convert the linked resultset into the proper Koha::Object(s)-based class. For example: my $patron_checkouts = $patron->checkouts; in this case, the actual code is pretty simple thanks to _new_from_dbic: sub checkouts { my ($self) = @_; my $checkouts = $self->_result->issues; return Koha::Checkouts->_new_from_dbic( $checkouts ); } Methods like ->search behave consistently to what DBIC does, and as such, they honor list context. This is: my $scalar = Koha::Patrons->search(filter); my @list = Koha::Patrons->search($filter); will do what you think: $scalar will be an object, representing a resultset, and @list will be the actually fetched list of results from the search, as a list. But there's a catch. And we need to be aware of that and there is an ongoing discussion about it: _new_from_dbic doesn't honor list context [1]. This means when you code, you need to go look if the method you're calling is _new_from_dbic-based, or ->search based [2]. This is not cool. @checkouts = $patron->checkouts; # doesn't do what you expect! @checkouts = $patron->checkouts->filter_by_overdue; # this does if ->search based. Our codebase is full of places in which we either call ->as_list in our resultsets (because something exploded if we didn't, for example): my @checkouts = $patron->checkouts->as_list; or in which we explicitly call `scalar the_thing' so we are sure things are evaluated in scalar context because we want the resultset instead (for example, when passing params to a template): $template->param( checkouts => scalar $patron->checkouts ); I proposed we make ->_new_from_dbic and ->empty honor list context and hence making our methods consistent (can be seen by the referenced bugs). But we found a nasty problem: calling methods in Template::Toolkit internally assigns them to a global stash which is implemented as a hash (a.k.a. list context :-D). So, you will find that 'some' things are calculated on the controller (.pl) scripts and then passed to the templates (to overcome this), and some others are calculated directly in the templates. Now you know the reason we've introduced those things over the years in the codebase. So, making _new_from_dbic honor list context, opens a big can of worms in the template front. We explored the idea of using a different Template::Toolkit stash, that honors scalar context, but the author has marked it as experimental, and it would still require changing many things in the templates. The tradeoff doesn't lean towards that path. The conclusion so far is that we should drop support for list context. Hence, my suggestion as developer and QA team member is: TL;DR Make use of ->as_list when you have a resultset really need list context like in: foreach my $item ( @{$items->as_list} ) { ... } grep { filter($_) } @{@libraries->as_list} my @biblios = $biblios->as_list; and so on. This will save you some headaches (in some cases) and will make your code survive this upcoming change. We should start enforcing this in the QA step as well, so adjust your code for this. Once we remove wantarray, things will explode on their own. Best regards [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28883 [2] There is also Koha::Objects->empty, actually. That presents the same problem as _new_from_dbic. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28871 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From wrobertson1981 at yahoo.co.nz Mon Jan 10 09:13:22 2022 From: wrobertson1981 at yahoo.co.nz (Waylon Robertson) Date: Mon, 10 Jan 2022 08:13:22 +0000 (UTC) Subject: [Koha-devel] Reusable barcode? References: <2119197562.871463.1641802402508.ref@mail.yahoo.com> Message-ID: <2119197562.871463.1641802402508@mail.yahoo.com> Is there a way to use a barcode multiple times, as a category/tag on checkin/out? A toy library would like to just have categories like 'Game', 'vehicle', 'book', etc, and to scan those, instead of barcoding each item individually. How would this work? -------------- next part -------------- An HTML attachment was scrubbed... URL: From oleonard at myacpl.org Mon Jan 10 13:09:48 2022 From: oleonard at myacpl.org (Owen Leonard) Date: Mon, 10 Jan 2022 07:09:48 -0500 Subject: [Koha-devel] Reusable barcode? In-Reply-To: <2119197562.871463.1641802402508@mail.yahoo.com> References: <2119197562.871463.1641802402508.ref@mail.yahoo.com> <2119197562.871463.1641802402508@mail.yahoo.com> Message-ID: > Is there a way to use a barcode multiple time Koha expects items to have unique barcodes. I don't think what you're describing is possible. Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From fridolin.somers at biblibre.com Tue Jan 11 10:14:53 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 10 Jan 2022 23:14:53 -1000 Subject: [Koha-devel] Reusable barcode? In-Reply-To: <2119197562.871463.1641802402508@mail.yahoo.com> References: <2119197562.871463.1641802402508.ref@mail.yahoo.com> <2119197562.871463.1641802402508@mail.yahoo.com> Message-ID: Hi, You may have a look at system preference "itemBarcodeFallbackSearch". It allows circulation of items without barcode. Best regards, Le 09/01/2022 à 22:13, Waylon Robertson a écrit : > Is there a way to use a barcode multiple times, as a category/tag on > checkin/out? A toy library would like to just have categories like > 'Game', 'vehicle', 'book', etc, and to scan those, instead of barcoding > each item individually. > > How would this work? > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Wed Jan 12 08:00:38 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 11 Jan 2022 21:00:38 -1000 Subject: [Koha-devel] General IRC Meeting 12 January 2022 Message-ID: See you at : https://wiki.koha-community.org/wiki/General_IRC_meeting_12_January_2022 -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From mik at adminkuhn.ch Wed Jan 12 17:17:13 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 12 Jan 2022 17:17:13 +0100 Subject: [Koha-devel] Can't locate object method "output_with_http_headers" via package "CGI" Message-ID: <982d4148-6daa-f646-b71e-f47d85980b84@adminkuhn.ch> Hi Our library uses a non-Koha Perl script to authenticate with Divibib Onleihe (a digital distributor like Overdrive). The script worked with Koha 18.05 but after the update to Debian 11 with Perl 5.032001 und Koha 21.11.01 the following error appears: Can't locate object method "output_with_http_headers" via package "CGI" at /usr/share/koha/opac/cgi-bin/opac/onleihe_auth.pl line 91. The script file actually contains these lines (among others): use CGI; use XML::Simple; use Koha::Patrons; use Koha::AuthUtils qw(hash_password); use Digest::MD5 qw(md5_base64); use C4::Output; use C4::Context; my $query = new CGI; ... output_with_http_headers $query, undef, $xml, 'xml'; Can anyone please give me a hint how to solve 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 at adminkuhn.ch · W www.adminkuhn.ch From jonathan.druart at bugs.koha-community.org Wed Jan 12 17:40:53 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 12 Jan 2022 17:40:53 +0100 Subject: [Koha-devel] Can't locate object method "output_with_http_headers" via package "CGI" In-Reply-To: <982d4148-6daa-f646-b71e-f47d85980b84@adminkuhn.ch> References: <982d4148-6daa-f646-b71e-f47d85980b84@adminkuhn.ch> Message-ID: use C4::Output qw( output_with_http_headers ) will fix it. See also the "Other" section of the tech release note from 21.11 (related to bug 17600) https://koha-community.org/koha-21-11-released/ Le mer. 12 janv. 2022 à 17:17, Michael Kuhn a écrit : > Hi > > Our library uses a non-Koha Perl script to authenticate with Divibib > Onleihe (a digital distributor like Overdrive). The script worked with > Koha 18.05 but after the update to Debian 11 with Perl 5.032001 und Koha > 21.11.01 the following error appears: > > Can't locate object method "output_with_http_headers" via package > "CGI" at /usr/share/koha/opac/cgi-bin/opac/onleihe_auth.pl line 91. > > The script file actually contains these lines (among others): > > use CGI; > use XML::Simple; > use Koha::Patrons; > use Koha::AuthUtils qw(hash_password); > use Digest::MD5 qw(md5_base64); > use C4::Output; > use C4::Context; > my $query = new CGI; > ... > output_with_http_headers $query, undef, $xml, 'xml'; > > Can anyone please give me a hint how to solve 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 at adminkuhn.ch · W www.adminkuhn.ch > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Wed Jan 12 23:05:31 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 12 Jan 2022 12:05:31 -1000 Subject: [Koha-devel] Can't locate object method "output_with_http_headers" via package "CGI" In-Reply-To: References: <982d4148-6daa-f646-b71e-f47d85980b84@adminkuhn.ch> Message-ID: Hi, Also avoid this syntax : my $query = new CGI; Prefer : my $query = CGI->new; See Bug 25898: Prohibit indirect object notation Best regards, Le 12/01/2022 à 06:40, Jonathan Druart a écrit : > use C4::Output qw( output_with_http_headers ) > > will fix it. See also the "Other" section of the tech release note from > 21.11 (related to bug 17600) > https://koha-community.org/koha-21-11-released/ > > > Le mer. 12 janv. 2022 à 17:17, Michael Kuhn > a écrit : > > Hi > > Our library uses a non-Koha Perl script to authenticate with Divibib > Onleihe (a digital distributor like Overdrive). The script worked with > Koha 18.05 but after the update to Debian 11 with Perl 5.032001 und > Koha > 21.11.01 the following error appears: > >   Can't locate object method "output_with_http_headers" via package > "CGI" at /usr/share/koha/opac/cgi-bin/opac/onleihe_auth.pl > line 91. > > The script file actually contains these lines (among others): > >   use CGI; >   use XML::Simple; >   use Koha::Patrons; >   use Koha::AuthUtils qw(hash_password); >   use Digest::MD5 qw(md5_base64); >   use C4::Output; >   use C4::Context; >   my $query = new CGI; >   ... >   output_with_http_headers $query, undef, $xml, 'xml'; > > Can anyone please give me a hint how to solve 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 at adminkuhn.ch > · W www.adminkuhn.ch > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Wed Jan 12 23:22:15 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 12 Jan 2022 12:22:15 -1000 Subject: [Koha-devel] [Koha] Opening bids for KohaCon22 In-Reply-To: References: Message-ID: Hello dear world-wide community. Limit date is over and unfortunately we have no proposals. https://wiki.koha-community.org/wiki/KohaCon22_Proposals Community agreed to extend the end date to February 28. World-wide situation is still chaotic so an entirely online event can be proposed. This will not impact the next years continental rotation. https://wiki.koha-community.org/wiki/Processes_for_KohaCons#Continent_rotation I hope we can all be together around our common project. Long live Koha. Fridolin Somers, BibLibre France, actual release manager. Le 18/11/2021 à 03:24, Katrin Fischer a écrit : > Hello dear Koha community, > > another year is coming to an end. It's time to turn our attention to the > new year that's coming up, full of possibilities! > > If you or your organization would like to organize KohaCon22, please > enter all relevant information on this wiki page: > https://wiki.koha-community.org/wiki/KohaCon22_Proposals (if you do not > already have an account to edit the wiki, you can request one, it is > usually pretty fast to get access). > > The community has agreed that KohaCon conferences must be either hybrid > with an in-person conference streamed online, or entirely online. Apart > from keeping the community members safe, this will also allow for > greater accessibility, so that everyone can attend and learn from each > other no matter their availability, ability to travel, or budget. > > Know that the community stands behind anyone who volunteers to organize > and that help is always available if you're unsure how to proceed. > > Call for proposals will end on January 8, 2022 at 23:59 UTC. If there is > more than one proposal, we will organize a vote, which will be announced > on this mailing list. > > Best regards, > > > Katrin > _______________________________________________ > > Koha mailing list  http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From mik at adminkuhn.ch Thu Jan 13 09:45:31 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Thu, 13 Jan 2022 09:45:31 +0100 Subject: [Koha-devel] Call for news - Newsletter January 2022 Message-ID: <59c197d1-07ad-eb6e-e9b4-5dfbf22d36d3@adminkuhn.ch> Hi I'm collecting news for the January 2022 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 -- 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 at adminkuhn.ch · W www.adminkuhn.ch From mik at adminkuhn.ch Thu Jan 13 11:52:21 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Thu, 13 Jan 2022 11:52:21 +0100 Subject: [Koha-devel] Can't locate object method "output_with_http_headers" via package "CGI" In-Reply-To: References: <982d4148-6daa-f646-b71e-f47d85980b84@adminkuhn.ch> Message-ID: Hi Jonathan and Fridolin You wrote: > use C4::Output qw( output_with_http_headers ) > > will fix it. Thank you very much, this was the solution! Now our script again works as intended. > See also the "Other" section of the tech release note from > 21.11 (related to bug 17600) > https://koha-community.org/koha-21-11-released/ Unfortunately I didn't understand very much of the information there. > Also avoid this syntax : > my $query = new CGI; > > Prefer : > my $query = CGI->new; > > See Bug 25898: Prohibit indirect object notation I have changed this line, thanks for the suggestion! 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 at adminkuhn.ch · W www.adminkuhn.ch Am 12.01.22 um 17:40 schrieb Jonathan Druart: > use C4::Output qw( output_with_http_headers ) > > will fix it. See also the "Other" section of the tech release note from > 21.11 (related to bug 17600) > https://koha-community.org/koha-21-11-released/ > > > Le mer. 12 janv. 2022 à 17:17, Michael Kuhn > a écrit : > > Hi > > Our library uses a non-Koha Perl script to authenticate with Divibib > Onleihe (a digital distributor like Overdrive). The script worked with > Koha 18.05 but after the update to Debian 11 with Perl 5.032001 und > Koha > 21.11.01 the following error appears: > >   Can't locate object method "output_with_http_headers" via package > "CGI" at /usr/share/koha/opac/cgi-bin/opac/onleihe_auth.pl > line 91. > > The script file actually contains these lines (among others): > >   use CGI; >   use XML::Simple; >   use Koha::Patrons; >   use Koha::AuthUtils qw(hash_password); >   use Digest::MD5 qw(md5_base64); >   use C4::Output; >   use C4::Context; >   my $query = new CGI; >   ... >   output_with_http_headers $query, undef, $xml, 'xml'; > > Can anyone please give me a hint how to solve 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 at adminkuhn.ch > · W www.adminkuhn.ch > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > From katrin.fischer.83 at web.de Sat Jan 15 12:39:02 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sat, 15 Jan 2022 12:39:02 +0100 Subject: [Koha-devel] Listing as a Koha Support provider - https://koha-support.eu/ In-Reply-To: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> References: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> Message-ID: Hi Mark, great news about your project! I have added your entry to the Koha support providers list. Please check it and let me know if any changes need to be made. Best wishes, Katrin On 09.01.22 17:14, Mark Hofstetter wrote: > Hi, > > we are the HKS3 (Hofstetter, Klausner & Schmidt) OG and started > providing support for koha about 1,5 years ago - and would like to be > listed as "Koha Support provider" > >    Company Name: HKS3 > >    Contact Person: Mark Hofstetter > >    Contact email: office at koha-support.eu > >    Website: https://koha-support.eu/ > >    Telephone: +43 676 7345660 > > this week our biggest project so far went live this weekend at: > > https://katalog.landesbibliothek.steiermark.at/ > > ( around 600k records) > > we are long time perl and database developers and want to (and already > did) participate in the great & very welcoming koha-community > > some (and future) contributions > > https://github.com/HKS3/ > > cheers & thanks > > Mark > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From victor at tuxayo.net Tue Jan 18 01:48:01 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Tue, 18 Jan 2022 01:48:01 +0100 Subject: [Koha-devel] Time to translate: string freeze to prepare Koha 20.11.14 has begun Message-ID: Hi, String freeze is into effect as of now for the 20.11.x maintenance branch. 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 20.11, then you must also copy it to 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo From chris at bigballofwax.co.nz Tue Jan 18 10:15:43 2022 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Tue, 18 Jan 2022 22:15:43 +1300 Subject: [Koha-devel] Listing as a Koha Support provider - https://koha-support.eu/ In-Reply-To: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> References: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> Message-ID: Hi Mark Great to have you as part of the community. It's always great to have more perl programmers join the community. I look forward to your future contributions, and covid willing to meet you at a future Kohacon Chris On Mon, 10 Jan 2022, 5:14 am Mark Hofstetter, wrote: > Hi, > > we are the HKS3 (Hofstetter, Klausner & Schmidt) OG and started > providing support for koha about 1,5 years ago - and would like to be > listed as "Koha Support provider" > > Company Name: HKS3 > > Contact Person: Mark Hofstetter > > Contact email: office at koha-support.eu > > Website: https://koha-support.eu/ > > Telephone: +43 676 7345660 > > this week our biggest project so far went live this weekend at: > > https://katalog.landesbibliothek.steiermark.at/ > > ( around 600k records) > > we are long time perl and database developers and want to (and already > did) participate in the great & very welcoming koha-community > > some (and future) contributions > > https://github.com/HKS3/ > > cheers & thanks > > Mark > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Tue Jan 18 11:21:47 2022 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 18 Jan 2022 11:21:47 +0100 Subject: [Koha-devel] hackfest in Marseille !!! Message-ID: Hello world ! According to my announced agenda, BibLibre is supposed to invite you for a Koha hackfest in Marseille, March 28th - April 1st. The pandemic is at a high level now, but specialist are optimistic for the next quarter. So, I'd like to be optimistic too and say : "OK, let's do it ! we'll meet in Marseille in late March". As usual : the hackfest is open to anyone willing to contribute to Koha, not only to developers: librarians are warmly welcomed and can contribute a lot ! It's a hackfest so no schedule, we decide day after day who work on what. If you can't join us for the whole week, that's OK, but joining 2 days is a minimum, 3 days being better (and 5 days the best, of course ;) ) And as usual, there will be the legendary French cheese lunch ;) If you want to join, just drop me an email ! -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries From fridolin.somers at biblibre.com Tue Jan 18 19:27:56 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 18 Jan 2022 08:27:56 -1000 Subject: [Koha-devel] Listing as a Koha Support provider - https://koha-support.eu/ In-Reply-To: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> References: <119cd511-ddcd-d58f-d7fb-932b6c34d155@hofstetter.at> Message-ID: Hi, As actual Release Manager, I give you a warm welcome. Perl skills are much appreciated. Helping with translation is also a good start : https://wiki.koha-community.org/wiki/Translating_Koha Nice Koha plugins ;) You may add the topic koha-plugin to them : https://github.com/topics/koha-plugin I see : minimum_version => '19.05.00.000' Version must be a number so prefer '19.05'. You may change the repo to add dirs Koha/Plugin/HKS3SubordinateItems, it allows running the plugin from git repo. Also allows to build KPZ with a simple zip command. See for example https://github.com/biblibre/koha-plugin-opac-matomo Best regards, Le 09/01/2022 à 06:14, Mark Hofstetter a écrit : > Hi, > > we are the HKS3 (Hofstetter, Klausner & Schmidt) OG and started > providing support for koha about 1,5 years ago - and would like to be > listed as "Koha Support provider" > >    Company Name: HKS3 > >    Contact Person: Mark Hofstetter > >    Contact email: office at koha-support.eu > >    Website: https://koha-support.eu/ > >    Telephone: +43 676 7345660 > > this week our biggest project so far went live this weekend at: > > https://katalog.landesbibliothek.steiermark.at/ > > ( around 600k records) > > we are long time perl and database developers and want to (and already > did) participate in the great & very welcoming koha-community > > some (and future) contributions > > https://github.com/HKS3/ > > cheers & thanks > > Mark > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From wainuiwitikapark at catalyst.net.nz Wed Jan 19 00:37:17 2022 From: wainuiwitikapark at catalyst.net.nz (Wainui Witika-Park) Date: Wed, 19 Jan 2022 12:37:17 +1300 Subject: [Koha-devel] Time to translate: string freeze to prepare Koha 19.11.25 has begun Message-ID: Hello, String freeze is into effect as of now for the 19.11.x maintenance branch in preparation for the 19.11.25 release. The minor release is scheduled for January 24. 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.11, 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating! Wainui Witika-Park (she/her) From oleonard at myacpl.org Wed Jan 19 18:52:18 2022 From: oleonard at myacpl.org (Owen Leonard) Date: Wed, 19 Jan 2022 12:52:18 -0500 Subject: [Koha-devel] Staff interface redesign: Update Message-ID: As Paul announced in December (https://lists.koha-community.org/pipermail/koha-devel/2021-December/046841.html) Biblibre is sponsoring a refresh of the staff interface design. They have hired a graphic designer, Thibaud Petit, to create some proposals, and will have an intern starting in February who will be able to devote six months to assisting in the implementation. Yesterday we had our first meeting: Paul, me, Thibaud, Mark Gavillet of PTFS-Europe, Lucas Gass of ByWater Solutions, and Brooke Johnson, friend of Koha. We discussed the possibilities and the difficulties involved in the task and talked about the possible scope of the changes. Some major points: - Style can be "easily" affected by global CSS changes. We've done this before, 10 years ago (!) with Bug 7979, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7979 - The scope of other changes will be limited by the difficulty involved in making global changes to the many staff interface templates. The opportunity is there to implement some global changes via global includes, e.g. header, footer, sidebar menus. - I hope that we can have an upgrade to jQuery before the implementation starts, and an upgrade to Bootstrap either before or as part of the redesign. - We have not instructed Thibaud to limit his proposals to the green color scheme we currently associate with Koha. We hope to review some design proposals in two weeks on February first. Thanks to everyone who participated, and thanks especially to Paul and Biblibre for spearheading this effort! -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From jonathan.druart at bugs.koha-community.org Wed Jan 19 19:44:55 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 19 Jan 2022 19:44:55 +0100 Subject: [Koha-devel] Staff interface redesign: Update In-Reply-To: References: Message-ID: Can we make propositions or submit ideas? I'd like a dark theme :-) Le mer. 19 janv. 2022 à 18:52, Owen Leonard a écrit : > As Paul announced in December > ( > https://lists.koha-community.org/pipermail/koha-devel/2021-December/046841.html > ) > Biblibre is sponsoring a refresh of the staff interface design. They > have hired a graphic designer, Thibaud Petit, to create some > proposals, and will have an intern starting in February who will be > able to devote six months to assisting in the implementation. > > Yesterday we had our first meeting: Paul, me, Thibaud, Mark Gavillet > of PTFS-Europe, Lucas Gass of ByWater Solutions, and Brooke Johnson, > friend of Koha. > > We discussed the possibilities and the difficulties involved in the > task and talked about the possible scope of the changes. Some major > points: > > - Style can be "easily" affected by global CSS changes. We've done > this before, 10 years ago (!) with Bug 7979, > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7979 > > - The scope of other changes will be limited by the difficulty > involved in making global changes to the many staff interface > templates. The opportunity is there to implement some global changes > via global includes, e.g. header, footer, sidebar menus. > > - I hope that we can have an upgrade to jQuery before the > implementation starts, and an upgrade to Bootstrap either before or as > part of the redesign. > > - We have not instructed Thibaud to limit his proposals to the green > color scheme we currently associate with Koha. > > We hope to review some design proposals in two weeks on February first. > > Thanks to everyone who participated, and thanks especially to Paul and > Biblibre for spearheading this effort! > > -- Owen > > -- > Web Developer > Athens County Public Libraries > (740) 737-6006 > https://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bibliwho at gmail.com Wed Jan 19 20:01:44 2022 From: bibliwho at gmail.com (Cab Vinton) Date: Wed, 19 Jan 2022 14:01:44 -0500 Subject: [Koha-devel] Staff interface redesign: Update In-Reply-To: References: Message-ID: If there's a time that makes sense for end-users to chime in, let me know. I know less is more at certain project stages. I'm sure there'll be interest among librarians to provide feedback when the timing's right. All best, Cab Vinton, Director Plaistow Public Library Plaistow, NH From samu.heiskanen at hypernova.fi Wed Jan 19 20:30:50 2022 From: samu.heiskanen at hypernova.fi (Samu Heiskanen) Date: Wed, 19 Jan 2022 21:30:50 +0200 (EET) Subject: [Koha-devel] How to install Koha plugins for development Message-ID: Hi, I am a new Koha developer from windy and cold Finland. As new to the Koha-community, I'd like to wish all the best for everyone in the community. I have a problem with installing Koha plugins. I tried to find guidelines how install plugin from Git-repository, but haven't found. I'm forking a plugin and setting up an environment for development and testing. What is the the preferred way to install plugin from Git? Best Regards, Samu Heiskanen From michael.hafen at washk12.org Wed Jan 19 21:37:28 2022 From: michael.hafen at washk12.org (Michael Hafen (TECH)) Date: Wed, 19 Jan 2022 13:37:28 -0700 Subject: [Koha-devel] How to install Koha plugins for development In-Reply-To: References: Message-ID: The way I do it is: add a directory to the koha-conf.xml with a tag, that will be where I `git clone` the plugins. `git pull` as necessary, then `koha-shell [instance] -c /usr/local/koha_source/misc/devel/ install_plugins.pl` That's with the koha instance running from the koha_source directory in dev_mode. On Wed, Jan 19, 2022 at 12:30 PM Samu Heiskanen wrote: > Hi, > > I am a new Koha developer from windy and cold Finland. As new to the > Koha-community, I'd like to wish all the best for everyone in the community. > > I have a problem with installing Koha plugins. I tried to find guidelines > how install plugin from Git-repository, but haven't found. I'm forking a > plugin and setting up an environment for development and testing. What is > the the preferred way to install plugin from Git? > > Best Regards, > > Samu Heiskanen > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Michael Hafen Washington County School District Technology Department Systems Analyst -------------- next part -------------- An HTML attachment was scrubbed... URL: From samu.heiskanen at hypernova.fi Wed Jan 19 22:18:26 2022 From: samu.heiskanen at hypernova.fi (Samu Heiskanen) Date: Wed, 19 Jan 2022 23:18:26 +0200 (EET) Subject: [Koha-devel] How to install Koha plugins for development In-Reply-To: Message-ID: Thanks, Michael! On Wed, 19 Jan 2022 13:37:28 -0700, "Michael Hafen (TECH)" wrote: > The way I do it is: > add a directory to the koha-conf.xml with a tag, that will be > where I `git clone` the plugins. > `git pull` as necessary, then > `koha-shell [instance] -c /usr/local/koha_source/misc/devel/ > install_plugins.pl` > > That's with the koha instance running from the koha_source directory in > dev_mode. > > > On Wed, Jan 19, 2022 at 12:30 PM Samu Heiskanen > wrote: > > > Hi, > > > > I am a new Koha developer from windy and cold Finland. As new to the > > Koha-community, I'd like to wish all the best for everyone in the community. > > > > I have a problem with installing Koha plugins. I tried to find guidelines > > how install plugin from Git-repository, but haven't found. I'm forking a > > plugin and setting up an environment for development and testing. What is > > the the preferred way to install plugin from Git? > > > > Best Regards, > > > > Samu Heiskanen > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > > > -- > Michael Hafen > Washington County School District Technology Department > Systems Analyst From tomascohen at gmail.com Thu Jan 20 01:57:55 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 19 Jan 2022 21:57:55 -0300 Subject: [Koha-devel] How to install Koha plugins for development In-Reply-To: References: Message-ID: You should use koha-testing-docker, there's an alias specifically for that. Once you use it, the instructions Michael have you are similar! El mié., 19 ene. 2022 16:31, Samu Heiskanen escribió: > Hi, > > I am a new Koha developer from windy and cold Finland. As new to the > Koha-community, I'd like to wish all the best for everyone in the community. > > I have a problem with installing Koha plugins. I tried to find guidelines > how install plugin from Git-repository, but haven't found. I'm forking a > plugin and setting up an environment for development and testing. What is > the the preferred way to install plugin from Git? > > Best Regards, > > Samu Heiskanen > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Thu Jan 20 07:26:16 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 19 Jan 2022 20:26:16 -1000 Subject: [Koha-devel] How to install Koha plugins for development In-Reply-To: References: Message-ID: <853e178c-b94a-125f-9f36-d4bbcf04cabd@biblibre.com> Hi, Plugins are great :D Note that git repo must contain dirs Koha/Plugin/xxx For example add /home/koha/plugins/koha-plugin-opac-matomo for plugin https://github.com/biblibre/koha-plugin-opac-matomo For some plugins you may have to patch to set version. For example https://github.com/bywatersolutions/koha-plugin-coverflow Replace in Koha/Plugin/Com/ByWaterSolutions/CoverFlow.pm : our $VERSION = "{VERSION}"; Don't forget to restart plack after each code change. Re-run misc/devel/install_plugins.pl if you implement a new hook in your plugin. You may look at https://github.com/bywatersolutions/dev-koha-plugin-kitchen-sink to see examples of implemtation. Best regards 🦄 Le 19/01/2022 à 11:18, Samu Heiskanen a écrit : > > Thanks, Michael! > > > On Wed, 19 Jan 2022 13:37:28 -0700, "Michael Hafen (TECH)" wrote: > >> The way I do it is: >> add a directory to the koha-conf.xml with a tag, that will be >> where I `git clone` the plugins. >> `git pull` as necessary, then >> `koha-shell [instance] -c /usr/local/koha_source/misc/devel/ >> install_plugins.pl` >> >> That's with the koha instance running from the koha_source directory in >> dev_mode. >> >> >> On Wed, Jan 19, 2022 at 12:30 PM Samu Heiskanen >> wrote: >> >>> Hi, >>> >>> I am a new Koha developer from windy and cold Finland. As new to the >>> Koha-community, I'd like to wish all the best for everyone in the community. >>> >>> I have a problem with installing Koha plugins. I tried to find guidelines >>> how install plugin from Git-repository, but haven't found. I'm forking a >>> plugin and setting up an environment for development and testing. What is >>> the the preferred way to install plugin from Git? >>> >>> Best Regards, >>> >>> Samu Heiskanen >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at 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/ >>> >> >> >> -- >> Michael Hafen >> Washington County School District Technology Department >> Systems Analyst > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From paul.poulain at biblibre.com Thu Jan 20 09:18:35 2022 From: paul.poulain at biblibre.com (Paul Poulain) Date: Thu, 20 Jan 2022 09:18:35 +0100 Subject: [Koha-devel] Staff interface redesign: Update In-Reply-To: References: Message-ID: <04ba3823-2871-ea7f-da1c-8c5150a1af4a@biblibre.com> Hi Cab, Of course end users are more than welcomed ! I agree that we need not to be too many, but a end user, that's a great idea ! I'll add you to our next meeting invitation, you should get an email. Le 19/01/2022 à 20:01, Cab Vinton a écrit : > If there's a time that makes sense for end-users to chime in, let me know. > > I know less is more at certain project stages. I'm sure there'll be > interest among librarians to provide feedback when the timing's right. > > All best, > > Cab Vinton, Director > Plaistow Public Library > Plaistow, NH > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries From jonathan.druart at bugs.koha-community.org Tue Jan 25 11:49:09 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 25 Jan 2022 11:49:09 +0100 Subject: [Koha-devel] Loosing owner permissions under koha-testing-docker (solution) Message-ID: Hi devs, If you are using koha-testing-docker and you write patches, you certainly also use the koha-qa.pl script (alias `qa`). That may cause you permission problems. There is a workaround I explained on https://gitlab.com/koha-community/qa-test-tools/-/issues/57 Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Jan 25 14:07:16 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 25 Jan 2022 10:07:16 -0300 Subject: [Koha-devel] Loosing owner permissions under koha-testing-docker (solution) In-Reply-To: References: Message-ID: What I do is running the qa script within the kshell. We should add an alias there. El mar., 25 ene. 2022 7:49, Jonathan Druart < jonathan.druart at bugs.koha-community.org> escribió: > Hi devs, > > If you are using koha-testing-docker and you write patches, you certainly > also use the koha-qa.pl script (alias `qa`). > That may cause you permission problems. > > There is a workaround I explained on > https://gitlab.com/koha-community/qa-test-tools/-/issues/57 > > Cheers, > Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Jan 27 00:38:51 2022 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 27 Jan 2022 10:38:51 +1100 Subject: [Koha-devel] Loosing owner permissions under koha-testing-docker (solution) In-Reply-To: References: Message-ID: <048501d8130d$e031c3d0$a0954b70$@prosentient.com.au> I’ve commented on the Gitlab issue but I think what Tomas suggests is a good way to go. 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: Koha-devel On Behalf Of Tomas Cohen Arazi Sent: Wednesday, 26 January 2022 12:07 AM To: Jonathan Druart Cc: koha-devel Subject: Re: [Koha-devel] Loosing owner permissions under koha-testing-docker (solution) What I do is running the qa script within the kshell. We should add an alias there. El mar., 25 ene. 2022 7:49, Jonathan Druart > escribió: Hi devs, If you are using koha-testing-docker and you write patches, you certainly also use the koha-qa.pl script (alias `qa`). That may cause you permission problems. There is a workaround I explained on https://gitlab.com/koha-community/qa-test-tools/-/issues/57 Cheers, Jonathan _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Sun Jan 30 21:45:49 2022 From: kohanews at gmail.com (Koha Newsletter) Date: Sun, 30 Jan 2022 21:45:49 +0100 Subject: [Koha-devel] Koha Community Newsletter: January 2022 Message-ID: The Koha Community Newsletter for January 2022 is here: https://koha-community.org/koha-community-newsletter-january-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 -------------- next part -------------- An HTML attachment was scrubbed... URL: