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

Current status of Plack in Koha staff client?
by Leif Andersson 10 Jul '15

10 Jul '15

Hi, during the last few days I have been looking at Plack. Rather confusing. And I wonder: What is the current status of Plack in Koha staff client? I started looking at koha 3.18. With the Plack patch applied. I still had various utf8 problems in facets, in column location (of results), and I believe also in Patron search. After upgrading to 3.20.01.000 (package install on Debian GNU/Linux 7.6 (wheezy)) I have not - so far - experianced any utf8 problems. Does anybody know what was done to fix this? In v 3.20 I still have a lot of different cache(?) problems, though. Well, simple updates like global system preferences -> Staff client -> IntranetNav seems to work fine. (any text is displayed on every screen in Koha, so it is easy to spot success/failure) So if I change the text in a session (intranet:5001 plack), then the change is shown when I leave the preferences page and go to another koha screen. It is also shown in plack sessions started later on the same or on other machines. But if I change i.e. sysprefs -> Searching -> setting UseQueryParser to "Try" The change is not reflected in my current session In fact it seems I can not make any plack driven session use QueryParser. If I connect through port 8080 QueryParser is used. If I check "About Koha" to see the recentness of my perl modules. And then goes on to upgrade some of the modules. This will be poorly reflected in any plack driven session launched *after* the upgrade! Sometimes a plackdriven session may all of a sudden take me to Koha webinstaller! re-Loading the previous page may solve the problem. (Caused by lost mysql connection?) All in all it gives the impression that Plack in Koha staff module is still very unstable and unreliable. Does anyone have a contrary experiance? If others have the same experiences as I have: are there any plans to fix the problems? Has anyone done more systematic and more exhaustive tests? Has it been shared somewhere? /Leif Leif Andersson, systems librarian Stockholm University Library Sweden

2 1

QA script - New check for spelling
by Jonathan Druart 09 Jul '15

09 Jul '15

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

3 8

Koha Community Newsletter: June 2015
by kohanews 03 Jul '15

03 Jul '15

Fellow Koha users: The Koha Community Newsletter for April 2015 is here: http://koha-community.org/koha-community-newsletter-june-2015/ 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. Thanks! Chad Roseburg Editor, Koha Community Newsletter

1 0

»Command-line Utilities« vs. »Packaging« categories
by Mirko Tietgen 30 Jun '15

30 Jun '15

I have written two patches today which already existed. One, because I misunderstood something, the other because I searched for a bug in (and added my patch to) »packaging«, while the solution was in »Command-line Utilities«. Apart from having learned to take sunday off instead of writing redundant code, I wonder why we have these two categories which seem to be confusing to everyone. Take a look and you will see what I mean, there is a lot of koha-* scripts in both. Can we agree on having all command-line stuff used exclusively with package installations in »packaging« in the future? Cheers, Mirko PS. As it is redundancy day for me, I bet I have also missed an email saying exactly the same a few days ago. -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

4 6

PRESENTATION: New member
by Anders Gunnare 29 Jun '15

29 Jun '15

Hello Word ;) My name is Anders, working at Luleå Technical University. My background is old-school Oracle DBA :) with Java/SED/AWK/Unix shell script/C++ and Fortran as programing languages. Unix/Linux experience. Have been walking a long way in the promiSED land, sometimes with awk as my brother in arms. Right now, at this very moment me and some colleagues are working in a migration project from Aleph (Oracle) to Koha. Have done a lot of programming with the database as the central part of all systems, most of the time I have been living inside the db :) Well, nature-photo is one of my biggest interest, www.enfotograf.se Regards Anders Gunnare IT-service Luleå tekniska universitet, 971 87 Luleå 0920 - 49 14 50 (070 306 40 37) anders.gunnare(a)ltu.se www.ltu.se

5 4

DB-QUESTION: Encrypt/decrypt password field in the table BORROWERS
by Anders Gunnare 29 Jun '15

29 Jun '15

Hello Word :) Which encryption method is used to encrypt/decrypt the password field in the database for the table borrowers ? I need to create users "by hand" with core insert :) In my case I have a password (not encrypted) which I would like to store in the table and column for the password. But how shall I do that ?! Regards Anders Gunnare IT-service Luleå tekniska universitet, 971 87 Luleå 0920 - 49 14 50 (070 306 40 37) anders.gunnare(a)ltu.se www.ltu.se

2 3

Re: [Koha-devel] [Koha-patches] Bug 14407 - Limit web-based self-checkout to specific IP addresses
by Jesse 25 Jun '15

25 Jun '15

(moving this discussion to koha-devel) Koha currently just uses regular expressions to match against IP addresses (see line 1040 or so in latest C4/Auth.pm). While this isn't terribly elegant, it's at least simple; what additional benefits does Net::IP::Match::XS bring? (It would also be a problematic dependency, given that it's not currently a Debian package.) 2015-06-24 22:59 GMT-06:00 Nicholas van Rheede van Oudtshoorn < vanoudt(a)gmail.com>: > Greetings everyone, > > As I'm still very much a perl newbie, I'd love to get some feedback on a > patch I just pushed to bug 14407 (my own bug!) We use Self-Checkout here > <http://library.pbc.wa.edu.au/>, with users just having to scan their > barcode to take books out. Our OPAC is also live over the internet. That > means that anyone who knows Koha, can access the self-checkout from off > campus! This patch adds a preference allowing one to limit access to those > pages to specific IP addresses or ranges. I've used Net::IP::Match::XS to > do the heavy lifting - is there another library that Koha already uses to > do the same sort of thing? > > Thanks in advance, > Nick > Perth Bible College <http://www.pbc.wa.edu.au/> > > > _______________________________________________ > Koha-patches mailing list > Koha-patches(a)lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-patches > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Jesse Weaver

1 0

DB: Any stored procedure to create a patron/user
by Anders Gunnare 25 Jun '15

25 Jun '15

Hello Word :) Is there any stored procedure for the Koha db MySQL that takes some parameters (input) and creates a patron/user ?! Have searched, havn't found ?! Or some guideline which tables to populate ... I assume that there must be other tables then borrowers included. Yes, I have seen the db-model, and I become afraid .... Regards Anders Gunnare IT-service Luleå tekniska universitet, 971 87 Luleå 0920 - 49 14 50 (070 306 40 37) anders.gunnare(a)ltu.se www.ltu.se

2 1

koha and mod perl
by Gaetan Boisson 25 Jun '15

25 Jun '15

Hello all, we have kept working on mod perl, and have reached a state that seems fairly stable to us for now. I know the community is working towards plack support, so this could be regarded as a temporary trick, but since most of us use Apache anyway to serve Koha, i think it's a trick worth having a look at. While we haven't managed to get plack in a state stable enough that we felt we could set it up in production for one of our libraries, we feel like we are close enough with mod perl and will likely try this very soon. So if you are feeling brave and want to give it a ride, you can head to http://intranet-demo.biblibre.com/ (login/pwd test/test, this is reset every night) and http://demo.biblibre.com/ to see how much faster it feels. We'll keep you posted once we've tried it in a real production environment ! -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.boisson(a)biblibre.com

1 0

Re: [Koha-devel] QA script - New check for spelling
by Mark Tompsett 25 Jun '15

25 Jun '15

Greetings, Christopher Nighswongerchris.nighswonger(a)gmail.com wrote: > Of course if we stick to using US English (or whatever, really) > as the default, that should really not be an issue. Agreed. > Seems like we've been down this road before. This patch makes the road more apparent. This may or may not be pleasant for some people. Languages, even dialects of English, are a politically charged mess. I won’t even go into localization issues. GPML, Mark Tompsett

1 0