Mailing lists matching lists.koha-community.org
koha-bugs lists.koha-community.orgkoha-devel lists.koha-community.org
Re: [Koha-devel] Plugin hooks on datas and store()
should allow you to modify the item, > unless we > > > need a "pre store" hook. > > > I had a look at the code and I didn't find any problems. > > > Fridolin, what did you try exactly, can you share the code? > > > > > > Le lun. 8 mars 2021 à 11:17, Tomas Cohen Arazi > > mailto:tomasco...@gmail.com> <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>> > <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com> <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>>> > > > <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com> <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>> > <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com> <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>>>>> a > > écrit : > > > > > > Maybe you need some other hook. Ones that allows you > to make > > changes > > > to the object right before it is stored instead of > this one, that > > > gets the 'just updated' object. > > > When I added 'after' hooks for biblios and items > actions, the > > idea > > > was that they should act as triggers for other > actions: in my > > case, > > > fill a zebraqueue-ish table my plugin uses. > > > > > > El lun, 8 mar 2021 a las 5:11, Fridolin SOMERS > > > (mailto:fridolin.som...@biblibre.com> > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com>> > > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com> > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com>>> > > > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com> > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com>> > > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com> > <mailto:fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com>>>>>) escribió: > > > > > > Hi, > > > > > > While testing new hook : > > > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>> > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>> > > > > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>> > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>>> > > > > > > I faced a problem : > > > How can I modify the current patron object ? > > > Since we are in the store() method of that object and > > inside a > > > transation. > > > I tried to call $self->SUPER::store(); but does > not work. > > > > > > Should we i
Re: [Koha-devel] [SIGNED_OFF] labels
+1 for the cases where all patches are signed off.
I think there might be a lot of our documentation describing adding the
[SIGNED OFF] label - could we additionally teach git bz to ignore those
and obsolete correctly?
On 25.08.2017 13:58, Barton Chittenden wrote:
I think that there's an alias in the gitconfig on kohadevbox (among
other places) that adds the [SIGNED_OFF] label. This is from my
gitconfig on a different box, but kohadevbox has something similar IIRC:
[alias]
so = "!f() { c=`expr $1 - 1`; git filter-branch -f --msg-filter
\"echo -n \\\"[SIGNED-OFF] \\\" && cat && echo \\\"\nSigned-off-by:
Barton Chittenden <mailto:bar...@bywatersolutions.com>>\\\"\" HEAD~$c^..; }; f"
On Fri, Aug 25, 2017 at 6:17 AM, Tomas Cohen Arazi
mailto:tomasco...@gmail.com>> wrote:
+1
On vie., 25 de ago. de 2017 4:07 AM Marc Véron mailto:ve...@veron.ch>> wrote:
+1
Am 25.08.2017 um 08:52 schrieb David Cook:
+1
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:*koha-devel-boun...@lists.koha-community.org
<mailto:koha-devel-boun...@lists.koha-community.org>
[mailto:koha-devel-boun...@lists.koha-community.org
<mailto:koha-devel-boun...@lists.koha-community.org>] *On
Behalf Of *Marcel de Rooy
*Sent:* Friday, 25 August 2017 4:29 PM
*To:* Koha-devel
<mailto:koha-devel@lists.koha-community.org>
*Subject:* [Koha-devel] [SIGNED_OFF] labels
Hi all,
I would favor stopping the use of adding [SIGNED_OFF] labels
to patches when it is not strictly needed (which normally is
the case).
Only when (exceptionally) a few patches are signed and a few
are not on one report, I could see its use.
At this moment they need to be obsoleted manually with git bz.
Can we stop adding them ?
Marcel
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website :http://www.koha-community.org/
git :http://git.koha-community.org/
bugs :http://bugs.koha-community.org/ <http://bugs.koha-community.org/>
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
<http://bugs.koha-community.org/>
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
<http://bugs.koha-community.org/>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plugin hooks on datas and store()
<mailto:fridolin.som...@biblibre.com>>>>) escribió:
> >
> > Hi,
> >
> > While testing new hook :
> >
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>
>
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>
> >
>
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>
>
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>>
> >
> > I faced a problem :
> > How can I modify the current patron object ?
> > Since we are in the store() method of that object and
> inside a
> > transation.
> > I tried to call $self->SUPER::store(); but does
not work.
> >
> > Should we implement this possiblity or document
hooks to
> say it is
> > impossible.
> >
> > Thanks a lot for your help :D
> >
> > Best regards,
> >
> > --
> > Fridolin SOMERS mailto:fridolin.som...@biblibre.com>
> <mailto:fridolin.som...@biblibre.com
<mailto:fridolin.som...@biblibre.com>>
> > <mailto:fridolin.som...@biblibre.com
<mailto:fridolin.som...@biblibre.com>
> <mailto:fridolin.som...@biblibre.com
<mailto:fridolin.som...@biblibre.com>>>>
> > Software and system maintainer 🦄
> > BibLibre, France
> > ___
> > Koha-devel mailing list
> > Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
> <mailto:Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>>
> > <mailto:Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
> <mailto:Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>>>
> >
>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
>
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>>
> >
>
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>>>
> > website : https://www.koha-community.org/
<https://www.koha-community.org/>
> <https://www.koha-community.org/
<https://www.koha-community.org/>>
> > <https://www.koha-community.org/
<https://www.koha-community.org/>
> <https://www.koha-community.org/
<https://www.koha-community.org/>>>
> > git : https://git.koha-community.org/
<https://git.koha-community.org/>
> <https://git.koha-community.org/
<https://git.koha-community.org/>>
> > <https://git.koha-community.org/
<https://git.koha-community.org/>
> <https://git.koha-community.org/
<https://git.koha-community.org/>>>
> > bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
> <https://bugs.koha-community.org/
<https://bugs.koha-community.org/>>
> > <https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
> <https://bugs.koha-community.org/
<https://bugs.koha-community.org/>>>
> >
> >
> >
> > --
> > Tomás Cohen Arazi
> > Theke Solutions (http://theke.io <http://theke.io>
<http://theke.io <http://theke.io>
Re: [Koha-devel] Plugin hooks on datas and store()
; > > > <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com> > > <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>>>> a > > > écrit : > > > > > > > > Maybe you need some other hook. Ones that allows you > > to make > > > changes > > > > to the object right before it is stored instead of > > this one, that > > > > gets the 'just updated' object. > > > > When I added 'after' hooks for biblios and items > > actions, the > > > idea > > > > was that they should act as triggers for other > > actions: in my > > > case, > > > > fill a zebraqueue-ish table my plugin uses. > > > > > > > > El lun, 8 mar 2021 a las 5:11, Fridolin SOMERS > > > > ( > <mailto:fridolin.som...@biblibre.com> > > > <mailto:fridolin.som...@biblibre.com > > <mailto:fridolin.som...@biblibre.com>> > > > > <mailto:fridolin.som...@biblibre.com > > <mailto:fridolin.som...@biblibre.com> > > > <mailto:fridolin.som...@biblibre.com > > <mailto:fridolin.som...@biblibre.com>>>>) escribió: > > > > > > > > Hi, > > > > > > > > While testing new hook : > > > > > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066> > > > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>> > > > > > > > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066> > > > > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 > > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>> > > > > > > > > I faced a problem : > > > > How can I modify the current patron object ? > > > > Since we are in the store() method of that object > and > > > inside a > > > > transation. > > > > I tried to call $self->SUPER::store(); but does > > not work. > > > > > > > > Should we implement this possiblity or document > > hooks to > > > say it is > > > > impossible. > > > > > > > > Thanks a lot for your help :D > > > > > > > > Best regards, > > > > > > > > -- > > > > Fridolin SOMERS > <mailto:fridolin.som...@biblibre.com> > > > <mailto:fridolin.som...@biblibre.com > > <mailto:fridolin.som...@biblibre.com>> > > > > <mailto:fridolin.som...@biblibre.com > > <mailto:fridolin.som...@biblibre.com> > > > <mailto:fridolin.som...@biblibre.com > > <mailto:fridolin.som...@biblibre.com>>>> > > > > Software and system maintainer 🦄 > > > > BibLibre, France > > > > ___ > > > > Koha-devel mailing list > > > > Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org> > > > <mailto:Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org>> > > > > <mailto:Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org> > > > <mailto:Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org>>> > > > > > > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > < > https://lists.koha-co
Re: [Koha-devel] Removal of the prog and CCSR themes in 3.18
+1 for removing these deprecated themes.. Please do not remove prog at the staff side :) Van: koha-devel-boun...@lists.koha-community.org [koha-devel-boun...@lists.koha-community.org] namens Nicole Engard [neng...@gmail.com] Verzonden: dinsdag 13 mei 2014 20:32 Aan: Fridolin SOMERS CC: Koha Devel Onderwerp: Re: [Koha-devel] Removal of the prog and CCSR themes in 3.18 +1 for removal On Tue, May 13, 2014 at 7:11 AM, Fridolin SOMERS mailto:fridolin.som...@biblibre.com>> wrote: +1 for removal. Boostrap is great, long lives Boostrap. Le 13/05/2014 08:40, Marc Véron a écrit : +1 for removal Marc --- marc veron ag informatik information internet Baslerstrasse 50 CH - 4123 Allschwil +41 61 483 84 61 www.veron.ch<http://www.veron.ch> Acrobat / PDF - Lösungen seit 1995 Partner für Internet und Content Management Mitglied Koha Support Schweiz www.koha-support.ch<http://www.koha-support.ch> Am 12.05.2014 22:46, schrieb Chris Cormack: +1 from me ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com<mailto:fridolin.som...@biblibre.com> ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] 0000-00-00 is expired?
Sounds to me like NULL was meant ? Using -12-31 resulted in expensive date calculations previously. Van: koha-devel-boun...@lists.koha-community.org namens Jonathan Druart Verzonden: woensdag 14 februari 2018 16:41 Aan: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] -00-00 is expired? Great news then :) Sophie and Bob, could you determine what means this value? Would it make sense to update it with -12-31 and consider it as "will never expired"? On Wed, 14 Feb 2018 at 12:13 Tomas Cohen Arazi mailto:tomasco...@gmail.com>> wrote: In all my 65 instances, there's not '-00-00'. This is probably a data migration issue. El mié., 14 feb. 2018 a las 11:05, Sophie Meynieux (mailto:sophie.meyni...@biblibre.com>>) escribió: Hello, For all our customers that are hosted on our servers, only one has one patron with dateexpiry = "-00-00" Regards S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 14/02/2018 à 12:12, Katrin Fischer a écrit : I've also checked our oldest 5 - didn't find any patrons with dateexpiry -00-00. Gesendet: Mittwoch, 14. Februar 2018 um 08:18 Uhr Von: "Magnus Enger" <mailto:mag...@enger.priv.no> An: koha-devel@lists.koha-community.org<mailto:koha-devel@lists.koha-community.org> Betreff: Re: [Koha-devel] -00-00 is expired? Hiya! On 13 February 2018 at 20:06, Jonathan Druart <mailto:jonathan.dru...@bugs.koha-community.org> wrote: > It would be useful to know the return of > SELECT COUNT(*) FROM borrowers where dateexpiry="-00-00" > on old installations. I just checked my 5 oldest instances (upgraded regularly since 2009/2010) and none of them had any users meeting this criterium. Best regards, Magnus Libriotech ___________ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (https://theke.io<http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F _______ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plack only
Jonathan, It is certainly slower than I would like. The Plack support in Koha wasn’t great last time I tried it. I’m curious to try it again now, since people have worked on it more. I have used Plack for non-Koha apps and it’s worked great, so I’d like to move away from CGI. I’m planning to use Plack for dedicated servers, but for larger multitenant deployments, I’m wary of the resources that Starman would require when aggregated all together. While higher performance would be great, it certainly comes at the cost of resources. But… I haven’t tried that out recently, so I’m keen to see what the actual memory requirements will be. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org] Sent: Friday, 9 February 2018 12:31 AM To: David Cook Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only David, I cannot imagine Koha without Plack, it must be so slow... unless you run very old versions. The wiki page is there since years and the psgi in our codebase as well (the one outside the debian directory). Did you only try once to read the wiki page, modify the apache config and run starman or plackup with the psgi file? Before the debian package was ready for Plack, I was doing that (since at least 2014). You really should compare the performance with and without Plack... Jonathan On Wed, 7 Feb 2018 at 21:10 David Cook mailto:dc...@prosentient.com.au> > wrote: +1 Julian I've been avoiding Plack because we don't use Debian, but at some point I'll have to use it, and it would be great if it was community supported beyond just Debian. I'm happy to help test things, so long as I can have some guidance on what to do. (I'd love for the multi-tenant management tools to be de-debianized as well, but totally recognize that money/time is an obstacle. It's something I'd like to look at more in the future myself, but occupied with non-Koha projects at the moment...) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Julian Maurice Sent: Thursday, 8 February 2018 3:50 AM To: Tomas Cohen Arazi mailto:tomasco...@gmail.com> > Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Plack only Are they really in sync ? They look very different (I cannot use the rest api with misc/plack/koha.psgi for instance). IMO a good starting point would be to move debian/templates/plack.psgi outside of debian/ and make it the .psgi reference file for all types of install (and remove misc/plack in the process). Any thoughts ? Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : > Good point, Julian. You are right. > > Basically, we ship misc/plack/* which we keep in sync with > debian/templates/plack.psgi. > > I would love to spend some time de-debianizing hte multi-tenant > management tools, but its been hard to find sponsorship or time for it. > Most people are comfortable with Debian it seems. > > Regards > > El mié., 7 feb. 2018 a las 9:26, Julian Maurice > (mailto:julian.maur...@biblibre.com> > <mailto:julian.maur...@biblibre.com <mailto:julian.maur...@biblibre.com> >>) > escribió: > > What about people that do not use Debian ? It seems that there is no > "standard" way to use Plack outside of the Debian world, and it looks > like 90% of https://wiki.koha-community.org/wiki/Plack is outdated. > If we abandon CGI support, I think we should first provide a clear setup > documentation. I would happily rewrite the wiki page, but I'm not sure > of what to write (how to setup Plack on dev install for instance, or > 'standard' install without debian packages). > Or maybe I'm missing some important up-to-date documentation about > Plack ? > > (somewhat) related bug: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 > > Le 06/02/2018 à 19:50, Tomas Cohen Arazi a écrit : > > For running in Plack-mode, people needs to: > > > > sudo koha-plack --enable > > sudo koha-plack --start > > sudo systemctl restart apache2 > > > > after creating the . > > > > What I meant is that we should have people avoid the need for those > > commands. And people with
Re: [Koha-devel] Plack only
Hi Fridolin, I assume that's only 1 Plack instance on that 1 machine though, yes? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Fridolin SOMERS Sent: Saturday, 10 February 2018 2:40 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only Our tests when installing Plack shows a RAM use of around 200Mo, that's cool. We added a nightly reboot (made by logrotate) of starman for security. Page processing goes from 2 seconds without plack to 100-200ms with it, not the search pages of course because they depend on Zebra request time. We use 2 or 4 workers on a 4 CPU machine. We used 8 workers on a 4 CPU machine once for a library with a lot of accesses. Regards, Le 08/02/2018 à 23:41, David Cook a écrit : > Jonathan, > > > > It is certainly slower than I would like. > > > > The Plack support in Koha wasn’t great last time I tried it. I’m curious to > try it again now, since people have worked on it more. I have used Plack for > non-Koha apps and it’s worked great, so I’d like to move away from CGI. > > > > I’m planning to use Plack for dedicated servers, but for larger multitenant > deployments, I’m wary of the resources that Starman would require when > aggregated all together. While higher performance would be great, it > certainly comes at the cost of resources. But… I haven’t tried that out > recently, so I’m keen to see what the actual memory requirements will be. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org] > Sent: Friday, 9 February 2018 12:31 AM > To: David Cook > Cc: koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] Plack only > > > > David, > > I cannot imagine Koha without Plack, it must be so slow... unless you run > very old versions. > > The wiki page is there since years and the psgi in our codebase as well (the > one outside the debian directory). Did you only try once to read the wiki > page, modify the apache config and run starman or plackup with the psgi file? > > Before the debian package was ready for Plack, I was doing that (since at > least 2014). > > > > You really should compare the performance with and without Plack... > > Jonathan > > > > On Wed, 7 Feb 2018 at 21:10 David Cook <mailto:dc...@prosentient.com.au> > wrote: > > +1 Julian > > I've been avoiding Plack because we don't use Debian, but at some point I'll > have to use it, and it would be great if it was community supported beyond > just Debian. I'm happy to help test things, so long as I can have some > guidance on what to do. > > (I'd love for the multi-tenant management tools to be de-debianized as > well, but totally recognize that money/time is an obstacle. It's > something I'd like to look at more in the future myself, but occupied > with non-Koha projects at the moment...) > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > > -Original Message- > From: koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> > [mailto:koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of > Julian Maurice > Sent: Thursday, 8 February 2018 3:50 AM > To: Tomas Cohen Arazi <mailto:tomasco...@gmail.com> > > Cc: koha-devel@lists.koha-community.org > <mailto:koha-devel@lists.koha-community.org> > Subject: Re: [Koha-devel] Plack only > > Are they really in sync ? They look very different (I cannot use the rest api > with misc/plack/koha.psgi for instance). > > IMO a good starting point would be to move debian/templates/plack.psgi > outside of debian/ and make it the .psgi reference file for all types of > install (and remove misc/plack in the process). > Any thoughts ? > > Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : >> Good point, Julian. You are right. >> >> Basically, we ship misc/plack/* which we keep in sync with >> debian/templates/plack.psgi. >> >> I would love to spend some time de-debian
Re: [Koha-devel] Plack only
Our tests when installing Plack shows a RAM use of around 200Mo, that's cool. We added a nightly reboot (made by logrotate) of starman for security. Page processing goes from 2 seconds without plack to 100-200ms with it, not the search pages of course because they depend on Zebra request time. We use 2 or 4 workers on a 4 CPU machine. We used 8 workers on a 4 CPU machine once for a library with a lot of accesses. Regards, Le 08/02/2018 à 23:41, David Cook a écrit : Jonathan, It is certainly slower than I would like. The Plack support in Koha wasn’t great last time I tried it. I’m curious to try it again now, since people have worked on it more. I have used Plack for non-Koha apps and it’s worked great, so I’d like to move away from CGI. I’m planning to use Plack for dedicated servers, but for larger multitenant deployments, I’m wary of the resources that Starman would require when aggregated all together. While higher performance would be great, it certainly comes at the cost of resources. But… I haven’t tried that out recently, so I’m keen to see what the actual memory requirements will be. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org] Sent: Friday, 9 February 2018 12:31 AM To: David Cook Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only David, I cannot imagine Koha without Plack, it must be so slow... unless you run very old versions. The wiki page is there since years and the psgi in our codebase as well (the one outside the debian directory). Did you only try once to read the wiki page, modify the apache config and run starman or plackup with the psgi file? Before the debian package was ready for Plack, I was doing that (since at least 2014). You really should compare the performance with and without Plack... Jonathan On Wed, 7 Feb 2018 at 21:10 David Cook mailto:dc...@prosentient.com.au> > wrote: +1 Julian I've been avoiding Plack because we don't use Debian, but at some point I'll have to use it, and it would be great if it was community supported beyond just Debian. I'm happy to help test things, so long as I can have some guidance on what to do. (I'd love for the multi-tenant management tools to be de-debianized as well, but totally recognize that money/time is an obstacle. It's something I'd like to look at more in the future myself, but occupied with non-Koha projects at the moment...) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Julian Maurice Sent: Thursday, 8 February 2018 3:50 AM To: Tomas Cohen Arazi mailto:tomasco...@gmail.com> > Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Plack only Are they really in sync ? They look very different (I cannot use the rest api with misc/plack/koha.psgi for instance). IMO a good starting point would be to move debian/templates/plack.psgi outside of debian/ and make it the .psgi reference file for all types of install (and remove misc/plack in the process). Any thoughts ? Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : Good point, Julian. You are right. Basically, we ship misc/plack/* which we keep in sync with debian/templates/plack.psgi. I would love to spend some time de-debianizing hte multi-tenant management tools, but its been hard to find sponsorship or time for it. Most people are comfortable with Debian it seems. Regards El mié., 7 feb. 2018 a las 9:26, Julian Maurice (mailto:julian.maur...@biblibre.com> <mailto:julian.maur...@biblibre.com <mailto:julian.maur...@biblibre.com> >>) escribió: What about people that do not use Debian ? It seems that there is no "standard" way to use Plack outside of the Debian world, and it looks like 90% of https://wiki.koha-community.org/wiki/Plack is outdated. If we abandon CGI support, I think we should first provide a clear setup documentation. I would happily rewrite the wiki page, but I'm not sure of what to write (how to setup Plack on dev install for instance, or 'standard' install without debian packages). Or maybe I'm missing some important up-to-date documentation about Plack ? (somewhat) related bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 Le 06/02/2018 à 19:50, Tomas Cohen Arazi a écrit : > For ru
Re: [Koha-devel] Plack only
Hi indeed, 1 Plack instance Le 12/02/2018 à 03:48, David Cook a écrit : Hi Fridolin, I assume that's only 1 Plack instance on that 1 machine though, yes? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Fridolin SOMERS Sent: Saturday, 10 February 2018 2:40 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only Our tests when installing Plack shows a RAM use of around 200Mo, that's cool. We added a nightly reboot (made by logrotate) of starman for security. Page processing goes from 2 seconds without plack to 100-200ms with it, not the search pages of course because they depend on Zebra request time. We use 2 or 4 workers on a 4 CPU machine. We used 8 workers on a 4 CPU machine once for a library with a lot of accesses. Regards, Le 08/02/2018 à 23:41, David Cook a écrit : Jonathan, It is certainly slower than I would like. The Plack support in Koha wasn’t great last time I tried it. I’m curious to try it again now, since people have worked on it more. I have used Plack for non-Koha apps and it’s worked great, so I’d like to move away from CGI. I’m planning to use Plack for dedicated servers, but for larger multitenant deployments, I’m wary of the resources that Starman would require when aggregated all together. While higher performance would be great, it certainly comes at the cost of resources. But… I haven’t tried that out recently, so I’m keen to see what the actual memory requirements will be. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org] Sent: Friday, 9 February 2018 12:31 AM To: David Cook Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only David, I cannot imagine Koha without Plack, it must be so slow... unless you run very old versions. The wiki page is there since years and the psgi in our codebase as well (the one outside the debian directory). Did you only try once to read the wiki page, modify the apache config and run starman or plackup with the psgi file? Before the debian package was ready for Plack, I was doing that (since at least 2014). You really should compare the performance with and without Plack... Jonathan On Wed, 7 Feb 2018 at 21:10 David Cook mailto:dc...@prosentient.com.au> > wrote: +1 Julian I've been avoiding Plack because we don't use Debian, but at some point I'll have to use it, and it would be great if it was community supported beyond just Debian. I'm happy to help test things, so long as I can have some guidance on what to do. (I'd love for the multi-tenant management tools to be de-debianized as well, but totally recognize that money/time is an obstacle. It's something I'd like to look at more in the future myself, but occupied with non-Koha projects at the moment...) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Julian Maurice Sent: Thursday, 8 February 2018 3:50 AM To: Tomas Cohen Arazi mailto:tomasco...@gmail.com> > Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Plack only Are they really in sync ? They look very different (I cannot use the rest api with misc/plack/koha.psgi for instance). IMO a good starting point would be to move debian/templates/plack.psgi outside of debian/ and make it the .psgi reference file for all types of install (and remove misc/plack in the process). Any thoughts ? Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : Good point, Julian. You are right. Basically, we ship misc/plack/* which we keep in sync with debian/templates/plack.psgi. I would love to spend some time de-debianizing hte multi-tenant management tools, but its been hard to find sponsorship or time for it. Most people are comfortable with Debian it seems. Regards El mié., 7 feb. 2018 a las 9:26, Julian Maurice (mailto:julian.maur...@biblibre.com> <mailto:julian.maur...@biblibre.com <mailto:julian.maur...@biblibre.com> >>) escribió: What about people that do not use Debian ? It seems that there is no "standard" way to use Plack outside of the Debian world, and it looks like 90% of https://wiki.koha-community.org
Re: [Koha-devel] Koha-devel Digest, Vol 206, Issue 43
Tun off slew of nessages Sent from the all new AOL app for Android On Sun, Jan 15, 2023 at 3:03 PM, koha-devel-requ...@lists.koha-community.org wrote: Send Koha-devel mailing list submissions to koha-devel@lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-requ...@lists.koha-community.org You can reach the person managing the list at koha-devel-ow...@lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. New request created with ID: ##7240## from koha-devel-requ...@lists.koha-community.org (Trident Support Team) 2. New request created with ID: ##7253## from koha-devel-requ...@lists.koha-community.org (Trident Support Team) 3. New request created with ID: ##7315## from koha-devel-requ...@lists.koha-community.org (Trident Support Team) -- Message: 1 Date: Sun, 15 Jan 2023 14:01:32 -0800 From: Trident Support Team To: Subject: [Koha-devel] New request created with ID: ##7240## from koha-devel-requ...@lists.koha-community.org Message-ID: <185b773ba46.4565c88e1722838.3526526786131021...@tridentcf.com> Content-Type: text/plain; charset="utf-8" An HTML attachment was scrubbed... URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230115/354ec3fe/attachment-0001.htm> -- Message: 2 Date: Sun, 15 Jan 2023 14:02:02 -0800 From: Trident Support Team To: Subject: [Koha-devel] New request created with ID: ##7253## from koha-devel-requ...@lists.koha-community.org Message-ID: <185b7742e9f.829361b91674553.5393276475597974...@tridentcf.com> Content-Type: text/plain; charset="utf-8" An HTML attachment was scrubbed... URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230115/3b3d6f12/attachment-0001.htm> -- Message: 3 Date: Sun, 15 Jan 2023 14:03:33 -0800 From: Trident Support Team To: Subject: [Koha-devel] New request created with ID: ##7315## from koha-devel-requ...@lists.koha-community.org Message-ID: <185b7758f32.5a142b1b1674609.6088691356341981...@tridentcf.com> Content-Type: text/plain; charset="utf-8" An HTML attachment was scrubbed... URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230115/5c612f12/attachment.htm> -- Subject: Digest Footer ___________ Koha-devel mailing list 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/ -- End of Koha-devel Digest, Vol 206, Issue 43 *** ___________ Koha-devel mailing list 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/
Re: [Koha-devel] To React or not to React
Also, how would this React POC go in terms of translations? React is just Javascript, and is translated the same way translate all our other js files. We don't translate js files at the moment - which may be debatable. One benefit at the moment of keeping the strings only in the templates is that we don't copy the js files as we do with the template files. I think this should be solvable, but it's something to keep in mind. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -Original Message- > From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel- <mailto:koha-devel-> > boun...@lists.koha-community.org <mailto:boun...@lists.koha-community.org>] On Behalf Of Owen Leonard > Sent: Monday, 19 September 2016 11:33 PM > To: Koha Devel mailto:koha-devel@lists.koha-community.org>> > Subject: Re: [Koha-devel] To React or not to React > > > Another thing is that you need nodejs to compile it so is another > > thing to throw on the stack. > > Isn't this the kind of dependency requirement that killed my request to > introduce a front-end build tool like Grunt or Gulp? > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > _______ > Koha-devel mailing list > Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ <http://community.org/> bugs : http://bugs.koha-community.org/ <http://bugs.koha-community.org/> ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Carrousel display issue on sandbox
Hi Shi Yao, did you see Jonathan's reply? https://lists.koha-community.org/pipermail/koha-devel/2023-September/048336.html Katrin On 22.09.23 14:42, Shi Yao Wang wrote: Hi Katrin, thank you for confirming the issue. Can anyone else help? Shi Yao On 2023-09-14 13:24, Katrin Fischer wrote: Hi Shi Yao, I have tested the plugin locally and I can confirm that the .js files are not loaded. But, I don't know what's needed to make it work. Maybe one of the other plugin developers could help? Katrin On 12.09.23 08:44, Fridolin SOMERS wrote: Oooo I did not knew the repos of InLibro have moved. Great :) I suggest you add topic koha-plugin on those repos : https://github.com/topics/koha-plugin Best regards, Le 11/09/2023 à 09:32, Shi Yao Wang a écrit : Hello, here it is: https://github.com/inLibro/koha-plugin-carrousel Shi Yao On 2023-09-11 15:26, Katrin Fischer wrote: Hi, sorry, I should have been more clear: Can you post the link to the repository? Katrin On 11.09.23 21:22, Shi Yao Wang wrote: version 4.1.4 On 2023-09-11 15:13, Katrin Fischer wrote: Hi Shi Yao, as there are multiple versions of the carousel plugin around, which one did you use/install? Hope this helps, Katrin On 11.09.23 21:10, Shi Yao Wang wrote: Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/
Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue?
Yeah, I keep thinking that people won’t do something more secure if it’s less convenient for them. I suppose that’s their choice in the end though… and we can provide better options for those that do care more. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Tomas Cohen Arazi Sent: Wednesday, 20 June 2018 11:02 AM To: koha-devel Subject: Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue? The way we do this is having a syspref to choose between both ways, and a big sign ok to of the release notes asking users to switch. El mar., 19 de jun. de 2018 9:25 p. m., Liz Rea mailto:l...@catalyst.net.nz> > escribió: The easy answer is : leave it alone for existing installs, default it on for new ones. On 20/06/18 12:19, David Cook wrote: > > I think that’s not a bad way of looking at it. If people do complain, > we can say that the change away was because of a commitment to patron > security and privacy. I would hope that people would find that > difficult to argue against. > > If I recall correctly, I think DSpace does it this way. When you > create a new user, I think it sends an email containing a URL with a > token to the user, and then they set their own password from there. It > works pretty well. Surely we could say “everybody else is doing it” as > well. > > But I know that there are a lot of libraries using this feature, and > it would be disruptive to their existing workflows for it to go away. > But… that’s also progress for you. So long as people have notice that > it’s going away before the upgrade, they’d have time to change their > workflows and adapt to a safer way of doing things? > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > *From:*Chris Cormack [mailto:chr...@catalyst.net.nz > <mailto:chr...@catalyst.net.nz> ] > *Sent:* Wednesday, 20 June 2018 10:12 AM > *To:* koha-devel@lists.koha-community.org > <mailto:koha-devel@lists.koha-community.org> ; David Cook > mailto:dc...@prosentient.com.au> >; 'Liz Rea' > mailto:l...@catalyst.net.nz> > > *Subject:* Re: [Koha-devel] Why we do not push the ACCTDETAILS email > via message queue? > > We could make a list of them. It could be the "libraries who don't > care about their users privacy" list. > > I'm only mostly joking > > Chris > > On June 20, 2018 12:06:52 PM GMT+12:00, David Cook > mailto:dc...@prosentient.com.au> > <mailto:dc...@prosentient.com.au <mailto:dc...@prosentient.com.au> >> wrote: > > I think that would probably be the best way of going about it, but > I’m sure there are a lot of libraries that wouldn’t be happy about > it. > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > *From:*koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> > <mailto:koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> > > [mailto:koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> ] *On Behalf Of > *Liz Rea > *Sent:* Tuesday, 19 June 2018 12:26 PM > *To:* koha-devel@lists.koha-community.org > <mailto:koha-devel@lists.koha-community.org> > <mailto:koha-devel@lists.koha-community.org > <mailto:koha-devel@lists.koha-community.org> > > *Subject:* Re: [Koha-devel] Why we do not push the ACCTDETAILS > email via message queue? > > I feel like instead of sending people a password, we should send > them to the "forgot password reset page" with a couple of slight > changes for new account holders, so they can set their own passwords. > > Seems better than sending the password in the clear in an email. > > Cheers, > Liz > > On 19/06/18 12:21, David Cook wrote: > > Cheers, Jonathan. I had totally forgotten about that. Yikes. > > > > Good call, Chris. While I think many mail servers these days use TLS > to secure the email between the mail servers, an unscrupulous administrator > could still certainly take advantage of peopl
Re: [Koha-devel] 0000-00-00 is expired?
It should be null. El mié., 14 feb. 2018 a las 12:58, Jonathan Druart (< jonathan.dru...@bugs.koha-community.org>) escribió: > yes could be NULL instead. > (date calculation perf issue is fixed) > > On Wed, 14 Feb 2018 at 12:50 Marcel de Rooy > wrote: > >> Sounds to me like NULL was meant ? >> >> Using -12-31 resulted in expensive date calculations previously. >> >> >> >> -- >> *Van:* koha-devel-boun...@lists.koha-community.org < >> koha-devel-boun...@lists.koha-community.org> namens Jonathan Druart < >> jonathan.dru...@bugs.koha-community.org> >> *Verzonden:* woensdag 14 februari 2018 16:41 >> *Aan:* koha-devel@lists.koha-community.org >> *Onderwerp:* Re: [Koha-devel] -00-00 is expired? >> >> Great news then :) >> >> Sophie and Bob, could you determine what means this value? Would it make >> sense to update it with -12-31 and consider it as "will never expired"? >> >> On Wed, 14 Feb 2018 at 12:13 Tomas Cohen Arazi >> wrote: >> >> In all my 65 instances, there's not '-00-00'. This is probably a data >> migration issue. >> >> El mié., 14 feb. 2018 a las 11:05, Sophie Meynieux (< >> sophie.meyni...@biblibre.com>) escribió: >> >> Hello, >> >> For all our customers that are hosted on our servers, only one has one >> patron with dateexpiry = "-00-00" >> >> Regards >> >> S. Meynieux >> >> -- >> Responsable support >> BibLibre+ 33 (0)4 91 81 35 08 >> <+33%204%2091%2081%2035%2008>http://www.biblibre.com >> >> Le 14/02/2018 à 12:12, Katrin Fischer a écrit : >> >> I've also checked our oldest 5 - didn't find any patrons with dateexpiry >> -00-00. >> >> *Gesendet:* Mittwoch, 14. Februar 2018 um 08:18 Uhr >> *Von:* "Magnus Enger" >> *An:* koha-devel@lists.koha-community.org >> *Betreff:* Re: [Koha-devel] -00-00 is expired? >> Hiya! >> >> On 13 February 2018 at 20:06, Jonathan Druart >> >> wrote: >> > It would be useful to know the return of >> > SELECT COUNT(*) FROM borrowers where dateexpiry="-00-00" >> > on old installations. >> >> I just checked my 5 oldest instances (upgraded regularly since >> 2009/2010) and none of them had any users meeting this criterium. >> >> Best regards, >> Magnus >> Libriotech >> _______ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> ___ >> Koha-devel mailing >> listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> -- >> Tomás Cohen Arazi >> Theke Solutions (https://theke.io <http://theke.io/>) >> ✆ +54 9351 3513384 <+54%209%20351%20351-3384> >> GPG: B2F3C15F >> ___________ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] How to see security fixes
Uh..., probably it is not so good to publish security issues on a public list. The official way is https://koha-community.org/security/ <https://koha-community.org/security/> if I'm not wrong. sb > On 15 Mar 2017, at 16:57, Devinim Koha Development Team > wrote: > > Hi, > > In that case we can reach the user detailed information without giving a > password by curl. > > If you want we can share the code how to get this information without > authentication, from this list. > > On 15-03-2017 18:50, Jonathan Druart wrote: >> Hi, >> >> authnotrequired is set to 1 because opac-memberentry.pl >> <http://opac-memberentry.pl/> is also used by the self registration feature. >> The patron information displayed is based on the logged in user, not a >> parameter passed to the script. >> >> Everything looks ok to me. >> >> Regards, >> Jonathan >> >> On Wed, 15 Mar 2017 at 12:18 Devinim Koha Development Team >> mailto:kohadevi...@devinim.com.tr>> wrote: >> Hi all, >> >> In the opac-memberentry.pl <http://opac-memberentry.pl/> authnotrequired >> area is 1 by default, in that case, user information can be reached without >> given a user authentication >> and this can lead some vulnerabilites, do we miss something? We were not >> able to understand why it is 1 by default? >> >> Thanks. >> On 14-03-2017 11:33, Chris Cormack wrote: >>> Hi, >>> >>> Normally once they are released the release maintainer shifts them out of >>> security. That one got missed, shifted now >>> >>> Chris >>> >>> On 14 March 2017 9:13:51 PM NZDT, Devinim Koha Development Team >>> <mailto:kohadevi...@devinim.com.tr> wrote: >>> Hi all, >>> >>> How can we see the fixes of security bugs? >>> >>> We've faced with a vulnerability with Bug# 16969 in a new version, but >>> it's said that it was fixed in 3.22.10. >>> >>> >>> Thanks. >>> >>> Devinim Koha Dev. Team >>> >>> >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> <mailto:Koha-devel@lists.koha-community.org> >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> <http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> >>> website : http://www.koha-community.org <http://www.koha-community.org/>/ >>> git : http://git.koha-community.org <http://git.koha-community.org/>/ >>> bugs : http://bugs.koha-community.org <http://bugs.koha-community.org/>/ >>> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. >> ___ Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> <mailto:Koha-devel@lists.koha-community.org> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> <http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> >> website : http://www.koha-community.org/ <http://www.koha-community.org/> >> git : http://git.koha-community.org/ <http://git.koha-community.org/>bugs : >> http://bugs.koha-community.org/ <http://bugs.koha-community.org/> >> ___________ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> <mailto:Koha-devel@lists.koha-community.org> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> <http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> >> website : http://www.koha-community.org/ <http://www.koha-community.org/> >> git : http://git.koha-community.org/ <http://git.koha-community.org/> >> bugs : http://bugs.koha-community.org/ >> <http://bugs.koha-community.org/>___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-bugs] [Bug 5166] Refactor rebuild_zebra.pl into a library
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5166 --- Comment #19 from MJ Ray (software.coop) 2011-04-10 11:25:16 UTC --- This bug is mentioned in: [Bug 5166] Refactor rebuild_zebra.pl into alibrary http://lists.koha-community.org/pipermail/koha-patches/2011-March/013969.html [Bug 5166] Libraries and zebraqueuedaemon scripts http://lists.koha-community.org/pipermail/koha-patches/2011-March/014163.html [Bug 5166] Sysprefs http://lists.koha-community.org/pipermail/koha-patches/2011-March/014164.html [Bug 5166] zebraqueue daemon scripts http://lists.koha-community.org/pipermail/koha-patches/2011-March/014165.html [Bug 5166] updatedatabase.pl fix http://lists.koha-community.org/pipermail/koha-patches/2011-March/014166.html Bug 5166: Libraries andzebraqueue daemon scripts http://lists.koha-community.org/pipermail/koha-patches/2011-March/014175.html Bug 5166: Sysprefs http://lists.koha-community.org/pipermail/koha-patches/2011-March/014176.html Bug 5166: zebraqueue daemonscripts http://lists.koha-community.org/pipermail/koha-patches/2011-March/014177.html Bug 5166: updatedatabase.plfix http://lists.koha-community.org/pipermail/koha-patches/2011-March/014178.html -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA Contact for the bug. ___ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-bugs] [Bug 17015] New Koha Calendar
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17015 --- Comment #313 from Victor Grousset/tuxayo --- (In reply to Blou from comment #312) > You can see comment 12 from Mehdi, for some summary. Thanks, that's great. > There was also emails > sent to the lists at the time, describing the plan. And replies that > basically shut it down. I dug in koha-devel and found the early proposal and later the "emails sent to the lists at the time" but did find the replies that basically shut it down. Or was that at the moment of the early proposal? See 2016-August emails bellow. https://lists.koha-community.org/pipermail/koha-devel/2016-July/042854.html https://lists.koha-community.org/pipermail/koha-devel/2016-July/042856.html https://lists.koha-community.org/pipermail/koha-devel/2016-July/042858.html https://lists.koha-community.org/pipermail/koha-devel/2016-July/042859.html https://lists.koha-community.org/pipermail/koha-devel/2016-July/042865.html https://lists.koha-community.org/pipermail/koha-devel/2016-July/042867.html https://lists.koha-community.org/pipermail/koha-devel/2016-July/042871.html https://lists.koha-community.org/pipermail/koha-devel/2016-August/042881.html https://lists.koha-community.org/pipermail/koha-devel/2016-August/042890.html https://lists.koha-community.org/pipermail/koha-devel/2017-January/043420.html https://lists.koha-community.org/pipermail/koha-devel/2017-February/043454.html Is the new calendar at feature parity with the current one? Or are there features that you didn't need and didn't reimplemented in the new backend or new UI? -- You are receiving this mail because: You are watching all bug changes. ___ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Errors generating fr-FR templates in 3.18.5
Thanks Bernardo and Marc (and Katrin) for the explanations and help! So what should I do in future when I encounter problems like this? Just email koha-translate? Or try to resolve them myself on Pootle? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Bernardo Gonzalez Kriegel [mailto:bgkrie...@gmail.com] Sent: Friday, 27 March 2015 10:23 AM To: David Cook Cc: Marc Véron; Koha-org - Translate list; koha-devel Subject: Re: [Koha-devel] Errors generating fr-FR templates in 3.18.5 Normally, those errors are detected and set as fuzzy on updating from english templates. When updated po files are loaded on translation server, that strings are shown as fuzzy to translators. But some strings have been incorrectly set as translated and now are on master and 3.18.x :) I will fix them on next stable release, and give RM a patch to fix them on master. Bernardo -- Bernardo Gonzalez Kriegel bgkrie...@gmail.com <mailto:bgkrie...@gmail.com> On Thu, Mar 26, 2015 at 7:41 PM, David Cook mailto:dc...@prosentient.com.au> > wrote: Hi Marc: I'm sorry but I don't understand. There were two %s missing in fr-FR-i-staff-t-prog-v-3006000.po... I don't think they were superfluous? I still don't understand where the .po files come from. Does someone generate them from the English templates? When? How does one submit fixes? Through Pootle? Through Git? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -Original Message- > From: koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel- > <mailto:koha-devel-> > boun...@lists.koha-community.org <mailto:boun...@lists.koha-community.org> ] > On Behalf Of Marc Véron > Sent: Thursday, 26 March 2015 6:14 PM > To: koha-transl...@lists.koha-community.org > <mailto:koha-transl...@lists.koha-community.org> > Cc: Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > Subject: Re: [Koha-devel] Errors generating fr-FR templates in 3.18.5 > > Hi David, > > There were printf() errors on Pootle for French 3.18: : > > http://translate.koha-community.org/fr/318/ > Click "Expand details" > Printf() 3 Errors > > I fixed them on Pootle (2 %s were superfluous, 1 had a wrong capitalization) > > Marc > _______ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ <http://community.org/> bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] koha for e-resource management
Hi there! Very Effectiveness! It is very straightforward to set up. Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux! On 08.09.2015 04:06, long_sam.tw wrote: Hi kivilahti good idea, So how Effectiveness ? BR, longsam Kivilahti Olli-Antti <mailto:olli-antti.kivila...@jns.fi> 於 2015/9/7 (週一) 10:12 PM 寫道﹕ Hi! We just started to use eResources in Koha. We link from the Bibliographic detail-view to the eResource vendors web-site. And authenticate from there using SIP2, protected with an IP-limit enforced in a firewall rule. Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux! On 04.09.2015 15:49, long_sam.tw wrote: Hi, François A-Z https://www.ebscohost.com/discovery/technology/a-to-z Advanced ERM products Discovery Service Serials Solutions Summon Ex Libris Primo Central OCLC WorldCat Local EBSCO Discovery Service Innovative Interface You can refer http://americanlibrariesmagazine.org/2015/05/01/library-systems-report/ Marshall Breeding's wrote a very detailed. BR, longsam Francois Charbonnier <mailto:francois.charbonn...@inlibro.com> 於 2015/9/4 (週五) 8:24 PM 寫道﹕ Hello Longsam, Do you have examples of those ILS? I'm curious about what they call ERM in their systems. Thanks. François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonn...@inlibro.com<mailto:francois.charbonn...@inlibro.com> inLibro | pour esprit libre | www.inLibro.com<http://www.inlibro.com/> Le 2015-09-04 04:16, long_sam.tw a écrit : Dear koha folks. Recently , many ILS provide e-resource management for library. In koha, Are there some plan about e-resource management in the future? BR, longsam ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] items.itype FK constraint?
If we set items.itype to NULL, aren’t we potentially causing problems for people who want to JOIN “statistics” and “items” tables? Do we already have software logic to prevent Item Types from being deleted if they’re used in items or biblioitems? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org On Behalf Of Tomas Cohen Arazi Sent: Wednesday, 31 July 2019 5:08 AM To: Katrin Fischer Cc: koha-devel Subject: Re: [Koha-devel] items.itype FK constraint? We can set a FK constraint while allowing NULL too. The reason for me to post this on the list is to hear (probably) historical reasons for this constraint not to be set already at DB level. Thanks for your replies! El mar., 30 jul. 2019 a las 16:05, Katrin Fischer (mailto:katrin.fischer...@web.de> >) escribió: Hi Sophie, I think on database level we need to allow NULL, because of the item-level_itype 'record level' setting. I understand that itemtypes are not set on item level at all in that case? Katrin On 30.07.19 16:32, Sophie Meynieux wrote: Hello, But itype must not be null if syspref item-level_itype is on, isn't it ? S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 29/07/2019 à 20:17, Katrin Fischer a écrit : +1 With a on delete set null? On 29.07.19 19:39, Tomas Cohen Arazi wrote: Why shouldn't we add it :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F signature.asc Description: PGP signature _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] mariadb versions and koha
the update has many advantages and new features. There is a new feature with 10.4 that limits the size of temporary tables. This is useful when running poorly constructed reports (Cartesian products) that can generate gigabytes of temporary tables. For exemple: [mysqld] innodb_temp_data_file_path = ibtmp1:12M:autoextend:max:1G did anyone ever test this feature? Laurent Ducos Administrateur système et réseaux chez BibLibre 23 août 2019 04:24 "Tomas Cohen Arazi" mailto:tomasco...@gmail.com?to=%22Tomas%20Cohen%20Arazi%22%20)> a écrit: We've been testing MySQL 8 as well, without major issues, besides the need to solve the authentication issue (i.e. making mysql-client v5.x work). Regards El jue., 22 ago. 2019 a las 22:53, Mark Tompsett (mailto:mtomp...@hotmail.com)>) escribió: Greetings, In order to avoid the auto-increment bug, you really want 10.3 or higher. :) GPML, Mark Tompsett -Original Message- From: Laurent Ducos Sent: Thursday, August 22, 2019 4:50 AM To: koha-devel@lists.koha-community.org (mailto:koha-devel@lists.koha-community.org) Subject: [Koha-devel] mariadb versions and koha Hello We are currently using version 10.0 of mariadb with koha. We are planning a upgrade. Have you noticed problems with versions 10.1 10.2, 10.3 or 10.4? -- Laurent Ducos Administrateur système et réseaux chez BibLibre IT system and network administrator at BibLibre ___ Koha-devel mailing list Koha-devel@lists.koha-community.org (mailto:Koha-devel@lists.koha-community.org) https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel (https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel) website : http://www.koha-community.org/ (http://www.koha-community.org/) git : http://git.koha-community.org/ (http://git.koha-community.org/) bugs : http://bugs.koha-community.org/ (http://bugs.koha-community.org/) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org (mailto:Koha-devel@lists.koha-community.org) https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel (https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel) website : http://www.koha-community.org/ (http://www.koha-community.org/) git : http://git.koha-community.org/ (http://git.koha-community.org/) bugs : http://bugs.koha-community.org/ (http://bugs.koha-community.org/) -- Tomás Cohen Arazi Theke Solutions (http://theke.io (http://theke.io/)) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Indexes of Physical presentation
Thanks Bernardo ;)
Le 18/11/2015 21:02, Katrin Fischer a écrit :
Ah, that explains, thx Bernardo! :)
Am 18.11.2015 um 17:49 schrieb Bernardo Gonzalez Kriegel:
It's UNIMARC specific :)
--
Bernardo Gonzalez Kriegel
bgkrie...@gmail.com <mailto:bgkrie...@gmail.com>
On Wed, Nov 18, 2015 at 1:15 PM, Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>> wrote:
Hie Katrin,
'physical presentation' is just the name of one of the search fields
in advanced search.
In intranet you must click on 'Coded information filters' to see it.
I don't know if it is UNIMARC-only, can you check with the demo
websites ?
Best regards.
Le 10/11/2015 23:14, Katrin Fischer a écrit :
Hi Fridolin,
I have tried to look into this, but I am not sure what you mean with
'physical presentation'. Can you explain a bit more? Is this UNIMARC
specific?
Katrin
Am 05.11.2015 um 09:33 schrieb Fridolin SOMERS:
Hie,
In intranet search, physical presentation uses index ff8-23.
In opac search, physical presentation uses index Material-type.
This is strange because the search always use the coded
values, meaning
it is ff8-23 the correct index.
Do you agree ?
Regards,
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--
Fridolin SOMERS
Biblibre - Pôles support et système
fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com>
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--
Fridolin SOMERS
Biblibre - Pôles support et système
fridolin.som...@biblibre.com
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Request for feedback: Bug 20779 - Style refresh for patron detail page
+1 El lun., 4 de jun. de 2018 3:23 p. m., Barton Chittenden < bar...@bywatersolutions.com> escribió: > +1 > > > On Mon, Jun 4, 2018 at 2:20 PM, Katrin Fischer > wrote: > >> +1 ! >> >> :) >> >> >> On 04.06.2018 18:27, Séverine Queune wrote: >> >> I like that one ! >> >> 2018-06-04 18:10 GMT+02:00 Owen Leonard : >> >>> If there is consensus that the add/edit buttons should be in line with >>> the section headings: >>> >>> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75780 >>> >>> -- Owen >>> ___ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >> >> >> >> -- >> >> *Séverine QUEUNE* >> Administrateur fonctionnel du SIGB >> Équipe signalement et exposition des données >> Pôle Flux et données >> >> >> <https://www.youtube-nocookie.com/embed/myZ2K_alngw> >> [image: Logo BULAC] >> >> Bibliothèque universitaire >> des langues et civilisations >> >> >> 65 rue des Grands Moulins >> F-75013 PARIS >> T +33 1 81 69 *18 55* >> www.bulac.fr >> >> >> ___ >> Koha-devel mailing >> listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> >> ___________ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Carrousel display issue on sandbox
Hello, here it is: https://github.com/inLibro/koha-plugin-carrousel Shi Yao On 2023-09-11 15:26, Katrin Fischer wrote: Hi, sorry, I should have been more clear: Can you post the link to the repository? Katrin On 11.09.23 21:22, Shi Yao Wang wrote: version 4.1.4 On 2023-09-11 15:13, Katrin Fischer wrote: Hi Shi Yao, as there are multiple versions of the carousel plugin around, which one did you use/install? Hope this helps, Katrin On 11.09.23 21:10, Shi Yao Wang wrote: Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/
Re: [Koha-devel] [Koha] Koha packages are available 🎁
I'm looking at archives :
https://lists.koha-community.org/pipermail/koha-devel/2021-December/date.html
I dont see it.
Can anyone confirm ?
Le 29/12/2021 à 05:07, Kyle Hall a écrit :
I sent out an email for 21.11, did it get blocked?
Kyle
---
http://www.kylehall.info <http://www.kylehall.info>
ByWater Solutions ( http://bywatersolutions.com
<http://bywatersolutions.com> )
Meadville Public Library ( http://www.meadvillelibrary.org
<http://www.meadvillelibrary.org> )
Crawford County Federated Library System ( http://www.ccfls.org
<http://www.ccfls.org> )
On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>> wrote:
Hi,
There has been a mail for 20.11.13 release :
https://koha-community.org/koha-20-11-13-released/
<https://koha-community.org/koha-20-11-13-released/>
For other versions I don't see emails.
Here are the details :
20.11.01 release :
https://koha-community.org/koha-21-11-01-released/
<https://koha-community.org/koha-21-11-01-released/>
21.05.08 release :
https://koha-community.org/koha-21-05-08-released/
<https://koha-community.org/koha-21-05-08-released/>
Best regards,
Le 25/12/2021 à 16:02, Mason James a écrit :
> kia ora community,
> the latest Koha packages are available
>
> cheers, Mason
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
> website : https://www.koha-community.org/
<https://www.koha-community.org/>
> git : https://git.koha-community.org/
<https://git.koha-community.org/>
> bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Fridolin SOMERS
<mailto:fridolin.som...@biblibre.com>>
Software and system maintainer 🦄
BibLibre, France
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : https://www.koha-community.org/
<https://www.koha-community.org/>
git : https://git.koha-community.org/ <https://git.koha-community.org/>
bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Fridolin SOMERS
Software and system maintainer 🦄
BibLibre, France
___
Koha-devel mailing list
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/
Re: [Koha-devel] 0000-00-00 is expired?
yes could be NULL instead. (date calculation perf issue is fixed) On Wed, 14 Feb 2018 at 12:50 Marcel de Rooy wrote: > Sounds to me like NULL was meant ? > > Using -12-31 resulted in expensive date calculations previously. > > > > -- > *Van:* koha-devel-boun...@lists.koha-community.org < > koha-devel-boun...@lists.koha-community.org> namens Jonathan Druart < > jonathan.dru...@bugs.koha-community.org> > *Verzonden:* woensdag 14 februari 2018 16:41 > *Aan:* koha-devel@lists.koha-community.org > *Onderwerp:* Re: [Koha-devel] -00-00 is expired? > > Great news then :) > > Sophie and Bob, could you determine what means this value? Would it make > sense to update it with -12-31 and consider it as "will never expired"? > > On Wed, 14 Feb 2018 at 12:13 Tomas Cohen Arazi > wrote: > > In all my 65 instances, there's not '-00-00'. This is probably a data > migration issue. > > El mié., 14 feb. 2018 a las 11:05, Sophie Meynieux (< > sophie.meyni...@biblibre.com>) escribió: > > Hello, > > For all our customers that are hosted on our servers, only one has one > patron with dateexpiry = "-00-00" > > Regards > > S. Meynieux > > -- > Responsable support > BibLibre+ 33 (0)4 91 81 35 08 > <+33%204%2091%2081%2035%2008>http://www.biblibre.com > > Le 14/02/2018 à 12:12, Katrin Fischer a écrit : > > I've also checked our oldest 5 - didn't find any patrons with dateexpiry > -00-00. > > *Gesendet:* Mittwoch, 14. Februar 2018 um 08:18 Uhr > *Von:* "Magnus Enger" > *An:* koha-devel@lists.koha-community.org > *Betreff:* Re: [Koha-devel] -00-00 is expired? > Hiya! > > On 13 February 2018 at 20:06, Jonathan Druart > > wrote: > > It would be useful to know the return of > > SELECT COUNT(*) FROM borrowers where dateexpiry="-00-00" > > on old installations. > > I just checked my 5 oldest instances (upgraded regularly since > 2009/2010) and none of them had any users meeting this criterium. > > Best regards, > Magnus > Libriotech > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > ___ > Koha-devel mailing > listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > ___________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] 0000-00-00 is expired?
Actually we already have Bug 14717: Prevent -00-00 dates in patron data) on 3.21.00.023 which does that! On Wed, 14 Feb 2018 at 13:03 Tomas Cohen Arazi wrote: > It should be null. > > El mié., 14 feb. 2018 a las 12:58, Jonathan Druart (< > jonathan.dru...@bugs.koha-community.org>) escribió: > >> yes could be NULL instead. >> (date calculation perf issue is fixed) >> >> On Wed, 14 Feb 2018 at 12:50 Marcel de Rooy >> wrote: >> >>> Sounds to me like NULL was meant ? >>> >>> Using -12-31 resulted in expensive date calculations previously. >>> >>> >>> >>> ------ >>> *Van:* koha-devel-boun...@lists.koha-community.org < >>> koha-devel-boun...@lists.koha-community.org> namens Jonathan Druart < >>> jonathan.dru...@bugs.koha-community.org> >>> *Verzonden:* woensdag 14 februari 2018 16:41 >>> *Aan:* koha-devel@lists.koha-community.org >>> *Onderwerp:* Re: [Koha-devel] -00-00 is expired? >>> >>> Great news then :) >>> >>> Sophie and Bob, could you determine what means this value? Would it make >>> sense to update it with -12-31 and consider it as "will never expired"? >>> >>> On Wed, 14 Feb 2018 at 12:13 Tomas Cohen Arazi >>> wrote: >>> >>> In all my 65 instances, there's not '-00-00'. This is probably a >>> data migration issue. >>> >>> El mié., 14 feb. 2018 a las 11:05, Sophie Meynieux (< >>> sophie.meyni...@biblibre.com>) escribió: >>> >>> Hello, >>> >>> For all our customers that are hosted on our servers, only one has one >>> patron with dateexpiry = "-00-00" >>> >>> Regards >>> >>> S. Meynieux >>> >>> -- >>> Responsable support >>> BibLibre+ 33 (0)4 91 81 35 08 >>> <+33%204%2091%2081%2035%2008>http://www.biblibre.com >>> >>> Le 14/02/2018 à 12:12, Katrin Fischer a écrit : >>> >>> I've also checked our oldest 5 - didn't find any patrons with dateexpiry >>> -00-00. >>> >>> *Gesendet:* Mittwoch, 14. Februar 2018 um 08:18 Uhr >>> *Von:* "Magnus Enger" >>> *An:* koha-devel@lists.koha-community.org >>> *Betreff:* Re: [Koha-devel] -00-00 is expired? >>> Hiya! >>> >>> On 13 February 2018 at 20:06, Jonathan Druart >>> >>> wrote: >>> > It would be useful to know the return of >>> > SELECT COUNT(*) FROM borrowers where dateexpiry="-00-00" >>> > on old installations. >>> >>> I just checked my 5 oldest instances (upgraded regularly since >>> 2009/2010) and none of them had any users meeting this criterium. >>> >>> Best regards, >>> Magnus >>> Libriotech >>> _______ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> ___ >>> Koha-devel mailing >>> listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> _______ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> -- >>> Tomás Cohen Arazi >>> Theke Solutions (https://theke.io <http://theke.io/>) >>> ✆ +54 9351 3513384 <+54%209%20351%20351-3384> >>> GPG: B2F3C15F >>> ___ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> ___ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >> >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Carrousel display issue on sandbox
Oooo I did not knew the repos of InLibro have moved. Great :) I suggest you add topic koha-plugin on those repos : https://github.com/topics/koha-plugin Best regards, Le 11/09/2023 à 09:32, Shi Yao Wang a écrit : Hello, here it is: https://github.com/inLibro/koha-plugin-carrousel Shi Yao On 2023-09-11 15:26, Katrin Fischer wrote: Hi, sorry, I should have been more clear: Can you post the link to the repository? Katrin On 11.09.23 21:22, Shi Yao Wang wrote: version 4.1.4 On 2023-09-11 15:13, Katrin Fischer wrote: Hi Shi Yao, as there are multiple versions of the carousel plugin around, which one did you use/install? Hope this helps, Katrin On 11.09.23 21:10, Shi Yao Wang wrote: Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France ___ Koha-devel mailing list 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/
Re: [Koha-devel] Z39.50 marc21 to unimarc
I wonder if this applies to your question: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6536 -Original Message- From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Andrea Furin Sent: Tuesday, March 04, 2014 11:01 AM To: Koha-devel@lists.koha-community.org; Koha Subject: [Koha-devel] Z39.50 marc21 to unimarc Hi. I need to import Z39.50 marc21 results in a unimarc database: is it possible? Tia andrea f. ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] RFC: Retiring of the koha-patches mailing list
I suppose the question is who has the power to do this? Kyle <https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB> http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Jul 12, 2016 at 1:41 PM, Katrin Fischer wrote: > Already +1'ed this some time ago :) > > Who can make it happen? > > Am 12.07.2016 um 15:00 schrieb Marcel de Rooy: > > +1 > > > > -------- > > *Van:* koha-devel-boun...@lists.koha-community.org > > namens Tomas Cohen Arazi > > > > *Verzonden:* dinsdag 12 juli 2016 14:45:21 > > *Aan:* Owen Leonard; koha-devel@lists.koha-community.org > > *Onderwerp:* Re: [Koha-devel] RFC: Retiring of the koha-patches mailing > > list > > > > +1 > > > > El mar., 12 jul. 2016 a las 9:34, Owen Leonard ( > <mailto:oleon...@myacpl.org>>) escribió: > > > > > Does anyone have any strong objections to shutting down the > > mailing list? > > > > +1 to shutting down the patches mailing list. > > > > I haven't heard any objections yet, so let's move forward on it. > > > > -- Owen > > > > -- > > Web Developer > > Athens County Public Libraries > > http://www.myacpl.org > > ___ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org> > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io <http://theke.io/>) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > > > > > > ___ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > _______ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Carrousel display issue on sandbox
Hi Katrin, thank you for confirming the issue. Can anyone else help? Shi Yao On 2023-09-14 13:24, Katrin Fischer wrote: Hi Shi Yao, I have tested the plugin locally and I can confirm that the .js files are not loaded. But, I don't know what's needed to make it work. Maybe one of the other plugin developers could help? Katrin On 12.09.23 08:44, Fridolin SOMERS wrote: Oooo I did not knew the repos of InLibro have moved. Great :) I suggest you add topic koha-plugin on those repos : https://github.com/topics/koha-plugin Best regards, Le 11/09/2023 à 09:32, Shi Yao Wang a écrit : Hello, here it is: https://github.com/inLibro/koha-plugin-carrousel Shi Yao On 2023-09-11 15:26, Katrin Fischer wrote: Hi, sorry, I should have been more clear: Can you post the link to the repository? Katrin On 11.09.23 21:22, Shi Yao Wang wrote: version 4.1.4 On 2023-09-11 15:13, Katrin Fischer wrote: Hi Shi Yao, as there are multiple versions of the carousel plugin around, which one did you use/install? Hope this helps, Katrin On 11.09.23 21:10, Shi Yao Wang wrote: Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/
Re: [Koha-devel] How to see security fixes
BTW,
We have created this bug as #18275. We didnot put the script how to
crawl the data on the bug.
On 15-03-2017 19:27, Devinim Koha Development Team wrote:
Hi,
We have sent the code to the Jonathan Druart as he wanted
and we can get all info without authorization even in 3.20.x, hence it
should be fixed ASAP.
Best regards,
Devinim Koha Development Team
On 15-03-2017 19:17, Stefano Bargioni wrote:
Uh..., probably it is not so good to publish security issues on a
public list.
The official way is
https://koha-community.org/security/
if I'm not wrong.
sb
On 15 Mar 2017, at 16:57, Devinim Koha Development Team
mailto:kohadevi...@devinim.com.tr>> wrote:
Hi,
In that case we can reach the user detailed information without
giving a password by curl.
If you want we can share the code how to get this information
without authentication, from this list.
On 15-03-2017 18:50, Jonathan Druart wrote:
Hi,
authnotrequired is set to 1 because opac-memberentry.pl
<http://opac-memberentry.pl/> is also used by the self registration
feature.
The patron information displayed is based on the logged in user,
not a parameter passed to the script.
Everything looks ok to me.
Regards,
Jonathan
On Wed, 15 Mar 2017 at 12:18 Devinim Koha Development Team
mailto:kohadevi...@devinim.com.tr>> wrote:
Hi all,
In the opac-memberentry.pl <http://opac-memberentry.pl/>
authnotrequired area is 1 by default, in that case, user
information can be reached without given a user authentication
and this can lead some vulnerabilites, do we miss something? We
were not able to understand why it is 1 by default?
Thanks.
On 14-03-2017 11:33, Chris Cormack wrote:
Hi,
Normally once they are released the release maintainer shifts
them out of security. That one got missed, shifted now
Chris
On 14 March 2017 9:13:51 PM NZDT, Devinim Koha Development
Team
<mailto:kohadevi...@devinim.com.tr> wrote:
Hi all,
How can we see the fixes of security bugs?
We've faced with a vulnerability with Bug# 16969 in a new version, but
it's said that it was fixed in 3.22.10.
Thanks.
Devinim Koha Dev. Team
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :http://www.koha-community.org <http://www.koha-community.org/>/
git :http://git.koha-community.org <http://git.koha-community.org/>/
bugs :http://bugs.koha-community.org
<http://bugs.koha-community.org/>/
-- Sent from my Android device with K-9 Mail. Please excuse my
brevity.
_______ Koha-devel
mailing list Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/ git :
http://git.koha-community.org/ bugs :
http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :http://www.koha-community.org/
git :http://git.koha-community.org/
bugs :http://bugs.koha-community.org/
_______ Koha-devel mailing
list Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/ git :
http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :http://www.koha-community.org/
git :http://git.koha-community.org/
bugs :http://bugs.koha-community.org/
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Request for feedback: Bug 20779 - Style refresh for patron detail page
+1 !
:)
On 04.06.2018 18:27, Séverine Queune wrote:
I like that one !
2018-06-04 18:10 GMT+02:00 Owen Leonard <mailto:oleon...@myacpl.org>>:
If there is consensus that the add/edit buttons should be in line with
the section headings:
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75780
<https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75780>
-- Owen
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
<http://bugs.koha-community.org/>
--
*
*
*Séverine QUEUNE*
Administrateur fonctionnel du SIGB
Équipe signalement et exposition des données
Pôle Flux et données
<https://www.youtube-nocookie.com/embed/myZ2K_alngw>
Logo BULAC
Bibliothèque universitaire
des langues et civilisations
65 rue des Grands Moulins
F-75013 PARIS
T +33 1 81 69 *18 55*
www.bulac.fr <http://www.bulac.fr>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Removal of the prog and CCSR themes in 3.18
+1 for removal On Tue, May 13, 2014 at 7:11 AM, Fridolin SOMERS < fridolin.som...@biblibre.com> wrote: > +1 for removal. > > Boostrap is great, long lives Boostrap. > > Le 13/05/2014 08:40, Marc Véron a écrit : > > +1 for removal >> >> Marc >> >> --- >> >> marc veron ag informatik information internet >> Baslerstrasse 50 >> CH - 4123 Allschwil >> >> +41 61 483 84 61 >> >> www.veron.ch >> >> Acrobat / PDF - Lösungen seit 1995 >> Partner für Internet und Content Management >> Mitglied Koha Support Schweiz www.koha-support.ch >> >> >> >> Am 12.05.2014 22:46, schrieb Chris Cormack: >> >>> +1 from me >>> >>> >>> >>> ___ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> > -- > Fridolin SOMERS > Biblibre - Pôles support et système > fridolin.som...@biblibre.com > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] RFC: Retiring of the koha-patches mailing list
Already +1'ed this some time ago :) Who can make it happen? Am 12.07.2016 um 15:00 schrieb Marcel de Rooy: > +1 > > > *Van:* koha-devel-boun...@lists.koha-community.org > namens Tomas Cohen Arazi > > *Verzonden:* dinsdag 12 juli 2016 14:45:21 > *Aan:* Owen Leonard; koha-devel@lists.koha-community.org > *Onderwerp:* Re: [Koha-devel] RFC: Retiring of the koha-patches mailing > list > > +1 > > El mar., 12 jul. 2016 a las 9:34, Owen Leonard ( <mailto:oleon...@myacpl.org>>) escribió: > > > Does anyone have any strong objections to shutting down the > mailing list? > > +1 to shutting down the patches mailing list. > > I haven't heard any objections yet, so let's move forward on it. > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > _______ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 > GPG: B2F3C15F > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Upgrading Koha's license?
+1 for GPL3 from me too -Ursprüngliche Nachricht- Von: koha-devel-boun...@lists.koha-community.org im Auftrag von Chris Cormack Gesendet: Mi 14.11.2012 20:47 An: koha-devel@lists.koha-community.org Betreff: Re: [Koha-devel] Upgrading Koha's license? On 15 November 2012 08:45, Robin Sheat wrote: > Op 15-11-12 08:40, Owen Leonard schreef: >> However, Bootstrap's license is Apache 2.0 which I'm told is >> incompatible with Koha's GPL2 license. >> >> What do we need to do to make inclusion of Bootstrap possible? > > Distribute it as GPLv3: > > http://www.apache.org/licenses/GPL-compatibility.html > http://gplv3.fsf.org/wiki/index.php/Compatible_licenses#GPLv3-compatible_licenses > http://www.fsf.org/blogs/licensing/new-license-recommendations-guide > +1 for GPLv3 Chris > Robin. > > > ___________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] [Koha] Koha packages are available 🎁
Oo my bad, it was in my "Katipo" folder.
I see it in archives :
https://lists.katipo.co.nz/pipermail/koha/2021-December/057162.html
All is good.
Le 29/12/2021 à 21:41, Fridolin SOMERS a écrit :
I'm looking at archives :
https://lists.koha-community.org/pipermail/koha-devel/2021-December/date.html
I dont see it.
Can anyone confirm ?
Le 29/12/2021 à 05:07, Kyle Hall a écrit :
I sent out an email for 21.11, did it get blocked?
Kyle
---
http://www.kylehall.info <http://www.kylehall.info>
ByWater Solutions ( http://bywatersolutions.com
<http://bywatersolutions.com> )
Meadville Public Library ( http://www.meadvillelibrary.org
<http://www.meadvillelibrary.org> )
Crawford County Federated Library System ( http://www.ccfls.org
<http://www.ccfls.org> )
On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>>
wrote:
Hi,
There has been a mail for 20.11.13 release :
https://koha-community.org/koha-20-11-13-released/
<https://koha-community.org/koha-20-11-13-released/>
For other versions I don't see emails.
Here are the details :
20.11.01 release :
https://koha-community.org/koha-21-11-01-released/
<https://koha-community.org/koha-21-11-01-released/>
21.05.08 release :
https://koha-community.org/koha-21-05-08-released/
<https://koha-community.org/koha-21-05-08-released/>
Best regards,
Le 25/12/2021 à 16:02, Mason James a écrit :
> kia ora community,
> the latest Koha packages are available
>
> cheers, Mason
> _______
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
> website : https://www.koha-community.org/
<https://www.koha-community.org/>
> git : https://git.koha-community.org/
<https://git.koha-community.org/>
> bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
-- Fridolin SOMERS mailto:fridolin.som...@biblibre.com>>
Software and system maintainer 🦄
BibLibre, France
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : https://www.koha-community.org/
<https://www.koha-community.org/>
git : https://git.koha-community.org/
<https://git.koha-community.org/>
bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Fridolin SOMERS
Software and system maintainer 🦄
BibLibre, France
___
Koha-devel mailing list
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/
[Koha-bugs] [Bug 4828] Erroneous SIP2 behaviour with non ascii characters
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4828 Ian Walls changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||DUPLICATE --- Comment #4 from MJ Ray (software.coop) 2011-03-02 18:47:37 UTC --- This bug is mentioned in: Bug 4828: Clean diacritics from SIP-writtenmessages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013882.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013884.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013886.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013888.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013891.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013892.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013894.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013896.html Bug 4828: Clean diacritics from SIP-written messages http://lists.koha-community.org/pipermail/koha-patches/2011-February/013887.html --- Comment #5 from Ian Walls 2011-08-26 16:34:41 UTC --- *** This bug has been marked as a duplicate of bug 6765 *** -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA Contact for the bug. ___ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] How to see security fixes
Hi,
We have sent the code to the Jonathan Druart as he wanted
and we can get all info without authorization even in 3.20.x, hence it
should be fixed ASAP.
Best regards,
Devinim Koha Development Team
On 15-03-2017 19:17, Stefano Bargioni wrote:
Uh..., probably it is not so good to publish security issues on a
public list.
The official way is
https://koha-community.org/security/
if I'm not wrong.
sb
On 15 Mar 2017, at 16:57, Devinim Koha Development Team
mailto:kohadevi...@devinim.com.tr>> wrote:
Hi,
In that case we can reach the user detailed information without
giving a password by curl.
If you want we can share the code how to get this information without
authentication, from this list.
On 15-03-2017 18:50, Jonathan Druart wrote:
Hi,
authnotrequired is set to 1 because opac-memberentry.pl
<http://opac-memberentry.pl/> is also used by the self registration
feature.
The patron information displayed is based on the logged in user, not
a parameter passed to the script.
Everything looks ok to me.
Regards,
Jonathan
On Wed, 15 Mar 2017 at 12:18 Devinim Koha Development Team
mailto:kohadevi...@devinim.com.tr>> wrote:
Hi all,
In the opac-memberentry.pl <http://opac-memberentry.pl/>
authnotrequired area is 1 by default, in that case, user
information can be reached without given a user authentication
and this can lead some vulnerabilites, do we miss something? We
were not able to understand why it is 1 by default?
Thanks.
On 14-03-2017 11:33, Chris Cormack wrote:
Hi,
Normally once they are released the release maintainer shifts
them out of security. That one got missed, shifted now
Chris
On 14 March 2017 9:13:51 PM NZDT, Devinim Koha Development Team
<mailto:kohadevi...@devinim.com.tr> wrote:
Hi all,
How can we see the fixes of security bugs?
We've faced with a vulnerability with Bug# 16969 in a new version, but
it's said that it was fixed in 3.22.10.
Thanks.
Devinim Koha Dev. Team
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :http://www.koha-community.org <http://www.koha-community.org/>/
git :http://git.koha-community.org <http://git.koha-community.org/>/
bugs :http://bugs.koha-community.org
<http://bugs.koha-community.org/>/
-- Sent from my Android device with K-9 Mail. Please excuse my
brevity.
_______ Koha-devel
mailing list Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/ git :
http://git.koha-community.org/ bugs :
http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :http://www.koha-community.org/
git :http://git.koha-community.org/
bugs :http://bugs.koha-community.org/
_______ Koha-devel mailing
list Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/ git :
http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
___________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plack only
We are using a plack.psgi directly inspired from debian/templates/plack.psgi, we just replace some paths. And we have a SystemD unit to deamonize. I will detail this on the wiki page maybe ? Le 08/02/2018 à 01:10, David Cook a écrit : +1 Julian I've been avoiding Plack because we don't use Debian, but at some point I'll have to use it, and it would be great if it was community supported beyond just Debian. I'm happy to help test things, so long as I can have some guidance on what to do. (I'd love for the multi-tenant management tools to be de-debianized as well, but totally recognize that money/time is an obstacle. It's something I'd like to look at more in the future myself, but occupied with non-Koha projects at the moment...) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Julian Maurice Sent: Thursday, 8 February 2018 3:50 AM To: Tomas Cohen Arazi Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only Are they really in sync ? They look very different (I cannot use the rest api with misc/plack/koha.psgi for instance). IMO a good starting point would be to move debian/templates/plack.psgi outside of debian/ and make it the .psgi reference file for all types of install (and remove misc/plack in the process). Any thoughts ? Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : Good point, Julian. You are right. Basically, we ship misc/plack/* which we keep in sync with debian/templates/plack.psgi. I would love to spend some time de-debianizing hte multi-tenant management tools, but its been hard to find sponsorship or time for it. Most people are comfortable with Debian it seems. Regards El mié., 7 feb. 2018 a las 9:26, Julian Maurice (mailto:julian.maur...@biblibre.com>>) escribió: What about people that do not use Debian ? It seems that there is no "standard" way to use Plack outside of the Debian world, and it looks like 90% of https://wiki.koha-community.org/wiki/Plack is outdated. If we abandon CGI support, I think we should first provide a clear setup documentation. I would happily rewrite the wiki page, but I'm not sure of what to write (how to setup Plack on dev install for instance, or 'standard' install without debian packages). Or maybe I'm missing some important up-to-date documentation about Plack ? (somewhat) related bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 Le 06/02/2018 à 19:50, Tomas Cohen Arazi a écrit : > For running in Plack-mode, people needs to: > > sudo koha-plack --enable > sudo koha-plack --start > sudo systemctl restart apache2 > > after creating the . > > What I meant is that we should have people avoid the need for those > commands. And people with specific needs that require non-Plack setups > can do it. > > I started thinking of this in the context of bug 20134 [1] BUT also in > the context of bugs 18315 [2] and 7174 [3]. > > Both of the latter bugs propose interesting ways of refactoring > authentication, and I'm sure abandoning CGI-mode could help simplify the > process. > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20134 > [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 > [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 > > El mar., 6 feb. 2018 a las 11:00, Julian Maurice > (mailto:julian.maur...@biblibre.com> <mailto:julian.maur...@biblibre.com <mailto:julian.maur...@biblibre.com>>>) > escribió: > > What does that mean to "make Plack the default" exactly ? > > Le 06/02/2018 à 14:31, Tomas Cohen Arazi a écrit : > > I would like to know if you think there's any reason to keep the CGI > > mode as default in Koha deployments. I think we should make Plack the > > default. There are some issues, tough. > > > > But if we set that goal, we could focus on fixing them. > > > > What do you think? > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io <http://theke.io/>) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > > > > > > _______ > > Koha-devel mailing list > > Koha-deve
Re: [Koha-devel] Carrousel display issue on sandbox
Hi Shi Yao, I have tested the plugin locally and I can confirm that the .js files are not loaded. But, I don't know what's needed to make it work. Maybe one of the other plugin developers could help? Katrin On 12.09.23 08:44, Fridolin SOMERS wrote: Oooo I did not knew the repos of InLibro have moved. Great :) I suggest you add topic koha-plugin on those repos : https://github.com/topics/koha-plugin Best regards, Le 11/09/2023 à 09:32, Shi Yao Wang a écrit : Hello, here it is: https://github.com/inLibro/koha-plugin-carrousel Shi Yao On 2023-09-11 15:26, Katrin Fischer wrote: Hi, sorry, I should have been more clear: Can you post the link to the repository? Katrin On 11.09.23 21:22, Shi Yao Wang wrote: version 4.1.4 On 2023-09-11 15:13, Katrin Fischer wrote: Hi Shi Yao, as there are multiple versions of the carousel plugin around, which one did you use/install? Hope this helps, Katrin On 11.09.23 21:10, Shi Yao Wang wrote: Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/
Re: [Koha-devel] To React or not to React
I think Katrin and I both are probably referring to this file: <https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=17297&attachment=55545> https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=17297&attachment=55545 It embeds HTML and hardcoded strings in the .js file. It would be great to see a translateable version. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Kyle Hall Sent: Tuesday, 20 September 2016 11:22 PM To: Katrin Cc: Koha Devel Subject: Re: [Koha-devel] To React or not to React Katrin I'm not quite sure what you mean. When I wrote we translate these files the same way we do other js files, I meant that we define the strings to be translated either in the script template file or in an include file and then only use the var storing the string in the js file. React is just Javascript and what we've been doing should work absolutely fine. I'll update my POC to be translatable when I get some time! If this is not what you meant Katrin, please let me know! Kyle <https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB> http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Sep 19, 2016 at 11:51 PM, Katrin mailto:katrin.fischer...@web.de> > wrote: Also, how would this React POC go in terms of translations? React is just Javascript, and is translated the same way translate all our other js files. We don't translate js files at the moment - which may be debatable. One benefit at the moment of keeping the strings only in the templates is that we don't copy the js files as we do with the template files. I think this should be solvable, but it's something to keep in mind. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -Original Message- > From: koha-devel-boun...@lists.koha-community.org > <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel- > <mailto:koha-devel-> > boun...@lists.koha-community.org <mailto:boun...@lists.koha-community.org> ] > On Behalf Of Owen Leonard > Sent: Monday, 19 September 2016 11:33 PM > To: Koha Devel <mailto:koha-devel@lists.koha-community.org> > > Subject: Re: [Koha-devel] To React or not to React > > > Another thing is that you need nodejs to compile it so is another > > thing to throw on the stack. > > Isn't this the kind of dependency requirement that killed my request to > introduce a front-end build tool like Grunt or Gulp? > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ <http://community.org/> bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Last failing test fixed...
Great ! Saw some passing QA this morning :) Van: koha-devel-boun...@lists.koha-community.org [koha-devel-boun...@lists.koha-community.org] namens Mark Tompsett [mtomp...@hotmail.com] Verzonden: vrijdag 1 april 2016 16:54 Aan: koha-devel@lists.koha-community.org Onderwerp: [Koha-devel] Last failing test fixed... Greetings, I continued looking at the failing tests more. Has anyone worked on solving the Circulation_Issuingrule test failure from http://jenkins.koha-community.org/view/Koha%20master/job/Koha_Master_D7/680/testReport/? If not, check out 16186 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16186) 16185 and 16186 should be the last of the problems that need sign off. GPML, Mark Tompsett ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Request for feedback: Bug 20779 - Style refresh for patron detail page
+1 On Mon, Jun 4, 2018 at 2:20 PM, Katrin Fischer wrote: > +1 ! > > :) > > > On 04.06.2018 18:27, Séverine Queune wrote: > > I like that one ! > > 2018-06-04 18:10 GMT+02:00 Owen Leonard : > >> If there is consensus that the add/edit buttons should be in line with >> the section headings: >> >> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75780 >> >> -- Owen >> _______ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> > > > > -- > > *Séverine QUEUNE* > Administrateur fonctionnel du SIGB > Équipe signalement et exposition des données > Pôle Flux et données > > > <https://www.youtube-nocookie.com/embed/myZ2K_alngw> > [image: Logo BULAC] > > Bibliothèque universitaire > des langues et civilisations > > > 65 rue des Grands Moulins > F-75013 PARIS > T +33 1 81 69 *18 55* > www.bulac.fr > > > ___ > Koha-devel mailing > listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Auto-increment problem has re-emerged
We've upgraded to MariaDB 10.3.13.
Thanks Fridolin, thanks Tomas.
Bob
On 7/3/19 9:22 pm, Tomas Cohen Arazi wrote:
Yesterday we noticed the sysadmin made a typo on the file and it was
causing the init file to be skipped silently on startup. I wrote a
small script to avoid human errors
I suggest you try that SQL file right now and see if it loads.
I can share that simple script.
El jue., 7 de marzo de 2019 05:02, Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>>
escribió:
Hi
Do you have the init script in MySQL/MariaDB ?
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup
We have it under Xenial and no problem anymore with autoincrements.
Regards,
Le 27/02/2019 à 06:24, Bob Birchall a écrit :
> We're running multiple instances of Koha 18.05.06 installed on
stretch
> from packages.
>
> In recent days we've struck the auto-increment problem several
times, in
> relation to issues / old_issues. Known fixes are applied.
>
> Is anyone else experiencing this?
>
> Thanks,
> Bob
>
> Calyx
> _______
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
--
Fridolin SOMERS
<mailto:fridolin.som...@biblibre.com>>
BibLibre, France - software and system maintainer
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] NorwegianPatronDB
FYI, if you’re using the Crypt::GCrypt module from CPAN (ie you’re not using a Debian-based system with libcrypt-gcrypt-perl), Koha is probably going to be unable to load Koha::NorwegianPatronDB. The CPAN module has issues which the Debian team have patched, and the CPAN author appears to have zero interest in patching the CPAN version (or talking about it at all). I wonder what CPAN’s policy is on abandoned modules… My point is that if you’re not using the Debian package, you’re that Crypt::GCrypt dependency appears to always fail now. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Tomas Cohen Arazi Sent: Saturday, 13 February 2016 2:52 AM To: Manos PETRIDIS Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] NorwegianPatronDB I think we should ship with all the dependencies. We cannot make people's Koha break if they enable some feature. 2016-02-11 17:47 GMT-03:00 Manos PETRIDIS mailto:egpetri...@gmail.com> >: Apparently libsoap-lite-perl, libcrypt-gcrypt-perl and libconvert-basen-perl should be/remain mandatory in 3.22, as they are required by a non-optional module, even if the functionality it provides is not used. 2016-02-11 5:06 GMT+02:00 Mark Tompsett mailto:mtomp...@hotmail.com> >: Greetings, It seems that “$debug && warn” is a popular style used in C4/Member already. I don’t think a system preference is needed. Just a $debug prepend, perhaps? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15795 Sign it off, kill it, suggest a counter-patch, whatever. I do think this addresses the issue. GPML, Mark Tompsett From: David Cook <mailto:dc...@prosentient.com.au> Sent: Wednesday, February 10, 2016 6:40 PM To: 'Philippe Blouin' <mailto:philippe.blo...@inlibro.com> Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] NorwegianPatronDB I think you’re right, Philippe. I’ve noticed the same thing. In fact, the “Unable to load Koha::NorwegianPatronDB” was added after the fact to stop the absence of those libraries causing Koha to die. I don’t necessarily see the point of having that warning there though, as most Koha users probably aren’t going to use the NorwegianPatronDB. Maybe that could have a system preference… so the warns (or the dying) only happens when the system preference is set? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Philippe Blouin Sent: Thursday, 11 February 2016 8:47 AM To: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: [Koha-devel] NorwegianPatronDB Hi! I'm working on 3.22.02 and my logs are FILLED with the following warnings: Members.pm: Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/acqui/booksellers.pl admin-home.pl <http://admin-home.pl> : Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/admin/preferences.pl I look at the code, and beside wondering why that custom feature is so profoundly imbricated into master Koha, I was wondering what is not working. So I hacked the code to add verbose => 1 on the can_load call, and found that NorwegianPatronDB was not compiling because it was missing the following libraries: apt-get -y install libsoap-lite-perl apt-get -y install libcrypt-gcrypt-perl apt-get -y install libconvert-basen-perl Those modules are specified as NOT mandatory in 3.22. As such, I should not be flooded with Norwegian errors because they are not available, for a module which I and most do not care for. Or am I getting it wrong? Thanks Philippe _ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _____
Re: [Koha-devel] koha for e-resource management
Hi! We just started to use eResources in Koha. We link from the Bibliographic detail-view to the eResource vendors web-site. And authenticate from there using SIP2, protected with an IP-limit enforced in a firewall rule. Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux! On 04.09.2015 15:49, long_sam.tw wrote: Hi, François A-Z https://www.ebscohost.com/discovery/technology/a-to-z Advanced ERM products Discovery Service Serials Solutions Summon Ex Libris Primo Central OCLC WorldCat Local EBSCO Discovery Service Innovative Interface You can refer http://americanlibrariesmagazine.org/2015/05/01/library-systems-report/ Marshall Breeding's wrote a very detailed. BR, longsam Francois Charbonnier <mailto:francois.charbonn...@inlibro.com> 於 2015/9/4 (週五) 8:24 PM 寫道﹕ Hello Longsam, Do you have examples of those ILS? I'm curious about what they call ERM in their systems. Thanks. François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonn...@inlibro.com<mailto:francois.charbonn...@inlibro.com> inLibro | pour esprit libre | www.inLibro.com<http://www.inlibro.com/> Le 2015-09-04 04:16, long_sam.tw a écrit : Dear koha folks. Recently , many ILS provide e-resource management for library. In koha, Are there some plan about e-resource management in the future? BR, longsam ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plack only
+1 Julian I've been avoiding Plack because we don't use Debian, but at some point I'll have to use it, and it would be great if it was community supported beyond just Debian. I'm happy to help test things, so long as I can have some guidance on what to do. (I'd love for the multi-tenant management tools to be de-debianized as well, but totally recognize that money/time is an obstacle. It's something I'd like to look at more in the future myself, but occupied with non-Koha projects at the moment...) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Julian Maurice Sent: Thursday, 8 February 2018 3:50 AM To: Tomas Cohen Arazi Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Plack only Are they really in sync ? They look very different (I cannot use the rest api with misc/plack/koha.psgi for instance). IMO a good starting point would be to move debian/templates/plack.psgi outside of debian/ and make it the .psgi reference file for all types of install (and remove misc/plack in the process). Any thoughts ? Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : > Good point, Julian. You are right. > > Basically, we ship misc/plack/* which we keep in sync with > debian/templates/plack.psgi. > > I would love to spend some time de-debianizing hte multi-tenant > management tools, but its been hard to find sponsorship or time for it. > Most people are comfortable with Debian it seems. > > Regards > > El mié., 7 feb. 2018 a las 9:26, Julian Maurice > (mailto:julian.maur...@biblibre.com>>) > escribió: > > What about people that do not use Debian ? It seems that there is no > "standard" way to use Plack outside of the Debian world, and it looks > like 90% of https://wiki.koha-community.org/wiki/Plack is outdated. > If we abandon CGI support, I think we should first provide a clear setup > documentation. I would happily rewrite the wiki page, but I'm not sure > of what to write (how to setup Plack on dev install for instance, or > 'standard' install without debian packages). > Or maybe I'm missing some important up-to-date documentation about > Plack ? > > (somewhat) related bug: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 > > Le 06/02/2018 à 19:50, Tomas Cohen Arazi a écrit : > > For running in Plack-mode, people needs to: > > > > sudo koha-plack --enable > > sudo koha-plack --start > > sudo systemctl restart apache2 > > > > after creating the . > > > > What I meant is that we should have people avoid the need for those > > commands. And people with specific needs that require non-Plack setups > > can do it. > > > > I started thinking of this in the context of bug 20134 [1] BUT also in > > the context of bugs 18315 [2] and 7174 [3]. > > > > Both of the latter bugs propose interesting ways of refactoring > > authentication, and I'm sure abandoning CGI-mode could help > simplify the > > process. > > > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20134 > > [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 > > [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 > > > > El mar., 6 feb. 2018 a las 11:00, Julian Maurice > > (mailto:julian.maur...@biblibre.com> > <mailto:julian.maur...@biblibre.com > <mailto:julian.maur...@biblibre.com>>>) > > escribió: > > > > What does that mean to "make Plack the default" exactly ? > > > > Le 06/02/2018 à 14:31, Tomas Cohen Arazi a écrit : > > > I would like to know if you think there's any reason to keep > the CGI > > > mode as default in Koha deployments. I think we should make > Plack the > > > default. There are some issues, tough. > > > > > > But if we set that goal, we could focus on fixing them. > > > > > > What do you think? > > > -- > > > Tomás Cohen Arazi > > > Theke Solutions (https://theke.io <http://theke.io/>) > > > ✆ +54 9351 3513384 > > > > GPG: B2F3C15F > > > > > > > > > _
Re: [Koha-devel] items.itype FK constraint?
We can set a FK constraint while allowing NULL too. The reason for me to post this on the list is to hear (probably) historical reasons for this constraint not to be set already at DB level. Thanks for your replies! El mar., 30 jul. 2019 a las 16:05, Katrin Fischer () escribió: > Hi Sophie, > > I think on database level we need to allow NULL, because of the > item-level_itype 'record level' setting. I understand that itemtypes are > not set on item level at all in that case? > > Katrin > > On 30.07.19 16:32, Sophie Meynieux wrote: > > Hello, > > But itype must not be null if syspref item-level_itype is on, isn't it ? > > S. Meynieux > > -- > Responsable support > BibLibre > + 33 (0)4 91 81 35 08http://www.biblibre.com > > Le 29/07/2019 à 20:17, Katrin Fischer a écrit : > > +1 > > With a on delete set null? > On 29.07.19 19:39, Tomas Cohen Arazi wrote: > > Why shouldn't we add it :-D > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > > ___ > Koha-devel mailing > listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > ___ > Koha-devel mailing > listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > ___ > Koha-devel mailing > listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Translate Koha Plugins?
https://gitlab.com/thekesolutions/plugins/koha-plugin-pay-via-paypal Le lun. 15 juin 2020 à 11:05, Fridolin SOMERS a écrit : > > > Le 15/06/2020 à 10:47, Jonathan Druart a écrit : > > There is koha-plugin-pay-via-paypal. > > I cant find this plugin. Is it on GitHub or somewhere ? > > > > > Le lun. 15 juin 2020 à 10:19, Fridolin SOMERS > > mailto:fridolin.som...@biblibre.com>> a > > écrit : > > > > Hi, > > > > Unfortunably I think there is not. > > > > I know plugins like Inlibro Carrousel did it manually : > > > > > https://git.biblibre.com/biblibre/koha-plugin-inlibro-carrousel/src/branch/master/Koha/Plugin/Carrousel > > > > We should provide a common way to do this. > > > > Best regards, > > > > Le 11/06/2020 à 02:13, dc...@prosentient.com.au > > <mailto:dc...@prosentient.com.au> a écrit : > > > Hi all, > > > > > > Is there an existing mechanism for translating Koha Plugins? > > > > > > I’m (slowly) working on some plugins, and there are folk in the > > Czech > > > Republic who would like to use them but not in English. > > > > > > David Cook > > > > > > Systems Librarian > > > > > > Prosentient Systems > > > > > > 72/330 Wattle St > > > > > > Ultimo, NSW 2007 > > > > > > Australia > > > > > > Office: 02 9212 0899 > > > > > > Online: 02 8005 0595 > > > > > > > > > ___ > > > Koha-devel mailing list > > > Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org> > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > > website : http://www.koha-community.org/ > > > git : http://git.koha-community.org/ > > > bugs : http://bugs.koha-community.org/ > > > > > > > -- > > Fridolin SOMERS > <mailto:fridolin.som...@biblibre.com>> > > Software and system maintainer 🦄 > > BibLibre, France > > ___ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > > <mailto:Koha-devel@lists.koha-community.org> > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Fridolin SOMERS > Software and system maintainer 🦄 > BibLibre, France > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Indexes of Physical presentation
Ah, that explains, thx Bernardo! :) Am 18.11.2015 um 17:49 schrieb Bernardo Gonzalez Kriegel: > It's UNIMARC specific :) > > -- > Bernardo Gonzalez Kriegel > bgkrie...@gmail.com <mailto:bgkrie...@gmail.com> > > On Wed, Nov 18, 2015 at 1:15 PM, Fridolin SOMERS > mailto:fridolin.som...@biblibre.com>> wrote: > > Hie Katrin, > > 'physical presentation' is just the name of one of the search fields > in advanced search. > In intranet you must click on 'Coded information filters' to see it. > > I don't know if it is UNIMARC-only, can you check with the demo > websites ? > > Best regards. > > > Le 10/11/2015 23:14, Katrin Fischer a écrit : > > Hi Fridolin, > > I have tried to look into this, but I am not sure what you mean with > 'physical presentation'. Can you explain a bit more? Is this UNIMARC > specific? > > Katrin > > Am 05.11.2015 um 09:33 schrieb Fridolin SOMERS: > > Hie, > > In intranet search, physical presentation uses index ff8-23. > In opac search, physical presentation uses index Material-type. > > This is strange because the search always use the coded > values, meaning > it is ff8-23 the correct index. > Do you agree ? > > Regards, > > > _______ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > -- > Fridolin SOMERS > Biblibre - Pôles support et système > fridolin.som...@biblibre.com <mailto:fridolin.som...@biblibre.com> > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Problems with suggestions
At 05:07 PM 9/24/2012 +0200, Fridolyn SOMERS wrote: In my opinion, the current branch filtering can be a behavior common to all intranet pages. Maybe a combo-box next to login. In this case, it would be easy to know what is the current filtering. It would be initialized with user's branch and its current value could be saved in cookie to remain after a deconnexion. It would also manage the "IndependantBranch" syspref. My 2c. +1 this would be a very logical step forward, unifying several loose ends. a+ -- paul Le 24/09/2012 09:45, Fischer, Katrin a écrit : I think I would still prefer a system preference here. But I also like the idea to remember the last state for each user. But I think this would be harder to do - while a system preference might be the easier way to go back to former behaviour? Katrin -Original Message- From: <mailto:koha-devel-boun...@lists.koha-community.org>koha-devel-boun...@lists.koha-community.org [<mailto:koha-devel>mailto:koha-devel- <mailto:boun...@lists.koha-community.org>boun...@lists.koha-community.org] On Behalf Of Gaetan Boisson Sent: Monday, September 24, 2012 9:29 AM To: <mailto:koha-devel@lists.koha-community.org>koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Problems with suggestions I completely agree that this is confusing, and it took my a while to figure out that when you reach this screen the filter is not empty. (The site is picked in "acquisition information"), actually if you play a little with the filter, then click "clear", you go back to a setting where you only see suggestions made for the site you are connected to. Like Robin suggested, i think adding a sentence like "By default you will only see suggestions made at the site you are connected to. Use the filter to change this behaviour." would solve the problem without resorting to fancy developments, unicorns and poneys. Just my 2 cents ;) Le lundi 24 septembre 2012 à 18:24 +1200, Robin Sheat a écrit : We have had a few queries about suggestions not working correctly in 3.8, that seem to be the result of this: <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7300#c6>http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7300#c6 can we decide the path to solving this? Making suggestions hidden by default is distinctly a regression for many libraries. On the other hand, filtering by branch is a genuinely useful thing, as is the ability to filter by default. My suggestion (to avoid a syspref) is that it has big, obvious words saying it's filtered and a button to show all, and it remembers the last state that user had (filtered or not) to show them next time. But I don't have any funding in line for this, so it'd really be up to whoever had the time to implement it. (It also maybe exposed a weakness in the patch signoff workflow, as it didn't really get any external review before going in, but that's another conversation perhaps.) _______ Koha-devel mailing list <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha-community.org/>http://git.koha-community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/ -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille <mailto:gaetan.bois...@biblibre.com>gaetan.bois...@biblibre.com ___________ Koha-devel mailing list <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha>http://git.koha- community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/ _______ Koha-devel mailing list <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha-community.org/>http://git.koha-community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/ -- Fridolyn SOMERS Biblibre - Pôle Support 09 74 77 07 15 <mailto:fridolyn.som...@biblibre.com>fridolyn.som...@biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-commu
Re: [Koha] [Koha-devel] Koha packages are available 🎁
I'm looking at archives :
https://lists.koha-community.org/pipermail/koha-devel/2021-December/date.html
I dont see it.
Can anyone confirm ?
Le 29/12/2021 à 05:07, Kyle Hall a écrit :
I sent out an email for 21.11, did it get blocked?
Kyle
---
http://www.kylehall.info <http://www.kylehall.info>
ByWater Solutions ( http://bywatersolutions.com
<http://bywatersolutions.com> )
Meadville Public Library ( http://www.meadvillelibrary.org
<http://www.meadvillelibrary.org> )
Crawford County Federated Library System ( http://www.ccfls.org
<http://www.ccfls.org> )
On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>> wrote:
Hi,
There has been a mail for 20.11.13 release :
https://koha-community.org/koha-20-11-13-released/
<https://koha-community.org/koha-20-11-13-released/>
For other versions I don't see emails.
Here are the details :
20.11.01 release :
https://koha-community.org/koha-21-11-01-released/
<https://koha-community.org/koha-21-11-01-released/>
21.05.08 release :
https://koha-community.org/koha-21-05-08-released/
<https://koha-community.org/koha-21-05-08-released/>
Best regards,
Le 25/12/2021 à 16:02, Mason James a écrit :
> kia ora community,
> the latest Koha packages are available
>
> cheers, Mason
> ___
> Koha-devel mailing list
> koha-de...@lists.koha-community.org
<mailto:koha-de...@lists.koha-community.org>
>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
> website : https://www.koha-community.org/
<https://www.koha-community.org/>
> git : https://git.koha-community.org/
<https://git.koha-community.org/>
> bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Fridolin SOMERS
<mailto:fridolin.som...@biblibre.com>>
Software and system maintainer 🦄
BibLibre, France
_______
Koha-devel mailing list
koha-de...@lists.koha-community.org
<mailto:koha-de...@lists.koha-community.org>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : https://www.koha-community.org/
<https://www.koha-community.org/>
git : https://git.koha-community.org/ <https://git.koha-community.org/>
bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Fridolin SOMERS
Software and system maintainer 🦄
BibLibre, France
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha-devel] Plugin hooks on datas and store()
Mmmm interesting.
Why not send the $self object to plugin
and call SUPER::store() after hook ?
Best regards,
Le 10/03/2021 à 09:22, Jonathan Druart a écrit :
From perlobj pod:
"The |SUPER| pseudo-class is resolved from the package where the call is
made. It is /not/ resolved based on the object's class."
You can still call $item->_result->update.
I suggest you open a bug report to add a no_trigger flag to
Koha::Object->store (like we did in Koha::Objects).
Also spotted, at the end of store:
193 my $result = $self->SUPER::store;
202 $self->get_from_storage->_after_item_action_hooks({ action =>
$action });
203
204 return $result;
That's wrong!
Le mar. 9 mars 2021 à 09:32, Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>> a
écrit :
Yop
I've tried with :
sub after_item_action {
my ( $self, $params ) = @_;
warn "AFTER ITEM ACTION";
my $item = $params->{item};
$item->itemnotes("Edited at " . localtime);
}
Calling $item->SUPER::store() generates an error :
Plugin error (Example Kitchen-Sink Plugin): Can't locate object method
"store" via package "Koha::Plugin::Com::ByWaterSolutions::KitchenSink"
at
/mnt/git/koha-plugin-kitchen-sink/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm
line 580.
Surely only Koha::Item can call SUPER.
Adding $self->SUPER::store() at the end of Koha::Item->store() does
also
not work.
Is it because of "get_from_storage" ?
$self->get_from_storage->_after_item_action_hooks({ action =>
$action });
The _after_item_action_hooks method is called not on object $self
but on
a copy ?
Best regards,
Le 08/03/2021 à 11:49, Jonathan Druart a écrit :
> I wouldn't add other hooks, they are "_after_item_action_hooks" for
> creation and modification.
> "After item creation" should allow you to modify the item, unless we
> need a "pre store" hook.
> I had a look at the code and I didn't find any problems.
> Fridolin, what did you try exactly, can you share the code?
>
> Le lun. 8 mars 2021 à 11:17, Tomas Cohen Arazi
mailto:tomasco...@gmail.com>
> <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>>> a
écrit :
>
> Maybe you need some other hook. Ones that allows you to make
changes
> to the object right before it is stored instead of this one, that
> gets the 'just updated' object.
> When I added 'after' hooks for biblios and items actions, the
idea
> was that they should act as triggers for other actions: in my
case,
> fill a zebraqueue-ish table my plugin uses.
>
> El lun, 8 mar 2021 a las 5:11, Fridolin SOMERS
> (mailto:fridolin.som...@biblibre.com>
> <mailto:fridolin.som...@biblibre.com
<mailto:fridolin.som...@biblibre.com>>>) escribió:
>
> Hi,
>
> While testing new hook :
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>
>
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>
>
> I faced a problem :
> How can I modify the current patron object ?
> Since we are in the store() method of that object and
inside a
> transation.
> I tried to call $self->SUPER::store(); but does not work.
>
> Should we implement this possiblity or document hooks to
say it is
> impossible.
>
> Thanks a lot for your help :D
>
> Best regards,
>
> --
> Fridolin SOMERS mailto:fridolin.som...@biblibre.com>
> <mailto:fridolin.som...@biblibre.com
<mailto:fridolin.som...@biblibre.com>>>
> Software and system maintainer 🦄
> BibLibre, France
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
> <mailto:Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>>
>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
>
Re: [Koha-devel] Plack only
Are they really in sync ? They look very different (I cannot use the rest api with misc/plack/koha.psgi for instance). IMO a good starting point would be to move debian/templates/plack.psgi outside of debian/ and make it the .psgi reference file for all types of install (and remove misc/plack in the process). Any thoughts ? Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : > Good point, Julian. You are right. > > Basically, we ship misc/plack/* which we keep in sync with > debian/templates/plack.psgi. > > I would love to spend some time de-debianizing hte multi-tenant > management tools, but its been hard to find sponsorship or time for it. > Most people are comfortable with Debian it seems. > > Regards > > El mié., 7 feb. 2018 a las 9:26, Julian Maurice > (mailto:julian.maur...@biblibre.com>>) > escribió: > > What about people that do not use Debian ? It seems that there is no > "standard" way to use Plack outside of the Debian world, and it looks > like 90% of https://wiki.koha-community.org/wiki/Plack is outdated. > If we abandon CGI support, I think we should first provide a clear setup > documentation. I would happily rewrite the wiki page, but I'm not sure > of what to write (how to setup Plack on dev install for instance, or > 'standard' install without debian packages). > Or maybe I'm missing some important up-to-date documentation about > Plack ? > > (somewhat) related bug: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 > > Le 06/02/2018 à 19:50, Tomas Cohen Arazi a écrit : > > For running in Plack-mode, people needs to: > > > > sudo koha-plack --enable > > sudo koha-plack --start > > sudo systemctl restart apache2 > > > > after creating the . > > > > What I meant is that we should have people avoid the need for those > > commands. And people with specific needs that require non-Plack setups > > can do it. > > > > I started thinking of this in the context of bug 20134 [1] BUT also in > > the context of bugs 18315 [2] and 7174 [3]. > > > > Both of the latter bugs propose interesting ways of refactoring > > authentication, and I'm sure abandoning CGI-mode could help > simplify the > > process. > > > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20134 > > [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 > > [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 > > > > El mar., 6 feb. 2018 a las 11:00, Julian Maurice > > (mailto:julian.maur...@biblibre.com> > <mailto:julian.maur...@biblibre.com > <mailto:julian.maur...@biblibre.com>>>) > > escribió: > > > > What does that mean to "make Plack the default" exactly ? > > > > Le 06/02/2018 à 14:31, Tomas Cohen Arazi a écrit : > > > I would like to know if you think there's any reason to keep > the CGI > > > mode as default in Koha deployments. I think we should make > Plack the > > > default. There are some issues, tough. > > > > > > But if we set that goal, we could focus on fixing them. > > > > > > What do you think? > > > -- > > > Tomás Cohen Arazi > > > Theke Solutions (https://theke.io <http://theke.io/>) > > > ✆ +54 9351 3513384 > > > > GPG: B2F3C15F > > > > > > > > > _______ > > > Koha-devel mailing list > > > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > <mailto:Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org>> > > > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > > website : http://www.koha-community.org/ > > > git : http://git.koha-community.org/ > > > bugs : http://bugs.koha-community.org/ > > > > > > > -- > > Julian Maurice <mailto:julian.maur...@biblibre.com> > > <mailto:julian.maur...@biblibre.com > <mailto:julian.maur...@biblibre.com>>> > > BibLibre > > __
Re: [Koha-devel] NorwegianPatronDB
Hi Blou, The Debian package version should be fine. It’s the CPAN version which is not fine. While this isn’t a problem for Debian users, it is a problem for those of us who don’t use Debian. I’ve tried contacting the CPAN author but they’ve ignored or not received my messages. I see Martin has emailed as well though, so I’ll look at that now… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Philippe Blouin [mailto:philippe.blo...@inlibro.com] Sent: Tuesday, 16 February 2016 12:50 AM To: David Cook ; 'Tomas Cohen Arazi' ; 'Manos PETRIDIS' Cc: koha-devel@lists.koha-community.org Subject: [***SPAM*** Score/Req: 05.5/5.0] Re: [Koha-devel] NorwegianPatronDB Actually, I did fix it using the debian package on debian 7.5. Not sure if the module worked, but the warning disappeared (which then prompted my original email) Philippe Blouin, Responsable du développement informatique Tél. : (888) 604-2627 <mailto:philippe.blo...@inlibro.com> philippe.blo...@inlibro.com inLibro | pour esprit libre | <http://www.inLibro.com> www.inLibro.com On 02/14/2016 05:20 PM, David Cook wrote: FYI, if you’re using the Crypt::GCrypt module from CPAN (ie you’re not using a Debian-based system with libcrypt-gcrypt-perl), Koha is probably going to be unable to load Koha::NorwegianPatronDB. The CPAN module has issues which the Debian team have patched, and the CPAN author appears to have zero interest in patching the CPAN version (or talking about it at all). I wonder what CPAN’s policy is on abandoned modules… My point is that if you’re not using the Debian package, you’re that Crypt::GCrypt dependency appears to always fail now. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Tomas Cohen Arazi Sent: Saturday, 13 February 2016 2:52 AM To: Manos PETRIDIS <mailto:egpetri...@gmail.com> Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] NorwegianPatronDB I think we should ship with all the dependencies. We cannot make people's Koha break if they enable some feature. 2016-02-11 17:47 GMT-03:00 Manos PETRIDIS mailto:egpetri...@gmail.com> >: Apparently libsoap-lite-perl, libcrypt-gcrypt-perl and libconvert-basen-perl should be/remain mandatory in 3.22, as they are required by a non-optional module, even if the functionality it provides is not used. 2016-02-11 5:06 GMT+02:00 Mark Tompsett mailto:mtomp...@hotmail.com> >: Greetings, It seems that “$debug && warn” is a popular style used in C4/Member already. I don’t think a system preference is needed. Just a $debug prepend, perhaps? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15795 Sign it off, kill it, suggest a counter-patch, whatever. I do think this addresses the issue. GPML, Mark Tompsett From: David Cook <mailto:dc...@prosentient.com.au> Sent: Wednesday, February 10, 2016 6:40 PM To: 'Philippe Blouin' <mailto:philippe.blo...@inlibro.com> Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] NorwegianPatronDB I think you’re right, Philippe. I’ve noticed the same thing. In fact, the “Unable to load Koha::NorwegianPatronDB” was added after the fact to stop the absence of those libraries causing Koha to die. I don’t necessarily see the point of having that warning there though, as most Koha users probably aren’t going to use the NorwegianPatronDB. Maybe that could have a system preference… so the warns (or the dying) only happens when the system preference is set? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Philippe Blouin Sent: Thursday, 11 February 2016 8:47 AM To: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: [Koha-devel] NorwegianPatronDB Hi! I'm working on 3.22.02 and my logs are FILLED with the following warnings: Members.pm: Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/acqui/booksellers.pl admin-home.pl <http://admin-home.pl> : Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/admin/preferences.pl I look at the code, and beside wondering why that custom feature is so profoundly imbrica
Re: [Koha-devel] NorwegianPatronDB
Hi Martin, Thanks for that info! I have a pause account already, so maybe I should look at tracking down one of those people… I probably won’t have time to work on this for a while, but a long-term fix might be to take over maintenance of that module… I suppose I’m not a bad option as I find encryption interesting and who doesn’t want to maintain a CPAN module? :p David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Renvoize, Martin [mailto:martin.renvo...@ptfs-europe.com] Sent: Monday, 22 February 2016 7:22 PM To: David Cook Subject: Re: [Koha-devel] NorwegianPatronDB One can request to take over maintenence of abandoned cpan modules. You need a pause account obviously to start with, then need to find someone to add your commit bit to the repository for the abandoned module. There are a few such people around in the various perl irc channels. On 14 Feb 2016 10:21 pm, "David Cook" mailto:dc...@prosentient.com.au> > wrote: FYI, if you’re using the Crypt::GCrypt module from CPAN (ie you’re not using a Debian-based system with libcrypt-gcrypt-perl), Koha is probably going to be unable to load Koha::NorwegianPatronDB. The CPAN module has issues which the Debian team have patched, and the CPAN author appears to have zero interest in patching the CPAN version (or talking about it at all). I wonder what CPAN’s policy is on abandoned modules… My point is that if you’re not using the Debian package, you’re that Crypt::GCrypt dependency appears to always fail now. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Tomas Cohen Arazi Sent: Saturday, 13 February 2016 2:52 AM To: Manos PETRIDIS mailto:egpetri...@gmail.com> > Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] NorwegianPatronDB I think we should ship with all the dependencies. We cannot make people's Koha break if they enable some feature. 2016-02-11 17:47 GMT-03:00 Manos PETRIDIS mailto:egpetri...@gmail.com> >: Apparently libsoap-lite-perl, libcrypt-gcrypt-perl and libconvert-basen-perl should be/remain mandatory in 3.22, as they are required by a non-optional module, even if the functionality it provides is not used. 2016-02-11 5:06 GMT+02:00 Mark Tompsett mailto:mtomp...@hotmail.com> >: Greetings, It seems that “$debug && warn” is a popular style used in C4/Member already. I don’t think a system preference is needed. Just a $debug prepend, perhaps? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15795 Sign it off, kill it, suggest a counter-patch, whatever. I do think this addresses the issue. GPML, Mark Tompsett From: David Cook <mailto:dc...@prosentient.com.au> Sent: Wednesday, February 10, 2016 6:40 PM To: 'Philippe Blouin' <mailto:philippe.blo...@inlibro.com> Cc: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] NorwegianPatronDB I think you’re right, Philippe. I’ve noticed the same thing. In fact, the “Unable to load Koha::NorwegianPatronDB” was added after the fact to stop the absence of those libraries causing Koha to die. I don’t necessarily see the point of having that warning there though, as most Koha users probably aren’t going to use the NorwegianPatronDB. Maybe that could have a system preference… so the warns (or the dying) only happens when the system preference is set? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Philippe Blouin Sent: Thursday, 11 February 2016 8:47 AM To: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: [Koha-devel] NorwegianPatronDB Hi! I'm working on 3.22.02 and my logs are FILLED with the following warnings: Members.pm: Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/acqui/booksellers.pl admin-home.pl <http://admin-home.pl> : Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/admin/preferences.pl I look at the code, and beside wondering why that custom feature is so profoundly imbricated into master Koha, I was wondering what is not working. So I hacked the code to add verbose => 1 on the
Re: [Koha-devel] Fwd: Streamlining frontend development in Koha
Indeed it is, thank you. Missed that on my first look at the code.
2014-11-25 1:30 GMT-07:00 Kallinen Pasi :
>
> Reordering the substitutions is possible, using the standard po-file
> "c-format" style:
>
> _("You have checked out %1$s books, %2$s of which are on hold").format(X, Y);
>
>
>
> --
> Ystävällisin terveisin
>
> Pasi Kallinen
> ICT-asiantuntija
>
> p. 050-408 6958
> pasi.kalli...@pttk.fi
>
>
> Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi
>
> ____
> From: koha-devel-boun...@lists.koha-community.org
> [koha-devel-boun...@lists.koha-community.org] on behalf of Marc Véron
> [ve...@veron.ch]
> Sent: Tuesday, November 25, 2014 10:09
> To: koha-devel@lists.koha-community.org
> Subject: Re: [Koha-devel] Fwd: Streamlining frontend development in Koha
>
> It would be great to have the possibility to reorder substitutions like
> proposed:
>
> _$("You have checked out $1 books, $2 of which are on hold", X, Y)
>
> Marc
>
>
> Am 24.11.2014 19:51, schrieb Jesse:
>> Okay, thanks. That does seem to solve part of the problem. I notice
>> that the code doesn't allow translators to reorder substitutions; is
>> that not a major issue?
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
> _______
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
--
Jesse Weaver
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Z39.50 marc21 to unimarc
Hi Andrea, to do this Koha would need to transform UNIMARC to MARC21, which is not trivial. There has been some work in the past on implementing a feature like this, but there is nothing available yet. Hope this helps, Katrin > -Original Message- > From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- > boun...@lists.koha-community.org] On Behalf Of Andrea Furin > Sent: Tuesday, March 04, 2014 10:01 AM > To: Koha-devel@lists.koha-community.org; Koha > Subject: [Koha-devel] Z39.50 marc21 to unimarc > > Hi. > I need to import Z39.50 marc21 results in a unimarc database: is it > possible? > Tia > > andrea f. > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ bugs : http://bugs.koha-community.org/ > _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] dns hea.koha-community.org
Le Tuesday 21 Feb 2017 à 14:35:06 (+1300), Chris Cormack a écrit : > Done Thanks :) > > Chris > > On 21/02/17 05:03, Laurent Ducos wrote: > > Hello. > > I just move hea to another server. > > Someone can modify the dns entry of hea.koha-community.org to > > hea.koha-community.org.716INA163.172.17.20 > > Thanks. > > Laurent Ducos > > Administrateur Systèmes et Réseaux > > > > > > > > > > _______ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Laurent Ducos Administrateur Systèmes et Réseaux à BibLibre +3397477071 ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] items.itype FK constraint?
Hi Sophie, I think on database level we need to allow NULL, because of the item-level_itype 'record level' setting. I understand that itemtypes are not set on item level at all in that case? Katrin On 30.07.19 16:32, Sophie Meynieux wrote: Hello, But itype must not be null if syspref item-level_itype is on, isn't it ? S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 29/07/2019 à 20:17, Katrin Fischer a écrit : +1 With a on delete set null? On 29.07.19 19:39, Tomas Cohen Arazi wrote: Why shouldn't we add it :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] items.itype FK constraint?
There is the system that copies itemtype from biblio level if items.itype is null. I think we should remove this system before adding a FK. Best regards, Le 30/07/2019 à 16:32, Sophie Meynieux a écrit : Hello, But itype must not be null if syspref item-level_itype is on, isn't it ? S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 29/07/2019 à 20:17, Katrin Fischer a écrit : +1 With a on delete set null? On 29.07.19 19:39, Tomas Cohen Arazi wrote: Why shouldn't we add it :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Fridolin SOMERS BibLibre, France - software and system maintainer ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Carrousel display issue on sandbox
Hi, sorry, I should have been more clear: Can you post the link to the repository? Katrin On 11.09.23 21:22, Shi Yao Wang wrote: version 4.1.4 On 2023-09-11 15:13, Katrin Fischer wrote: Hi Shi Yao, as there are multiple versions of the carousel plugin around, which one did you use/install? Hope this helps, Katrin On 11.09.23 21:10, Shi Yao Wang wrote: Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/ ___ Koha-devel mailing list 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/
Re: [Koha-devel] 0000-00-00 is expired?
Great news then :) Sophie and Bob, could you determine what means this value? Would it make sense to update it with -12-31 and consider it as "will never expired"? On Wed, 14 Feb 2018 at 12:13 Tomas Cohen Arazi wrote: > In all my 65 instances, there's not '-00-00'. This is probably a data > migration issue. > > El mié., 14 feb. 2018 a las 11:05, Sophie Meynieux (< > sophie.meyni...@biblibre.com>) escribió: > >> Hello, >> >> For all our customers that are hosted on our servers, only one has one >> patron with dateexpiry = "-00-00" >> >> Regards >> >> S. Meynieux >> >> -- >> Responsable support >> BibLibre+ 33 (0)4 91 81 35 08 >> <+33%204%2091%2081%2035%2008>http://www.biblibre.com >> >> Le 14/02/2018 à 12:12, Katrin Fischer a écrit : >> >> I've also checked our oldest 5 - didn't find any patrons with dateexpiry >> -00-00. >> >> *Gesendet:* Mittwoch, 14. Februar 2018 um 08:18 Uhr >> *Von:* "Magnus Enger" >> *An:* koha-devel@lists.koha-community.org >> *Betreff:* Re: [Koha-devel] -00-00 is expired? >> Hiya! >> >> On 13 February 2018 at 20:06, Jonathan Druart >> >> wrote: >> > It would be useful to know the return of >> > SELECT COUNT(*) FROM borrowers where dateexpiry="-00-00" >> > on old installations. >> >> I just checked my 5 oldest instances (upgraded regularly since >> 2009/2010) and none of them had any users meeting this criterium. >> >> Best regards, >> Magnus >> Libriotech >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> _______ >> Koha-devel mailing >> listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Errors generating fr-FR templates in 3.18.5
Hi Marc: I'm sorry but I don't understand. There were two %s missing in fr-FR-i-staff-t-prog-v-3006000.po... I don't think they were superfluous? I still don't understand where the .po files come from. Does someone generate them from the English templates? When? How does one submit fixes? Through Pootle? Through Git? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -Original Message- > From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- > boun...@lists.koha-community.org] On Behalf Of Marc Véron > Sent: Thursday, 26 March 2015 6:14 PM > To: koha-transl...@lists.koha-community.org > Cc: Koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] Errors generating fr-FR templates in 3.18.5 > > Hi David, > > There were printf() errors on Pootle for French 3.18: : > > http://translate.koha-community.org/fr/318/ > Click "Expand details" > Printf() 3 Errors > > I fixed them on Pootle (2 %s were superfluous, 1 had a wrong capitalization) > > Marc > ___________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] BibLibre new staff & intern
Welcome!
On 12.10.2017 16:14, Tomas Cohen Arazi wrote:
Awesome news, Paul.
Welcome Simon and Victor!
El jue., 12 oct. 2017 a las 11:10, Jonathan Druart
(<mailto:jonathan.dru...@bugs.koha-community.org>>) escribió:
Awesome news indeed :) Welcome Simon and Victor!
First thing to do is to follow the koha howto!
https://wiki.koha-community.org/wiki/Koha_howto
Cheers,
Jonathan
On Thu, 12 Oct 2017 at 07:31 Paul Poulain
mailto:paul.poul...@biblibre.com>> wrote:
Hello koha-devel,
I'm happy to introduce Victor Grousset, that join the
support/maintenance team at BibLibre. He will probably submit
or signoff
his first patches in the next weeks.
I'm also happy to introduce Simon Pouchol, an intern that will
be with
us for 3 months. He will work on Koha community, more focused
on design
/ UI. We're already in touch with Owen ;-)
In the next months, we really want to re-invest in Koha
community time.
We will try to dedicate someone 2 days a week to community
work (QA,
sign-off, submit patches). Wait until Victor has ended his
learning
time, and our investment should be visible for 18.05 !
--
Paul Poulain, Associé-gérant / co-owner
BibLibre, Services en logiciels libres pour les bibliothèques
BibLibre, Open Source software and services for libraries
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Add rule for experimental features in coding guidelines
I'm perfectly happy with that : ) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -Original Message- > From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- > boun...@lists.koha-community.org] On Behalf Of Jonathan Druart > Sent: Wednesday, 30 September 2015 6:38 PM > To: koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] Add rule for experimental features in coding > guidelines > > Maybe it would be better to just specify that the code has to pass the koha- > qa script. > The experimental warnings is raised by perl -w and caught by this script. > > 2015-09-29 3:26 GMT+01:00 David Cook : > > Hi all: > > > > > > > > I just noticed that we don’t actually have a rule against using > > experimental features (e.g. smartmatch ~~, given/when) in the coding > > guidelines. We impose this rule during the testing/QA process, but > > it’s not actually documented. > > > > > > > > What do we need to do to add a rule? Bring this up at a meeting? > > > > > > > > http://wiki.koha-community.org/wiki/Coding_Guidelines > > > > > > > > > > > > David Cook > > > > Systems Librarian > > > > Prosentient Systems > > > > 72/330 Wattle St, Ultimo, NSW 2007 > > > > > > > > > > ___ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ git : > > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue?
Cheers, Jonathan. I had totally forgotten about that. Yikes. Good call, Chris. While I think many mail servers these days use TLS to secure the email between the mail servers, an unscrupulous administrator could still certainly take advantage of people on either end. The best idea probably is to just not use AutoEmailOpacUser, as Jonathan seems to suggest. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org] Sent: Tuesday, 19 June 2018 12:07 AM To: Christopher Nighswonger Cc: David Cook ; Koha Devel Subject: Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue? It has been reported (by David) on our bug tracker already (20796, security area, which does no longer make sense at it is public now...) For information this notice contains the password in clear for... 10 years now (bug 2149) and the behavior is turned off by default (AutoEmailOpacUser). On Mon, 18 Jun 2018 at 10:11 Christopher Nighswonger mailto:chris.nighswon...@gmail.com> > wrote: Considering that email is plaintext (AKA "postcard") mail, I'm surprised we would send a user's password in an email in any case. On Mon, Jun 18, 2018 at 4:14 AM, David Cook mailto:dc...@prosentient.com.au> > wrote: Considering that the borrower’s password is typically in the ACCTDETAILS email, I think using the message_queue for ACCTDETAILS would be a bad idea and would probably violate the GDPR in Europe. Just imagine looking through your database and seeing all those plain text passwords, especially for people who re-use the same password for everything. I think it would be a security and privacy nightmare. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Sophie Meynieux Sent: Friday, 15 June 2018 9:33 PM To: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue? Maybe because for this message you're expecting it is sent immediately while message_queue table could be processed more occasionally ? Best regards S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 15/06/2018 à 12:40, Indranil Das Gupta a écrit : Hi all, I was wondering why we do not push the ACCTDETAILS email via the message queue. Is it just one of those cases of "as things have always been done" OR there is a reason that I'm missing out? cheers indranil. Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 Blog: http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net <http://irc.freenode.net> Twitter : indradg _______ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
Hello all,
Have we considered using git's hooks for tidifying the code before
checking it in, or even on the server, this would ensure that whoever
does the checkin, it will be tidified.
Also, if we consider going with a global tidifying, a good timing could
be when creating a new branch.
My 2 cents !
Eric Bégin
www.inLibro.com
On 2012-03-09 04:16, Marcel de Rooy wrote:
+1 for a gradual perl tidy too
Even then, still don't like the idea of blocking a patch for tabs and
spaces ..
*Van:* koha-devel-boun...@lists.koha-community.org
[koha-devel-boun...@lists.koha-community.org] namens Ian Walls
[koha.sek...@gmail.com]
*Verzonden:* donderdag 8 maart 2012 20:21
*To:* Chris Cormack
*Cc:* Fischer, Katrin; koha-devel@lists.koha-community.org
*Onderwerp:* Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
Chris,
Right, with the colossal commit option, one could have to
1. Know the commit id of the change
2. git blame something
3. if that id comes up, then git checkout -b temporary
<>^
4. git blame again
The more history we pile on top of that, the longer it'll take git to
update the index, and then restore back to master when you're done.
If you're tracing out lots of blames, then this can be a serious crimp
in workflow.
-Ian
On Thu, Mar 8, 2012 at 13:50, Chris Cormack <mailto:chr...@catalyst.net.nz>> wrote:
* Ian Walls (koha.sek...@gmail.com <mailto:koha.sek...@gmail.com>)
wrote:
>Doing a large updating commit does not cost us any history.A
It just
>counts as an "update" to the code, even though none of the
logic has
>changed.A A This change would alter SLOC counts and such,
messing with
>our statistics, since we only want to measure intellectually
significant
>contributions (tidying someone else's work doesn't make it
yours).A There
>is no way for Git to know if a change to a line of text is a
logical
>change or just a formatting change (aside from whitespace),
because Git
>doesn't understand Perl.A There isn't too much we can do
about this.
It's not so much statistics I care about, although I do. But also that
it makes it hard to to do a git blame to find which commit actually
changed the line. Since now every line is changed by the same commit.
Chris
>
>So, best to keep cleaning up incrementally, I think.A As we
move from C4
>to Koha, that'll be an opportunity to clean up all the modules
>
>-Ian
>
>2012/3/8 Jared Camins-Esakov mailto:jcam...@cpbibliography.com>>
>
> +1 to a gradual perltidy
>
> 2012/3/8 Fischer, Katrin mailto:katrin.fisc...@bsz-bw.de>>
>
>I agree with Chris C. and Chris N. - I think what we
would win does
> not outweigh the loss of history.
>
> Katrin
>
>-UrsprA 1/4ngliche Nachricht-
>Von: koha-devel-boun...@lists.koha-community.org
<mailto:koha-devel-boun...@lists.koha-community.org> im Auftrag
von Chris
> Nighswonger
>Gesendet: Do 08.03.2012 19:26
>An: Chris Cormack
>Cc: koha-devel@lists.koha-community.org
<mailto:koha-devel@lists.koha-community.org>
>Betreff: Re: [Koha-devel] Koha 3.8 release schedule &
perltidy process
>
>2012/3/8 Chris Cormack mailto:ch...@bigballofwax.co.nz>>
>
> > My counter proposal is tidy as you go. Fix code as you touch it.
> >
> > With vim (and other editors) you can easily tidy a block,
doing that
>as
> > code is changed would be my preference.
> >
>
>I'd prefer a "pay-as-you-go" approach as well. We could
simply require
>all
>work to be tidied before submitting.
>
> Slow? Yes, but not nearly as messy and preserves the history.
>
>Kind Regards,
>Chris
>
>___
>Koha-devel mailing list
> Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>website : http://www.koha-community.org/
>git : http://git.koha-community.org/
>bugs : http://bugs.koha-community.org/
>
> --
> Jared Camins-Esakov
> Bibliographer, C & P Bibliography Services, LLC
> (pho
Re: [Koha-devel] Accidental ban from bugzilla
The bot only changes bugs that do not apply? If it would change all bugs it visits just for some timestamp or so, I would not be in favor. Marcel -Oorspronkelijk bericht- Van: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] Namens Chris Cormack Verzonden: zondag 6 maart 2016 23:02 Aan: Katrin Fischer CC: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Accidental ban from bugzilla Here's an example of what the bot is doing https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12747#c35 It set this to patch does not apply, when I test by hand, this is indeed the case. If people like it, I can run the bot each day Chris ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plack only
On 07/02/18 12:20, David Cook wrote: > This seems pretty Debian-centric, so doesn’t really affect me I suppose. > > > > I am curious how Plack works for multi-library Debian installs though. I > would be worried about data leaking between libraries. > > This isn't an issue any more than it would be under cgi, different threads are run for each instance Chris > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:*koha-devel-boun...@lists.koha-community.org > [mailto:koha-devel-boun...@lists.koha-community.org] *On Behalf Of > *Tomas Cohen Arazi > *Sent:* Wednesday, 7 February 2018 5:51 AM > *To:* koha-devel@lists.koha-community.org > *Subject:* Re: [Koha-devel] Plack only > > > > For running in Plack-mode, people needs to: > > > > sudo koha-plack --enable > > sudo koha-plack --start > > sudo systemctl restart apache2 > > > > after creating the . > > > > What I meant is that we should have people avoid the need for those > commands. And people with specific needs that require non-Plack setups > can do it. > > > > I started thinking of this in the context of bug 20134 [1] BUT also in > the context of bugs 18315 [2] and 7174 [3]. > > > > Both of the latter bugs propose interesting ways of refactoring > authentication, and I'm sure abandoning CGI-mode could help simplify the > process. > > > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20134 > > [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 > > [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 > > > > El mar., 6 feb. 2018 a las 11:00, Julian Maurice > (mailto:julian.maur...@biblibre.com>>) > escribió: > > What does that mean to "make Plack the default" exactly ? > > Le 06/02/2018 à 14:31, Tomas Cohen Arazi a écrit : > > I would like to know if you think there's any reason to keep the CGI > > mode as default in Koha deployments. I think we should make Plack the > > default. There are some issues, tough. > > > > But if we set that goal, we could focus on fixing them. > > > > What do you think? > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io <http://theke.io/>) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > > > > > > ___ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice <mailto:julian.maur...@biblibre.com>> > BibLibre > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io <http://theke.io/>) > ✆+54 9351 3513384 > GPG: B2F3C15F > > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] What is biblioitemnumber for?
+1 S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 17/11/2018 à 21:24, Tomas Cohen Arazi a écrit : Or merge biblio and biblioitems ;-) El sáb., 17 nov. 2018 a las 16:41, Barton Chittenden (mailto:bar...@bywatersolutions.com>>) escribió: Just out of curiosity, why does biblioitemnumber exist? There should be a one-to-one relationship between biblio records and biblioitem records ... so why not use biblionumber as the primary key for biblioitems? --Barton ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] KohaDevBox question...
Greetings, prove t/SMS.t C4/SMS.pm line 98 GPML, Mark Tompsett From: Jonathan Druart<mailto:jonathan.dru...@bugs.koha-community.org> Sent: Tuesday, January 03, 2017 2:37 AM To: Koha-devel<mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] KohaDevBox question... Hi Mark, on which test is the warning raised? On Tue, 3 Jan 2017 at 01:52 Mark Tompsett mailto:mtomp...@hotmail.com>> wrote: Greetings, I was running a ‘prove t’ on the kohadevbox which I just vagrant up jessie’d from scratch the other night. I encountered a message about an uninitialized variable which led me to bug 13029. This added a configuration item to the koha-conf.xml file. Will this auto-correct with a vagrant destroy and vagrant up in the near future (before 17.05’s release)? I can add the item manually myself, but I’d hate to have to remember this the next time I might destroy and up. GPML, Mark Tompsett ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-bugs] [Bug 5687] Add preference for display of AuthorisedValueImages at staff search results
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5687 --- Comment #27 from MJ Ray (software.coop) 2011-04-11 08:32:00 UTC --- This bug is mentioned in: Bug 5687: Add pref StaffAuthorisedValueImages for staff search results http://lists.koha-community.org/pipermail/koha-patches/2011-March/014018.html Bug 5687: Add pref StaffAuthorisedValueImages for staff search results (install) http://lists.koha-community.org/pipermail/koha-patches/2011-March/014019.html Bug 5687: Add prefStaffAuthorisedValueImages for staff search results (install) http://lists.koha-community.org/pipermail/koha-patches/2011-March/014113.html Bug 5687: Add pref StaffAuthorisedValueImages for staff search results (install) http://lists.koha-community.org/pipermail/koha-patches/2011-March/014255.html Bug 5687: Add prefStaffAuthorisedValueImages for staff search results http://lists.koha-community.org/pipermail/koha-patches/2011-March/014332.html Bug 5687: Add prefStaffAuthorisedValueImages for staff search results (install) http://lists.koha-community.org/pipermail/koha-patches/2011-March/014333.html -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA Contact for the bug. ___ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-bugs] [Bug 5940] Update Help Files for 3.4
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5940 Nicole C. Engard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #15 from MJ Ray (software.coop) 2011-04-03 23:19:32 UTC --- This bug is mentioned in: Bug 5940: Update Patron Help Files http://lists.koha-community.org/pipermail/koha-patches/2011-March/014216.html Bug 5940: Catalog and Cataloging Help Filesfor 3.4 http://lists.koha-community.org/pipermail/koha-patches/2011-March/014232.html Bug 5940: Acq and Suggestion Help Files for3.4 http://lists.koha-community.org/pipermail/koha-patches/2011-March/014319.html Bug 5940: Admin Help Files for 3.4 http://lists.koha-community.org/pipermail/koha-patches/2011-March/014322.html Bug 5940: Admin Help Files for 3.4 http://lists.koha-community.org/pipermail/koha-patches/2011-March/014329.html Bug 5940: Offline Circ & Patron Card Help Files for 3.4 http://lists.koha-community.org/pipermail/koha-patches/2011-March/014371.html -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA Contact for the bug. ___ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Development/ QA protocol question
+1 for using 'Patch complexity' 'Patch complexity' gives a hint for singing off as well. While signing off I fill it in most of the cases. Sometimes I forget it, though... Marc Am 30.03.2017 um 08:34 schrieb Marcel de Rooy: I always fill patch complexity. Also for patches that I qa. And not filling that field (and/or other fields) gives it a lower priority. And yes, the number of lines is not the same as complexity. -Oorspronkelijk bericht- Van: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] Namens Cab Vinton Verzonden: woensdag 29 maart 2017 23:01 Aan: Jonathan Druart CC: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Development/ QA protocol question On Wed, Mar 29, 2017 at 4:58 PM, Jonathan Druart wrote: There is a "Patch complexity" field, but I personally do not use it (I should yes). I've see. Don't think anyone else uses it either :-) Would be cool if it auto-populated with the number of new/ different lines in the patch ... Pretty rough & ready measure of complexity. ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] [Koha] Koha packages are available 🎁
Can verify that I’ve received December’s 22nd message informing us on the release of version 21.11.01. Στις Τετ, 29 Δεκ 2021 στις 5:07 μμ ο χρήστης Kyle Hall < kyle.m.h...@gmail.com> έγραψε: > I sent out an email for 21.11, did it get blocked? > > Kyle > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS < > fridolin.som...@biblibre.com> wrote: > >> Hi, >> >> There has been a mail for 20.11.13 release : >> https://koha-community.org/koha-20-11-13-released/ >> >> For other versions I don't see emails. >> Here are the details : >> >> 20.11.01 release : >> https://koha-community.org/koha-21-11-01-released/ >> >> 21.05.08 release : >> https://koha-community.org/koha-21-05-08-released/ >> >> Best regards, >> >> Le 25/12/2021 à 16:02, Mason James a écrit : >> > kia ora community, >> > the latest Koha packages are available >> > >> > cheers, Mason >> > ___ >> > Koha-devel mailing list >> > 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/ >> >> -- >> Fridolin SOMERS >> Software and system maintainer 🦄 >> BibLibre, France >> _______ >> Koha-devel mailing list >> 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/ >> > ___ > Koha-devel mailing list > 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/ > ___ Koha-devel mailing list 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/
Re: [Koha-devel] plugins on KohaDevboxes
It is the beloved Carrousel :
https://inlibro.com/instructions-carrousel/
Le 31/08/2023 à 12:28, Tomas Cohen Arazi a écrit :
What plugin is that?
El jue, 31 ago 2023 a las 17:16, Philippe Blouin
(mailto:philippe.blo...@inlibro.com>>)
escribió:
__
Hi!
Any suggestion onto why our plugin doesn't seem to work on
(bywater's) Devboxes while being perfectly fine in 22,23 or master
local installs ?
The UI of the config is all damaged, like the dropbox not being
clickable. Below first is the devbox version, versus our
installations right after.
Any hint would be greatly appreciated.
Thanks
--
Philippe Blouin,
Directeur de la technologie
Tél. : (833) 465-4276, poste 230
philippe.blo...@inlibro.com <mailto:philippe.blo...@inlibro.com>
inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
<mailto:Koha-devel@lists.koha-community.org>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : https://www.koha-community.org/
<https://www.koha-community.org/>
git : https://git.koha-community.org/ <https://git.koha-community.org/>
bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <https://theke.io>)
✆ +54 9351 3513384
GPG: B2F3C15F
_______
Koha-devel mailing list
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/
--
Fridolin SOMERS
Software and system maintainer 🦄
BibLibre, France
_______
Koha-devel mailing list
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/
Re: [Koha-devel] Koha instances for different domains
Hi, You may implement V-Host on you Ubuntu box to handle the different domain. Best Regards, - Bendon Murgor Sytems Engineer/IT Systems Auditor +254-720-529868 Sent from my BlackBerry® -Original Message- From: Quoc Uy Sender: koha-devel-boun...@lists.koha-community.org Date: Tue, 5 Nov 2013 05:48:19 To: koha-devel@lists.koha-community.org Reply-To: Quoc Uy Subject: [Koha-devel] Koha instances for different domains ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha] [Koha-devel] Koha packages are available 🎁
Oo my bad, it was in my "Katipo" folder.
I see it in archives :
https://lists.katipo.co.nz/pipermail/koha/2021-December/057162.html
All is good.
Le 29/12/2021 à 21:41, Fridolin SOMERS a écrit :
I'm looking at archives :
https://lists.koha-community.org/pipermail/koha-devel/2021-December/date.html
I dont see it.
Can anyone confirm ?
Le 29/12/2021 à 05:07, Kyle Hall a écrit :
I sent out an email for 21.11, did it get blocked?
Kyle
---
http://www.kylehall.info <http://www.kylehall.info>
ByWater Solutions ( http://bywatersolutions.com
<http://bywatersolutions.com> )
Meadville Public Library ( http://www.meadvillelibrary.org
<http://www.meadvillelibrary.org> )
Crawford County Federated Library System ( http://www.ccfls.org
<http://www.ccfls.org> )
On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS
mailto:fridolin.som...@biblibre.com>>
wrote:
Hi,
There has been a mail for 20.11.13 release :
https://koha-community.org/koha-20-11-13-released/
<https://koha-community.org/koha-20-11-13-released/>
For other versions I don't see emails.
Here are the details :
20.11.01 release :
https://koha-community.org/koha-21-11-01-released/
<https://koha-community.org/koha-21-11-01-released/>
21.05.08 release :
https://koha-community.org/koha-21-05-08-released/
<https://koha-community.org/koha-21-05-08-released/>
Best regards,
Le 25/12/2021 à 16:02, Mason James a écrit :
> kia ora community,
> the latest Koha packages are available
>
> cheers, Mason
> _______
> Koha-devel mailing list
> koha-de...@lists.koha-community.org
<mailto:koha-de...@lists.koha-community.org>
>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
> website : https://www.koha-community.org/
<https://www.koha-community.org/>
> git : https://git.koha-community.org/
<https://git.koha-community.org/>
> bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
-- Fridolin SOMERS mailto:fridolin.som...@biblibre.com>>
Software and system maintainer 🦄
BibLibre, France
___________
Koha-devel mailing list
koha-de...@lists.koha-community.org
<mailto:koha-de...@lists.koha-community.org>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
<https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
website : https://www.koha-community.org/
<https://www.koha-community.org/>
git : https://git.koha-community.org/
<https://git.koha-community.org/>
bugs : https://bugs.koha-community.org/
<https://bugs.koha-community.org/>
--
Fridolin SOMERS
Software and system maintainer 🦄
BibLibre, France
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha-devel] about using XSLT for display of holdings (952)
I imagine moving our current items display into the XSLT file would probably result in XSLT code that is quite hard to read and adjust. There are quite a lot of preferences that we would need to take into account. I think having the option to configure the display without programming would be better. If this is only to ease customization, maybe adding the column configuration tool or something similar the the OPAC could be another option. Katrin Am 08.02.2016 um 10:57 schrieb Marcel de Rooy: > Have a look at C4/XSLT.pm > XSLTParse4Display calls buildKohaItemsNamespace. This routine adds several > item fields. > Resulting data goes through transform call of XSLT handler. > > -Oorspronkelijk bericht- > Van: koha-devel-boun...@lists.koha-community.org > [mailto:koha-devel-boun...@lists.koha-community.org] Namens Gaetan Boisson > Verzonden: maandag 8 februari 2016 10:28 > Aan: koha-devel@lists.koha-community.org > Onderwerp: Re: [Koha-devel] about using XSLT for display of holdings (952) > > I would be in favor of the detail display bein made with XSLT for items. > That would of course be much more flexible, and would allow us to have custom > fields easily (i.e. to display whatever ends up in more_subfields_xml as we > please). > > I think there are historical reasons (the template based display needs to > work and took care of this with the table), and the fact that items are not > stored in the marcxml anylonger might be a reason too, althought maybe > something puts them back in the marcxml when doing the xslt processing. (And > you get them in the marcxml when saving the record, even though the item > level fields are not in biblioitems.marcxml.) > > Le 08/02/2016 02:10, David Cook a écrit : >> Hmm, it's a good question I think. >> >> I imagine part of it might be a speed thing, or coincidence? >> >> I know Fridolyn was planning on trimming the number of items added as >> 952s to the Zebra records, so in that case the database would have the >> true reflection of holdings while the MARCXML would only have a snapshot. >> >> Overall, not sure. >> >> David Cook >> Systems Librarian >> Prosentient Systems >> 72/330 Wattle St, Ultimo, NSW 2007 >> >> >>> -Original Message- >>> From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- >>> boun...@lists.koha-community.org] On Behalf Of Indranil Das Gupta >>> Sent: Sunday, 7 February 2016 8:43 AM >>> To: koha-devel@lists.koha-community.org >>> Subject: [Koha-devel] about using XSLT for display of holdings (952) >>> >>> Hi, >>> >>> At the risk of asking something very stupid, I was wondering why we >> utilize >>> XSLT only for the biblio record and not for the holdings data in say >>> opac- details.pl >>> >>> thanks in advance >>> >>> -- >>> Indranil Das Gupta >>> >>> Phone : +91-98300-20971 >>> Blog: http://indradg.randomink.org/blog >>> IRC : indradg on irc://irc.freenode.net >>> Twitter : indradg >>> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- >>> Please exchange editable Office documents only in ODF Format. No >>> other format is acceptable. Support Open Standards. >>> >>> For a free editor supporting ODF, please visit LibreOffice - >>> http://www.documentfoundation.org >>> _______ >>> Koha-devel mailing list >>> Koha-devel@lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ git : http://git.koha- >>> community.org/ bugs : http://bugs.koha-community.org/ >> >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ git : >> http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > -- > Gaetan Boisson > Chef de projet bibliothécaire > BibLibre > 06 52 42 51 29 > 108 avenue Breteuil 13006 Marseille > gaetan.bois...@biblibre.com > > _______ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue?
I think that would probably be the best way of going about it, but I’m sure there are a lot of libraries that wouldn’t be happy about it. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Liz Rea Sent: Tuesday, 19 June 2018 12:26 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue? I feel like instead of sending people a password, we should send them to the "forgot password reset page" with a couple of slight changes for new account holders, so they can set their own passwords. Seems better than sending the password in the clear in an email. Cheers, Liz On 19/06/18 12:21, David Cook wrote: Cheers, Jonathan. I had totally forgotten about that. Yikes. Good call, Chris. While I think many mail servers these days use TLS to secure the email between the mail servers, an unscrupulous administrator could still certainly take advantage of people on either end. The best idea probably is to just not use AutoEmailOpacUser, as Jonathan seems to suggest. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org] Sent: Tuesday, 19 June 2018 12:07 AM To: Christopher Nighswonger <mailto:chris.nighswon...@gmail.com> Cc: David Cook <mailto:dc...@prosentient.com.au> ; Koha Devel <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue? It has been reported (by David) on our bug tracker already (20796, security area, which does no longer make sense at it is public now...) For information this notice contains the password in clear for... 10 years now (bug 2149) and the behavior is turned off by default (AutoEmailOpacUser). On Mon, 18 Jun 2018 at 10:11 Christopher Nighswonger mailto:chris.nighswon...@gmail.com> <mailto:chris.nighswon...@gmail.com> <mailto:chris.nighswon...@gmail.com> > wrote: Considering that email is plaintext (AKA "postcard") mail, I'm surprised we would send a user's password in an email in any case. On Mon, Jun 18, 2018 at 4:14 AM, David Cook mailto:dc...@prosentient.com.au> <mailto:dc...@prosentient.com.au> <mailto:dc...@prosentient.com.au> > wrote: Considering that the borrower’s password is typically in the ACCTDETAILS email, I think using the message_queue for ACCTDETAILS would be a bad idea and would probably violate the GDPR in Europe. Just imagine looking through your database and seeing all those plain text passwords, especially for people who re-use the same password for everything. I think it would be a security and privacy nightmare. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> <mailto:koha-devel-boun...@lists.koha-community.org> <mailto:koha-devel-boun...@lists.koha-community.org> [mailto:koha-devel-boun...@lists.koha-community.org <mailto:koha-devel-boun...@lists.koha-community.org> <mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Sophie Meynieux Sent: Friday, 15 June 2018 9:33 PM To: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> <mailto:koha-devel@lists.koha-community.org> <mailto:koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Why we do not push the ACCTDETAILS email via message queue? Maybe because for this message you're expecting it is sent immediately while message_queue table could be processed more occasionally ? Best regards S. Meynieux ___________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 04 803 2265 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7 ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plugin hooks on datas and store()
So to have a "post_creation" hook that would be actually called *before*
the item is effectively created, hum... :)
Le ven. 12 mars 2021 à 13:47, Fridolin SOMERS
a écrit :
> Mmmm interesting.
>
> Why not send the $self object to plugin
> and call SUPER::store() after hook ?
>
> Best regards,
>
>
> Le 10/03/2021 à 09:22, Jonathan Druart a écrit :
> > From perlobj pod:
> > "The |SUPER| pseudo-class is resolved from the package where the call is
> > made. It is /not/ resolved based on the object's class."
> >
> > You can still call $item->_result->update.
> >
> > I suggest you open a bug report to add a no_trigger flag to
> > Koha::Object->store (like we did in Koha::Objects).
> >
> > Also spotted, at the end of store:
> > 193 my $result = $self->SUPER::store;
> >
> > 202 $self->get_from_storage->_after_item_action_hooks({ action =>
> > $action });
> > 203
> > 204 return $result;
> >
> > That's wrong!
> >
> > Le mar. 9 mars 2021 à 09:32, Fridolin SOMERS
> > mailto:fridolin.som...@biblibre.com>> a
> > écrit :
> >
> > Yop
> >
> > I've tried with :
> >
> > sub after_item_action {
> > my ( $self, $params ) = @_;
> > warn "AFTER ITEM ACTION";
> >
> > my $item = $params->{item};
> > $item->itemnotes("Edited at " . localtime);
> > }
> >
> > Calling $item->SUPER::store() generates an error :
> >
> > Plugin error (Example Kitchen-Sink Plugin): Can't locate object
> method
> > "store" via package
> "Koha::Plugin::Com::ByWaterSolutions::KitchenSink"
> > at
> >
>
> /mnt/git/koha-plugin-kitchen-sink/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm
> >
> > line 580.
> >
> > Surely only Koha::Item can call SUPER.
> >
> > Adding $self->SUPER::store() at the end of Koha::Item->store() does
> > also
> > not work.
> >
> > Is it because of "get_from_storage" ?
> >
> > $self->get_from_storage->_after_item_action_hooks({ action =>
> > $action });
> >
> > The _after_item_action_hooks method is called not on object $self
> > but on
> > a copy ?
> >
> > Best regards,
> >
> > Le 08/03/2021 à 11:49, Jonathan Druart a écrit :
> > > I wouldn't add other hooks, they are "_after_item_action_hooks"
> for
> > > creation and modification.
> > > "After item creation" should allow you to modify the item, unless
> we
> > > need a "pre store" hook.
> > > I had a look at the code and I didn't find any problems.
> > > Fridolin, what did you try exactly, can you share the code?
> > >
> > > Le lun. 8 mars 2021 à 11:17, Tomas Cohen Arazi
> > mailto:tomasco...@gmail.com>
> > > <mailto:tomasco...@gmail.com <mailto:tomasco...@gmail.com>>> a
> > écrit :
> > >
> > > Maybe you need some other hook. Ones that allows you to make
> > changes
> > > to the object right before it is stored instead of this one,
> that
> > > gets the 'just updated' object.
> > > When I added 'after' hooks for biblios and items actions, the
> > idea
> > > was that they should act as triggers for other actions: in my
> > case,
> > > fill a zebraqueue-ish table my plugin uses.
> > >
> > > El lun, 8 mar 2021 a las 5:11, Fridolin SOMERS
> > > ( > <mailto:fridolin.som...@biblibre.com>
> > > <mailto:fridolin.som...@biblibre.com
> > <mailto:fridolin.som...@biblibre.com>>>) escribió:
> > >
> > > Hi,
> > >
> > > While testing new hook :
> > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>
> > >
> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066
> > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066>>
> > >
> > > I faced a problem :
> > > How can I modify the current patron object ?
> &
Re: [Koha-devel] Plugin KOCT for offline circulation updated
Great news Paul! Thanks! Best regards, Andreas Hedström Mace Systems Librarian Stockholm University Library -Ursprungligt meddelande- Från: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] För Paul Poulain Skickat: den 13 oktober 2017 15:24 Till: k...@lists.katipo.co.nz; koha-devel@lists.koha-community.org Ämne: [Koha-devel] Plugin KOCT for offline circulation updated Hello koha, We have updated the KOCT firefox module to make it compatible with the new versions of Firefox (that changed how modules must be written) Enjoy : https://addons.mozilla.org/en-US/firefox/addon/koct/ -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] SSL problem with lists.koha-community.org
Laurent, Can you look & check please (David, right, we're hosting the mailing lists) Le 01/03/2019 à 04:27, David Cook a écrit : Hi all, It looks like BibLibre might be in charge of lists.koha-community.org? https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel seems to be sending an expired self-signed certificate with BibLibre information. Someone might want to take a look at that. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://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 ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] QA script - New check for spelling
There is no package for codespell on Wheezy. But I would like to keep using the qa script :) I am not sure if we should check spelling in QA and/or spend time on false negatives too.. -Oorspronkelijk bericht- Van: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] Namens Jonathan Druart Verzonden: donderdag 18 juni 2015 16:34 Aan: koha-devel@lists.koha-community.org Onderwerp: [Koha-devel] QA script - New check for spelling Hi devs, QAing bug 14383, I have just added a new check in the QA script to check the spelling in the code comments. Let me know if you find any issues. You will have to install codespell (apt-get install codespell). Cheers, Jonathan ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] RFC: Retiring of the koha-patches mailing list
+1 Van: koha-devel-boun...@lists.koha-community.org namens Tomas Cohen Arazi Verzonden: dinsdag 12 juli 2016 14:45:21 Aan: Owen Leonard; koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] RFC: Retiring of the koha-patches mailing list +1 El mar., 12 jul. 2016 a las 9:34, Owen Leonard (mailto:oleon...@myacpl.org>>) escribi?: > Does anyone have any strong objections to shutting down the mailing list? +1 to shutting down the patches mailing list. I haven't heard any objections yet, so let's move forward on it. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ___ Koha-devel mailing list Koha-devel@lists.koha-community.org<mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io<http://theke.io/>) ? +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] FW: Database
Hi Paul, Could you please check [or sign..] patch 5936.. ? Regards, Marcel Van: koha-devel-boun...@lists.koha-community.org [koha-devel-boun...@lists.koha-community.org] namens Paul Poulain [paul.poul...@biblibre.com] Verzonden: dinsdag 22 maart 2011 10:23 Aan: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Database Le 21/03/2011 13:54, Marcel de Rooy a écrit : > > Hi all, > Hi Marcel, > > I was checking some differences between db revisions and > kohastructure. Came across four fields from aqbooksellers: > > > > Deliverydays > > Followupdays > > Followupscancel > > Specialty > I don't have those fields in my databases (checked on customers database & kohacommunity setup). I don't remember seeing them anywhere, so I think you can drop them -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] FW: Patch format
+1 for removing redundancy ;) -Oorspronkelijk bericht- Van: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] Namens Mason James Verzonden: maandag 1 augustus 2011 02:50 CC: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Patch format i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla an automated bugzilla script could then send that new patch to the patches list this proposed method removes the double-handling of a patch (sending to patches-list and attaching to bugzilla) and would help encourage people to use bugzilla to track their patches, rather than sending the patch to the list, and the patch getting lost a good idea, or not? Mason ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-bugs] [Bug 5880] C4/Koha.pm : adding two functions GetAutorisedValueByCode and GetKohaImageurlFromAuthorisedValues
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5880 --- Comment #12 from MJ Ray (software.coop) 2011-04-07 10:50:43 UTC --- This bug is mentioned in: Bug 5880 : C4/Koha.pm : adding two functionsGetAutorisedValueByCode and GetKohaImageurlFromAuthorisedValues http://lists.koha-community.org/pipermail/koha-patches/2011-March/014075.html Bug 5880 : C4/Koha.pm : addingtwo functions GetAutorisedValueByCode and GetKohaImageurlFromAuthorisedValues http://lists.koha-community.org/pipermail/koha-patches/2011-March/014080.html Follow up for bug 5880: Added unit tests forthe two new subroutines http://lists.koha-community.org/pipermail/koha-patches/2011-March/014106.html Follow up for bug 5880: Improved unit test http://lists.koha-community.org/pipermail/koha-patches/2011-March/014111.html Bug 5880: Correct misleading pod in newsubroutine http://lists.koha-community.org/pipermail/koha-patches/2011-March/014189.html -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA Contact for the bug. ___ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] items.itype FK constraint?
Hello, But itype must not be null if syspref item-level_itype is on, isn't it ? S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 29/07/2019 à 20:17, Katrin Fischer a écrit : +1 With a on delete set null? On 29.07.19 19:39, Tomas Cohen Arazi wrote: Why shouldn't we add it :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] OPAC theme proposal
+1... On 28 Oct 2013 20:26, "Doug Kingston" wrote: > +1 on the strategy. > > > On Mon, Oct 28, 2013 at 11:34 AM, Owen Leonard wrote: > >> +1 from me on the timeline. >> >> > [4] The RM will assist in getting OPAC template patches in the pipeline >> that >> > were written for prog updated to support Bootstrap as well. >> >> I'm happy to help too. >> >> -- Owen >> >> -- >> Web Developer >> Athens County Public Libraries >> http://www.myacpl.org >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Removal of the prog and CCSR themes in 3.18
+1 for removal. Boostrap is great, long lives Boostrap. Le 13/05/2014 08:40, Marc Véron a écrit : +1 for removal Marc --- marc veron ag informatik information internet Baslerstrasse 50 CH - 4123 Allschwil +41 61 483 84 61 www.veron.ch Acrobat / PDF - Lösungen seit 1995 Partner für Internet und Content Management Mitglied Koha Support Schweiz www.koha-support.ch Am 12.05.2014 22:46, schrieb Chris Cormack: +1 from me ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Error when importing file
Hi,
It worked for us but didn't go much detail.
I opened a bug for this.
Maybe it is better to continue there.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33692
Mengü Yazıcıoğlu
Devinim
On 5.05.2023 23:18, Tiago Murakami wrote:
I try, but I had a new error:
[Fri May 05 17:13:40.418662 2023] [cgi:error] [pid 12480] [client
::1:33606] AH01215: Argument "_USE_ORIG_" isn't numeric in numeric eq
(==) at /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl
<http://manage-marc-import.pl> line 93.:
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl
<http://manage-marc-import.pl>, referer:
http://localhost:8080/cgi-bin/koha/tools/manage-marc-import.pl?import_batch_id=1
Thanks in advance
Tiago Murakami
On Fri, May 5, 2023 at 4:49 PM Mengu Yazicioglu <mailto:me...@devinim.com.tr>> wrote:
Hi
Changing line 93 to $overlay_framework = undef if
($overlay_framework == '_USE_ORIG');
will solve the issue
Mengü Yazıcıoğlu
Devinim
On 5.05.2023 22:35, Mengu Yazicioglu wrote:
Hi,
We've also hit the same problem and trying to solve the issue.
If we can, I'll share here.
Mengü Yazıcıoğlu
Devinim
On 5.05.2023 19:36, Michael Hafen wrote:
Looks like a bug in v22.11.05 to me. Here's line 93 of
tools/manage-marc-import.pl <http://manage-marc-import.pl>:
$overlay_framework = undef if $overlay_framework = '_USE_ORIG';
I think the second '=' should be 'eq'.
Same file in the master branch looks the same too.
On Fri, May 5, 2023 at 5:56 AM Tiago Murakami
mailto:trmurak...@gmail.com>> wrote:
Hi,
I try to import an MARC file in koha and job failed.
I search the log file intranet-error.log and found this error:
[Fri May 05 08:50:43.696999 2023] [cgi:error] [pid 7720]
[client ::1:42966] AH01215: Found = in conditional, should
be == at
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl
<http://manage-marc-import.pl> line 93.:
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl
<http://manage-marc-import.pl>, referer:
http://localhost:8080/cgi-bin/koha/tools/manage-marc-import.pl?import_batch_id=1
Can you please let me know if this is a configuration error
or a system error?
Thanks
--
Tiago Rodrigo Marçal Murakami
Bibliotecário
_______
Koha-devel mailing list
Koha-devel@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/
--
Michael Hafen
Washington County School District Technology Department
Systems Analyst
_______
Koha-devel mailing list
Koha-devel@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/
_______
Koha-devel mailing list
Koha-devel@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/
_______
Koha-devel mailing list
Koha-devel@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/
--
Tiago Murakami
___
Koha-devel mailing list
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/
Re: [Koha-devel] Bug 19767: serial-issues.pl unused?
+1 for removing the dead pages and code On 08.12.2017 07:56, Josef Moravec wrote: I agree, it's not linked from anywhere as I can say, and looks like it's not even fully functional... at least in 17.05 where I make quick test Best Josef čt 7. 12. 2017 v 18:46 odesílatel Owen Leonard <mailto:oleon...@myacpl.org>> napsal: Bug 19767 - serial-issues.pl <http://serial-issues.pl> is unused and should be removed https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19767 I think serial-issues.pl <http://serial-issues.pl>, serial-issues.tt <http://serial-issues.tt>, and serial-issues-full.tt <http://serial-issues-full.tt> are obsolete and should be removed. Does anyone know of any reason not to? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ___ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] kc.org support companies page broken...
At 01:50 PM 2/14/2013 +0100, Jonathan Druart wrote: Paul, La page s'affiche bien chez moi, en allant sur le lien, tu arrives sur une erreur ou bien tu utilises une recherche ? <http://koha-community.org/support/paid-support/country/#ind>http://koha-community.org/support/paid-support/country/#ind Paul - moi aussi... j'en trouve cinq. a+ Paul 2013/2/14 Paul Poulain <<mailto:paul.poul...@biblibre.com>paul.poul...@biblibre.com> Hello, I tried to go to <http://koha-community.org/support/paid-support/>http://koha-community.org/support/paid-support/ to check for indian companies being listed here... and got a nasty "no results". :\ -- Paul POULAIN - BibLibre <http://www.biblibre.com>http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper ___ Koha-devel mailing list <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha-community.org/>http://git.koha-community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/ _______ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca> ___________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plack only
David, I cannot imagine Koha without Plack, it must be so slow... unless you run very old versions. The wiki page is there since years and the psgi in our codebase as well (the one outside the debian directory). Did you only try once to read the wiki page, modify the apache config and run starman or plackup with the psgi file? Before the debian package was ready for Plack, I was doing that (since at least 2014). You really should compare the performance with and without Plack... Jonathan On Wed, 7 Feb 2018 at 21:10 David Cook wrote: > +1 Julian > > I've been avoiding Plack because we don't use Debian, but at some point > I'll have to use it, and it would be great if it was community supported > beyond just Debian. I'm happy to help test things, so long as I can have > some guidance on what to do. > > (I'd love for the multi-tenant management tools to be de-debianized as > well, but totally recognize that money/time is an obstacle. It's something > I'd like to look at more in the future myself, but occupied with non-Koha > projects at the moment...) > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 <02%2092%2012%2008%2099> > Direct: 02 8005 0595 <02%2080%2005%2005%2095> > > > -Original Message- > From: koha-devel-boun...@lists.koha-community.org [mailto: > koha-devel-boun...@lists.koha-community.org] On Behalf Of Julian Maurice > Sent: Thursday, 8 February 2018 3:50 AM > To: Tomas Cohen Arazi > Cc: koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] Plack only > > Are they really in sync ? They look very different (I cannot use the rest > api with misc/plack/koha.psgi for instance). > > IMO a good starting point would be to move debian/templates/plack.psgi > outside of debian/ and make it the .psgi reference file for all types of > install (and remove misc/plack in the process). > Any thoughts ? > > Le 07/02/2018 à 13:37, Tomas Cohen Arazi a écrit : > > Good point, Julian. You are right. > > > > Basically, we ship misc/plack/* which we keep in sync with > > debian/templates/plack.psgi. > > > > I would love to spend some time de-debianizing hte multi-tenant > > management tools, but its been hard to find sponsorship or time for it. > > Most people are comfortable with Debian it seems. > > > > Regards > > > > El mié., 7 feb. 2018 a las 9:26, Julian Maurice > > (mailto:julian.maur...@biblibre.com>>) > > escribió: > > > > What about people that do not use Debian ? It seems that there is no > > "standard" way to use Plack outside of the Debian world, and it looks > > like 90% of https://wiki.koha-community.org/wiki/Plack is outdated. > > If we abandon CGI support, I think we should first provide a clear > setup > > documentation. I would happily rewrite the wiki page, but I'm not > sure > > of what to write (how to setup Plack on dev install for instance, or > > 'standard' install without debian packages). > > Or maybe I'm missing some important up-to-date documentation about > > Plack ? > > > > (somewhat) related bug: > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 > > > > Le 06/02/2018 à 19:50, Tomas Cohen Arazi a écrit : > > > For running in Plack-mode, people needs to: > > > > > > sudo koha-plack --enable > > > sudo koha-plack --start > > > sudo systemctl restart apache2 > > > > > > after creating the . > > > > > > What I meant is that we should have people avoid the need for those > > > commands. And people with specific needs that require non-Plack > setups > > > can do it. > > > > > > I started thinking of this in the context of bug 20134 [1] BUT > also in > > > the context of bugs 18315 [2] and 7174 [3]. > > > > > > Both of the latter bugs propose interesting ways of refactoring > > > authentication, and I'm sure abandoning CGI-mode could help > > simplify the > > > process. > > > > > > [1] > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20134 > > > [2] > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 > > > [3] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 > > > > > > El mar., 6 feb. 2018 a las 11:00, Julian Maurice > > > (ma
Re: [Koha-devel] [SIGNED_OFF] labels
I think that there's an alias in the gitconfig on kohadevbox (among other
places) that adds the [SIGNED_OFF] label. This is from my gitconfig on a
different box, but kohadevbox has something similar IIRC:
[alias]
so = "!f() { c=`expr $1 - 1`; git filter-branch -f --msg-filter
\"echo -n \\\"[SIGNED-OFF] \\\" && cat && echo \\\"\nSigned-off-by: Barton
Chittenden \\\"\" HEAD~$c^..; }; f"
On Fri, Aug 25, 2017 at 6:17 AM, Tomas Cohen Arazi
wrote:
> +1
>
> On vie., 25 de ago. de 2017 4:07 AM Marc Véron wrote:
>
>> +1
>>
>> Am 25.08.2017 um 08:52 schrieb David Cook:
>>
>> +1
>>
>>
>>
>> David Cook
>>
>> Systems Librarian
>>
>> Prosentient Systems
>>
>> 72/330 Wattle St
>>
>> Ultimo, NSW 2007
>>
>> Australia
>>
>>
>>
>> Office: 02 9212 0899
>>
>> Direct: 02 8005 0595
>>
>>
>>
>> *From:* koha-devel-boun...@lists.koha-community.org [
>> mailto:koha-devel-boun...@lists.koha-community.org
>> ] *On Behalf Of *Marcel de
>> Rooy
>> *Sent:* Friday, 25 August 2017 4:29 PM
>> *To:* Koha-devel
>>
>> *Subject:* [Koha-devel] [SIGNED_OFF] labels
>>
>>
>>
>> Hi all,
>>
>> I would favor stopping the use of adding [SIGNED_OFF] labels to patches
>> when it is not strictly needed (which normally is the case).
>>
>> Only when (exceptionally) a few patches are signed and a few are not on
>> one report, I could see its use.
>>
>> At this moment they need to be obsoleted manually with git bz.
>>
>> Can we stop adding them ?
>>
>>
>>
>> Marcel
>>
>>
>> ___________
>> Koha-devel mailing
>> listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>>
>> ___
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>
> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io <http://theke.io/>)
> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
> GPG: B2F3C15F
>
> _______
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
Re: [Koha-devel] SPAM in bugzilla: what do we do ?
Wait, someont//thing is writting bug report with the title "SPAM", or have they been rewritten by an admin leaving no trace? Because I expect my spam to at least offer me 8000$/month working from home. On 09/08/2016 09:13 AM, Jonathan Druart wrote: The later: 17276, 17242, 17219, 17199, 17071, 17070, etc. 2016-09-08 13:52 GMT+01:00 Mark Tompsett : Greetings, Define "SPAM" bug. Someone not searching for duplicates? People advertising something completely not related to Koha? The former means at least they are interacting with the community. The latter is a serious problem. GPML, Mark Tompsett -Original Message- From: Tajoli Zeno Sent: Thursday, September 08, 2016 8:39 AM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] SPAM in bugzilla: what do we do ? Hi to all, Watching new bug in bugzilla I see around one SPAM 'bug' every 2 day. What do we want to do with those 'bugs' ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
