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

How to get CAS based Single Sign On working?
by Koustubha Kale 25 May '15

25 May '15

Hi All, I have a situation where we have a main website based on Joomla. This Joomla site uses CAS to authenticate users. We would like users ( who have already logged in to the Joomla site via CAS) to be able to follow a link to Koha site and be logged in automatically ( e.g. Single Sign On ). I have got simple CAS ( not proxy CAS ) working with Koha ( version 3.2.6 ) using the same CAS server as used by Joomla site. Still when I login to Joomla site with CAS, and then go to Koha and click on login and follow the CAS login link, I am asked to fill up CAS login information again. How can this be avoided by using CAS SSO? I have read through http://wiki.koha-community.org/wiki/SSO_CAS_improvements and am confused by the statement "Note: simple sso cas support (no proxy) has been done already by biblibre, is in testing and should be released in Koha 3.2" in there. Does this statement mean that SSO is possible with simple CAS? If yes how to set it up? If not, I have also read through bugs 6012, 5630 and the CAS Proxy examples. Frankly I haven't been able to figure out how I can achieve the above required functionality based on all the reading. Any help is much appreciated.. Another related query is, Is it possible to automatically create users in Koha once they have authenticated with CAS? Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

3 3

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

Restructuring C4
by Ian Walls 21 Sep '11

21 Sep '11

Fellow Developers, Last night, I stayed up late running circ/circulation.pl through NYTProf, to get an idea where we may be able to optimize circulation for speed. After much frustration (darn session IDs...), I was able to get a report. The results were... not exactly what I expected. It seems that much of the time spent running circ/circulation.pl is spent BEGINing the various C4 modules, multiple times. C4::Items, for example, is BEGuN 14 times in the execution of circ/circulation.pl. More stats: C4::Accounts - 8 BEGINs C4::Acquisition - 14 BEGINs C4::Auth - 14 BEGINs C4::Biblio - 14 BEGINs C4::Branch - 5 BEGINs C4::Circulation - 22 BEGINs C4::Context - 18 BEGINs C4::Dates - 12 BEGINs ... and so on. Even modules like C4::XSLT, C4::SMS, C4::Suggestions, and C4::Search::PazPar2 are BEGuN several times, without any calls to any of their subroutines. Some modules, it seems, don't have an END at the end... I was also able to get a Graphviz file out, showing all the package calls (folks may remember my keen interest in such things from KohaCon). Running it through sccmap to detect cycles, I found a very long one between several of the modules. About 8 packages long. All this indicate to me that we REALLY need to start thinking about imposing some kind of structure on C4. I'm thinking something with two-levels: Level 1 : Calls to the database, other direct interaction with stored data Level 2: Calls to Level 1 functions to manipulate data all our scripts would then be modified to call only Level 2, which would take care of talking to Level 1. At the worst, a particular Level 1 package would be BEGuN as many times as there were Level 2 packages BEGuN in the script (and we could certainly do better). It would eliminate all the cycles, as well. I can provide access to my report for anyone who needs it, or more details about how I obtained it. Whatever any of you need to keep this conversation going. This is a big deal, in my opinion, and we need to start detangling our code before too much long, or we're going to get seriously bogged down. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

11 25

Koha 3.4.1 upgarde - failed: Access denied for user 'kohaadmin'@'localhost' (using password: YES)
by ISM KIS 23 Jun '11

23 Jun '11

I am still in the process of upgrading our Koha from 3.00.06 to 3.4.1 Installation is ok. I could import the data from 3.0.6 and did the database update from the :8080 interface. But then when I run the script to remove the biblioitems I get the following error message: koha34:/opt/kohaclone/misc/maintenance # perl remove_items_from_biblioitems.pl --run DBI connect('dbname=koha;host=localhost;port=3306','kohaadmin',...) failed: Access denied for user 'kohaadmin'@'localhost' (using password: YES) at /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692 Access denied for user 'kohaadmin'@'localhost' (using password: YES) at /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692. What does that mean? ( By the way: I' m able to access mysql -ukohaadmin -pxxxxx ) Any ideas? Rudy Wuthrich Kodaikanal International School

3 3

Trouble with CSS files after creating package with translations
by Magnus Enger 23 Jun '11

23 Jun '11

