also, as a more than 1M biblios library, hurray for Jonathan :)
2016-08-31 0:58 GMT+02:00 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.marcxm
2016-08-31 0:19 GMT+01:00 David Cook :
> Is ElasticSearch usable with Koha at this point? I heard a lot in 2015, but
> after Robin left I haven’t heard a word other than rumours that the patches
> had been pushed?
It's pushed and testable.
It does not work for new installs (bug 16838) and is broke
Hi devs,
Not sure I will manage to explain it better than you...
Basically we all agree that the permission check should not be done
from the controller. It would be good to let the Koha::Object-object
know if a given user can interact with it.
The problem is that the permissions can be different
2016-08-30 21:23 GMT+01:00 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 importa
2016-08-30 19:40 GMT+01:00 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.c
We had time and a resources available for a while. We got Bouzid to
learn Elastic Search, learn about its integration in Koha, then wanted
him to contribute. But been told twice to ... wait.
We certainly have no time anymore. We'll be back, but probably not
until 2017 unless sponsored.
No
Greetings,
Take the following steps:
check out, check in, restart mysql server, check out, check in... old_issues
bug!
This is because we delete from issues (among other tables) when we move it
to old_issues and "InnoDb forgets its highest auto_increment after server
restart".
Any ideas on the
> check out, check in, restart mysql server, check out, check in... old_issues
> bug!
What exactly is the bug?
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel mailing list
Koha-devel@lists.koha-community.
Greetings,
>> check out, check in, restart mysql server, check out, check in...
>> old_issues bug!
> What exactly is the bug?
Loss of history.
Unless you do this after the server restart:
use koha_library;
insert into issues (borrowernumber) values (1);
-- this will fill the gap, and should rest
Is there some consensus on having the required permissions defined in the
swagger file? If that was the case, no matter how we check them at
Koha::Object level, we need to make the permissions schema available at
that level. So we could need to parse the swagger file and cache it.
I like it for it
El mié., 31 ago. 2016 a las 9:17, Philippe Blouin (<
philippe.blo...@inlibro.com>) escribió:
> We had time and a resources available for a while. We got Bouzid to learn
> Elastic Search, learn about its integration in Koha, then wanted him to
> contribute. But been told twice to ... wait.
>
I d
On Wed, Aug 31, 2016 at 8:17 AM, Philippe Blouin <
philippe.blo...@inlibro.com> wrote:
> Now, may I suggest something? Documentation. Not user friendly, but at
> least dev-enlightening.
>
> "You" guys put time in there, as with plack and memcache and whatnot, but
> if you're on the outside, you
Fellow Koha users:
The Koha Community Newsletter for June 2016 is here:
https://koha-community.org/koha-community-newsletter-august-2016/
Many thanks to the folks who submitted articles and news to this month's
newsletter.
Please feel free to email me with any corrections or suggestions.
Tha
13 matches
Mail list logo
