Re: [Koha-devel] 16.05, zebra and jessie

2016-08-30 Thread Chris Cormack
* David Cook (dc...@prosentient.com.au) wrote: > > > > I suppose Adam at IndexData has been busy with the FOLIO project, so I doubt > he > has time to work on Zebra these days, even if we did have a patch available. > > > > Is ElasticSearch usable with Koha at this point? I heard a lot in

Re: [Koha-devel] What's on in Koha devel #3 (RESTful API)

2016-08-30 Thread David Cook
+1 The REST API is just a public interface. It should use the same internal APIs as the rest of Koha. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From:

Re: [Koha-devel] biblioitems.marcxml & biblioitems.marc / HUGE performance issue !

2016-08-30 Thread David Cook
Excitement! I've been looking forward to patches for those bugs for years. I don't have the time to test them now, but hoping that someone does soon! Of course, moving biblioitems.marcxml will break a lot of SQL reports I'm sure, but I think it's worth it. The broken reports should generate

Re: [Koha-devel] Interface patterns (tabs)

2016-08-30 Thread David Cook
Hi Owen, No worries. I haven't been checking my koha-devel mail for a little while, so it's quite the coincidence I found your message today! I suppose I was looking for an established guideline or a recommendation, but I appreciate your input nonetheless and it does answer the question! That

Re: [Koha-devel] Koha::* business objects authorization check

2016-08-30 Thread Chris Cormack
* Tomas Cohen Arazi (tomasco...@gmail.com) wrote: > Hi everyone, adding to the discussion about Koha::Objects I have a subject > that > needs broad (an urgent) discussion. > > The REST api patches are shaping up, and I'd like to focus on an important > one: > 14868 [1]. > > This bug introduces

[Koha-devel] Koha::* business objects authorization check

2016-08-30 Thread Tomas Cohen Arazi
Hi everyone, adding to the discussion about Koha::Objects I have a subject that needs broad (an urgent) discussion. The REST api patches are shaping up, and I'd like to focus on an important one: 14868 [1]. This bug introduces a way of specifying on the Swagger files, the required privileges to

Re: [Koha-devel] Sessions terminated at random under Plack

2016-08-30 Thread Tomas Cohen Arazi
Chris, of course! We are talking about debugging. The patches that solve the issue are already pushed! El mar., 30 ago. 2016 a las 15:44, Chris Cormack () escribió: > You will need to be aware though that reduces your users protection from > session hijacking

Re: [Koha-devel] Sessions terminated at random under Plack

2016-08-30 Thread Chris Cormack
You will need to be aware though that reduces your users protection from session hijacking tremendously. We really need to make fixing it a priority, without reducing security. Chris On 31 August 2016 6:40:39 AM NZST, Tomas Cohen Arazi wrote: >Magnus, there's been a lot

Re: [Koha-devel] Sessions terminated at random under Plack

2016-08-30 Thread Tomas Cohen Arazi
Magnus, there's been a lot of movement on the caching layer, and some of that work has been backported to the stable releases. Also, the RestrictSessionByIP setting was getting in the middle ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17050). There's also a problem with memcached

Re: [Koha-devel] Interface patterns (tabs)

2016-08-30 Thread Owen Leonard
> Do you have any documentation for preferred use of jQuery tabs? Hi David, Sorry to have let your question hang for so long! If I had to describe how tabs are generally used in Koha I would say that they are used to present distinct sub-categories of information about a thing in a way which

[Koha-devel] Sessions terminated at random under Plack

2016-08-30 Thread Magnus Enger
Dear Community, I am seeing a strange problem, and I'm not sure where to start digging. I have a (big) server with 30 odd Koha instances. One of these instances has been running under Plack for quite some time now, without any problems. Two new instances have a problem where librarians get