Hi! I recently built my first debian package, based on the 3.4.x branch from git, and with the addition of having installed translations for the Nordic languages. (I'll write up the process of doing that on the wiki, once I'm sure I have the correct steps.) I used the Perl version of build-git-snapshot provided by attachment 4007 from bug 5602 to build the packages: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5602 (I'll sign off on the patch once I see the resulting package working, I promise! ;-) After installing the package and creating a library I noticed that a couple of CSS files are missing from the OPAC when it is viewed in any language other then English, making it look weird: http://esme.priv.bibkat.no/ Firebug tells me these two files can not be found, when the language is not English: http://esme.priv.bibkat.no/opac-tmpl/prog/en/lib/yui/reset-fonts-grids.css - 404 Not Found http://esme.priv.bibkat.no/opac-tmpl/prog/en/lib/yui/skin.css - 404 Not Found But when I view the front page in English, those two files *are* found, but from a different path: http://esme.priv.bibkat.no/opac-tmpl/prog/en/css/reset-fonts-grids.css - 200 OK http://esme.priv.bibkat.no/opac-tmpl/prog/en/css/skin.css - 200 OK The contents of the css-folders for the two languages are quite different: http://esme.priv.bibkat.no/opac-tmpl/prog/en/css/ [TXT] colors.css 05-May-2011 20:59 0 [TXT] hierarchy.css 05-May-2011 20:59 1.5K [IMG] menu-button-arrow-disabled.png 22-May-2011 14:59 173 [IMG] menu-button-arrow.png 22-May-2011 14:59 173 [TXT] opac.css 22-May-2011 14:59 34K [TXT] print.css 05-May-2011 20:59 3.1K [TXT] reset-fonts-grids.css 22-May-2011 14:59 5.0K [TXT] sanop.css 05-May-2011 20:59 28K [TXT] sco.css 22-May-2011 14:59 4.0K [TXT] skin.css 22-May-2011 14:59 84K [IMG] split-button-arrow-active.png 22-May-2011 14:59 280 [IMG] split-button-arrow-disabled.png 22-May-2011 14:59 185 [IMG] split-button-arrow-focus.png 22-May-2011 14:59 185 [IMG] split-button-arrow-hover.png 22-May-2011 14:59 185 [IMG] split-button-arrow.png 22-May-2011 14:59 185 [IMG] sprite.png 22-May-2011 14:59 3.0K (The en folder in the demo on mykoha.co.nz is identical to the folder above: http://demo.mykoha.co.nz/opac-tmpl/prog/en/css/ ) http://esme.priv.bibkat.no/opac-tmpl/prog/nb-NO/css/ [TXT] colors.css 22-May-2011 08:34 0 [TXT] hierarchy.css 22-May-2011 08:34 1.5K [TXT] opac.css 22-May-2011 08:34 34K [TXT] print.css 22-May-2011 08:34 3.1K [TXT] sanop.css 22-May-2011 08:34 28K [TXT] sco.css 22-May-2011 08:34 4.0K The contents of the lib/yui directory are also different on a regular dev install: http://sksk.bibkat.no/opac-tmpl/prog/en/lib/yui/ (5 CSS files, 3 directories, 1 PNG) and a packaged install: http://esme.priv.bibkat.no/opac-tmpl/prog/en/lib/yui/ (lots of directories, no CSS, no PNG) http://demo.mykoha.co.nz/opac-tmpl/prog/en/lib/yui/ On a non-package (dev) install the contents of the corresponding folders are the same for en and nb-NO - and they are the same as the 6 files listed for nb-NO above. http://sksk.bibkat.no/opac-tmpl/prog/en/css/ http://sksk.bibkat.no/opac-tmpl/prog/nb-NO/css/ On a working non-package (dev) installation the files are taken from the en folder, where they are indeed to be found: http://sksk.bibkat.no/opac-tmpl/prog/en/lib/yui/ http://sksk.bibkat.no/opac-tmpl/prog/nb-NO/lib/yui/ On the virtual machine where I built the package, the contents of the two css-directories are also the same, and they are the 6 files listed for nb-NO above. Looks to me like the packaging/packages is doing some rearranging of the CSS files that only works for the English templates and not for templates translated into other languages? Are there any package gurus out there who are able to see what is going on? Best regards, Magnus Enger libriotech.no

3 9

Koha Library Software
by Yury Marishev 16 Jun '11

16 Jun '11

Dear sirs, We have detected a vulnerabilities in Koha Library Software. Please contact us to obtain the details. Our disclosure policy is available here: http://en.securitylab.ru/lab/disclosure-policy.php Kind regards, Yuriy Marishev Security Engineer Positive Technologies Tel: +007 (495) 744-0144 Fax: +007 (495) 744-0187 ymarishev(a)ptsecurity.ru<mailto:ymarishev@ptsecurity.ru> www.ptsecurity.com<http://www.ptsecurity.ru/> en.securitylab.ru<http://www.securitylab.ru/>

11 16

KohaCon11 hackfest: discussion
by Paul Poulain 10 Jun '11

10 Jun '11

Hello everybody, 3 weeks ago we had our 1st IRC meeting about the next KohaCon in India. It seems I've been selected to start the discussion about the Hackfest ! We've had 3 KohaCon already : one in France (2006) one in USA (2009), one in NZ (2010). In Marseille, it lasted one week and was mostly about hacking. In USA it lasted 3 days, we had one day (and a half ?) teaching new developers how to hack, then one day hacking In NZ it lasted 3 days too. the 1st day was dedicated to some -technical- lightning talks (http://www.kohacon10.org.nz/2010/hackfest/index.html) then teaching new hackers, then doing a few hacking What should be the hackfest in India then ? We have two goals during those meetings: welcome new developers, and do some real hacking: it's very efficient to work in the same room and without clock/time differences ! I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !) The 1st part would be dedicated to teaching Koha to ppl wanting to know how to join: things like using git, Koha source code organisation, Koha database, working with templates, dealing with translations, submitting patches. kmkale suggested to have 2 days for this part, just before sunday (that would be a day-off) The 2nd part would be dedicated to hacking: showing what is underway, showing POC if applicable (Proof of Concept), playing with bugzilla, writing unit tests,... How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious. So how long should this part last ? kmkale said there will be a room available for us for as long as we want. My proposition would be to say 3 days (mon-wed): not too short, we will be able to do useful things, not too long, we'll be back home on tuesday, before or for the next week-end, back to work next monday. What's your opinion on those ideas ? anything to add ? Feel free to give your opinion, nothing has been decided yet ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 12

Hardware requirements and cluster scalability
by Olli-Antti Kivilahti 01 Jun '11

01 Jun '11

Good day to everybody at the devel-list. And greetings from Finland! The library of Joensuu has started a project to compare different open source library systems, mainly Koha and Evergreen, with the goal of moving from our current closed source system to open source. We are planning to create a consortium of minimum of a ~20 libraries, but if open ILS are found to be superrior, probably the consortium can easily grow to ~250 libraries with ~5 million articles and ~150 000 transactions/hour. I have been hard pressed to find answers to the hardware requirements of Koha and Evergreen and have been instructed to ask here on devel-list by your library managers. My main interests are the hardware requirements of the said large consortium mainframe. How well does it cluster? What sort of hard disk and ram requirements are there? How many pc units with for example 2GHz cpu, 2Gb RAM do we need? Could every library host their own databases or should they be centralized? What are the average search speeds using simple SELECTs and then complex JOINs. What are the system bottlenecks? Can the OPAC be integrated with Drupal/Liferay so it can be compatible with our new web-services strategy? Are there any publications I could read about these topics? Happy coding! -- Olli-Antti Kivilahti Open Library 2013 Library of Joensuu

3 2

Super-tiny script to check for record errors before upgrading to 3.4.x
by Tomas Cohen Arazi 31 May '11

31 May '11

Hi, being back to work after a few weeks abroad is a bit difficult, but here I am. Back to koha, and back to Perl suff. We are just planning our upgrade to 3.4 and face the problem that our install base (+30 libraries/koha deploys and growing) has several enconding (and posibly other) problems carried from the initial migration from different sources and encodings. Those problems obviously arise now that we have to access all the records to remove holdings information from them, and running remove_items_from_biblioitems.pl waiting for it to fail and discover "where" it failed is not suitable for us. So... I managed to get a script to tell me which records are "problematic" in the sense koha defines problematic. I'd like some other dev to take a look at it to check it. It can be obviously beautified and improved. There's a link here so anyone can read it: http://blogs.unc.edu.ar/koha/lang/en/2011/05/31/migracion-a-3-4-surgen-prob… Thanks in advance To+

1 0

Koha 3.2.x Roadmap Update
by Chris Nighswonger 30 May '11

30 May '11

Hi all, With the release of 3.2.10 fast approaching, there are a couple of things our attention needs to be drawn to: 1. Pending any consensus otherwise a the July 2011 IRC meeting, 3.2.10 will be the final release of the 3.2.x branch, and 3.2.x will be EOL after that point. 2. If you have bugfixes you want to go into 3.2.10, please be sure to get those into master before the string freeze date of 1 June 2011. That is two days away. I will push changes which do not affect strings up to the day before the release on 15 June 2011. 3. No bugfixes made to TT templates have been pushed to 3.2.x for obvious reasons. If you have a template change you want pushed into 3.2.x, you will have to submit a patch directly against 3.2.x and flag it with [3.2.x] in the subject line. Thanks for everyone's work in making 3.2.x the first of what we hope are many successes in timed releases! Kind Regards, Chris Nighswonger Koha 3.2.x/3.4.x Release Maintainer

1 0