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

ldap authentication in koha 16.11 become broken when enabling plack
by Mohammad Nashbat 12 Dec '16

12 Dec '16

Hi All, We've recently upgraded to Koha 16.11 which is running on Debian Jessie, we also activated plack which makes the system really faster than before but found out that Koha ldap authentication become broken, but when we disabled plack it works fine with slowness. Any help to make koha ldap integration works with plack is highly appreciated. Thanks & Best Regards, Mohammed Nashbat Library Instructor Alfaisal University ________________________________ DISCLAIMER: This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of Alfaisal University shall understand to be neither given nor endorsed by Alfaisal University. The contents of any attachment to this e-mail may contain software viruses, which could damage your own computer system. While “Alfaisal University” has taken every reasonable precaution to minimize this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.

1 0

What's on in koha-devel #8
by Jonathan Druart 05 Dec '16

05 Dec '16

Hello librarians and developers, Koha 16.11 and its Debian packages have now been released [1]. As Mirko noted Debian Wheezy is no longer supported and Debian packages won't be provided for 3.22 [2]. I should also added that some important bugs have been reported recently and it may be better to wait for the 16.11.1 version to be released before upgrading [3, 4, 5]. Note that if you database password contain Unicode characters, you should also wait for bug 17720 (CSRF token is not generated correctly). = Refactoring = == Move to the Koha namespace == We keep on moving the C4::Members module code to the Koha namespace and a few subroutine of C4::Circulation are going to be moved as well [6]. == Remove the biblioitems.marcxml field == I have been asking for help on bug 17196 (Move marcxml out of the biblioitems table) for months now and this will certainly be my last attempt to get attention on it. As we are at the beginning of the release we should focus on it to get it pushed soon. That way we will have time to catch and fix bugs if we find some. == Rewrite of the upload feature = A month ago Marcel started to refactor the upload section [7]. This is the groundwork to start improvements in this area. Once this is pushed we will be able to add new features, so please test! = Template Toolkit syntax for notices = Kyle started a discussion some months ago [8] to switch from our home-made syntax for notices to the Template Toolkit syntax. That would bring us a lot of flexibility to write the notices. But to do so, we need a plan! We already started to support this syntax (inside 16.11) but then we have to decide what to do next. Currently the plan would be to replace the default syntax (bug 15278), then reveal in the editor that you can use this new syntax (bug 15277) and finally add documentation to help people writing/porting their own notices (bug 15276). We need to get opinions to know how we could move forward. Kyle is going to start a new topic on the Koha mailing list for that. Stay tuned! = Standardize our EXPORT = A bit more technically, I would need developer's attention on bug 17600 (Standardize the EXPORT). At the end of the last release, very bad bugs appeared at the last minute because of our circular dependencies and the way we export subroutines from routines. Everything is (quickly) explained on that bug and a patchset has been submitted for discussion. If you are aware of how we could fix that cleanly, please jump into the discussion. The next general IRC meeting is on December 7th, 14 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_7_December_2016 The next dev IRC meeting is on December 14th, 13 UTC. https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_December_20… Hope to see your there! Cheers, Jonathan [1] https://koha-community.org/koha-16-11-released-2 [2] http://lists.koha-community.org/pipermail/koha-devel/2016-November/043330.h… [3] Bug 17676 - Default COLLATE for marc_subfield_structure is not set [4] Bug 17344 - Can't set guarantor in quick add brief form [5] Bug 17709 - Article request broken [6] Bug 17677 - Move C4::Circulation code to the Koha namespace [7] Bug 17501 - Koha Objects for uploaded files [8] http://lists.koha-community.org/pipermail/koha-devel/2016-February/042316.h…

1 0

942 versus 952
by Karen Myers 02 Dec '16

02 Dec '16

Hi all I am wanting to clarify the usage of the 942$c field versus the 952$y field as I am setting up a new bib framework. I am wondering if it is necessary to have both the 942$c field and the 952$y field in the framework as they seem to record the same information i.e Koha item type. Is there an advantage to recording the same information in both fields and if not which is the preferred? We are using Koha 3.22 thanks! Karen

3 3

Improvements to framework plugins (cataloguing)
by Marcel de Rooy 02 Dec '16

02 Dec '16

Hi all, Around two years ago I wrote Koha::FrameworkPlugin now. As an ongoing project I wanted to convert existing plugins to its new style (while it also supports the old style). Unfortunately, this project did not get much further the last six months of 16.11. Two reports https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13438 and https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16203 are just waiting for a signoff already over 6 months, while they still apply. Since one report deals with normarc plugins, I hoped for Magnus, but unfortunately.. I am still hoping for some attention. Further development in this project depends on it. Testing them should not be that hard. Thanks, Marcel

1 0