May 2013 - 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

Fedora packages // including PLACK support
by Nicholas van Rheede van Oudtshoorn 24 Jul '13

24 Jul '13

Hello all! For those that are interested, I've made a repository (the RPM version of a PPA :-) ) to install all of the requirements for koha 3.10 - including those needed to get plack up and running. The repo can be added by running: sudo wget " http://download.opensuse.org/repositories/home:/vanoudt/Fedora_17/home:vano…" -O /etc/yum.repos.d/koha.repo A Fedora 18 repo should also be available soon. (I'm running f18, the repo just isn't live yet). Also attached are some systemd service files. Simply copy them into /lib/sytemd/system, copy koha.env into /etc/koha and then enable them using systemctl enable kohazebra.service systemctl enable kohaopac.service systemctl enable kohaopac.service As for plack - WOW! This stuff is amazing. I've made some modifications to the psgi files so that they run using a normal installation from source, and also so that they redirect from an empty URL to the main opac/intranet page. I've attached the psgi files here (install them in /usr/share/koha/psgi ) if anyone is interested! A great new release! Hope these ramblings of mine are of some use to someone! Nicholas van Oudtshoorn Perth Bible College library.pbc.wa.edu.au

3 2

opac / no results for a search
by Samuel Desseaux 13 Jun '13

13 Jun '13

Hi! We use koha 3.12 and we have today a problem with our opac. When we do a search, it gives no results (but, the professional search work fine). I run zebra as a user named koha and the ownership of files are ok. I've checked some systempreferences as "hidelostitem" and "opacsuppression": all is ok. An idea? Best regards Samuel

7 17

3.6.1 upgrade to 3.8.5 and bug 8071
by Paul 06 Jun '13

06 Jun '13

In my continuing quest to upgrade 3.6.1 to 3.8.x without loss of functionality (specifically authorities, generally zebra) I have now upgraded my sandbox (db fully synchronized with the production box) to 3.8.5 along the lines of "bug 8071 blocker" ... however in 3.8.5: Results 1 to 20 of 424 Summary Used in Delete World War, 1914-1918 Details 0 biblio(s) Delete World War, 1914-1918 Aerial operations. Details 0 biblio(s) Delete / ... / in 3.6.1: World War, 1914-1918 Details 5 biblio(s) World War, 1914-1918 Aerial operations. Details 16 biblio(s) / ... / So, are authorities during the upgrade still broken? Is it my db? I did do a "test" during the upgrade: paul@server:/koha-3.08.05$ sudo make test / ... / Test Summary Report ------------------- t/Barcodes_ValueBuilder.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 10 tests but ran 0. Files=89, Tests=8155, 15 wallclock secs ( 0.72 usr 0.13 sys + 13.75 cusr 0.86 csys = 15.46 CPU) Result: FAIL Failed 1/89 test programs. 0/8155 subtests failed. make: *** [test_dynamic] Error 255 but decided (despite that) to try: paul@server:/koha-3.08.05$ sudo make upgrade No errors reported From web interface: Update report : Upgrade to 3.08.04.001 done (Bug 8657 - Default sort by call number does not work. Correcting system preference value.) Upgrade to 3.08.04.002 done. (Bug 8002: Update patron attribute types table from varchar(1) to varchar(10) category_code) Warning to Koha System Administrators: If you use borrower attributes defined by borrower categories, you have to check your configuration. A bug may have removed your attribute links to borrower categories. Please check, and fix it if necessary.Upgrade to 3.08.05.000 (3.8.5 release) done So ... is 3.8.x repairable? What am I missing? thanks - Paul

3 7

Broken url in arabic facets.. and fix
by Bernardo Gonzalez Kriegel 06 Jun '13

06 Jun '13

Hi, Karam made an interesting discovery for Bug 10176 [1], putting "use utf8;" on Search.pm fixes URL of facets (not display well for me, but url works). Digging a little I found that on line 574 of master Search.pm there is a strange symbol (last between []). Seems to be an inverted question mark. Karam saids that is Arabic one. 572:# Sanitize the link value : parenthesis, question and exclamation mark will cause errors with CCL 573- my $facet_link_value = $one_facet; 574- $facet_link_value =~ s/[()!?¡¿؟]/ /g; 575- Question: this char is a typo? Was introduced on Bug 9183 [2] 'use utf8;' fixes the substitute, and the URLs. Also removing that char gives the same effect (without 'use utf8:' Patch is from jcamins Regards, bernardo [1] http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10176 [2] http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9183 -- Bernardo Gonzalez Kriegel bgkriegel(a)gmail.com

4 6

OPAC dir structure redesign
by Mason James 05 Jun '13

05 Jun '13

hi All Owen and I were talking recently about a plan to improve the current OPAC directory structure... the big problem is there is currently much duplication of unnecessary dirs/files. each theme has many duplicated files - and each language for each theme has many duplicated files all this duplication means that subtle bugs can occur... now that we have got the awesome new CCSR theme added, the next step is to fix the OPAC dir structure to accommodate multiple themes easily and safely :) i have a proposed redesign, which i think is the best balance of removing all duplication, and making the least number of changes to the existing structure in the new design there are 2 new top-level dirs, 'themes' and 'langs'. note: these are the *only* newly created dirs - the rest of the redesign is simply moving existing dirs from one location to another location each theme's dir (eg: prog or ccsr) only needs a 'css' dir, all other theme's existing subdirs can be moved to the shared top-level 'lib' and 'images' dirs again, with the language subdirs… each 'langs' subdir (eg: en or fr-FR) only needs an 'includes', 'modules', and 'xslt' dir (as these are the only dirs that have any actual language translation/substiution applied to them) all other existing language's subdirs can be moved to the shared top-level 'lib' and 'images' dirs, too below is an example of a redesigned OPAC dir structure, for 2 themes, with 2 languages (en and fr-FR) the directory/file count has been reduced from from 124 directories, 2542 files… to 60 directories, 1857 files any thoughts or improvements...? opac-tmpl └── themes (new) ├── ccsr │ └── css └── prog └── css ├── langs (new) │ ├── en │ │ ├── includes │ │ │ └── search │ │ ├── modules │ │ │ ├── errors │ │ │ ├── sco │ │ │ ├── search │ │ │ ├── svc │ │ │ └── text │ │ └── xslt │ └── fr-FR │ ├── includes │ │ └── search │ ├── modules │ │ ├── errors │ │ ├── sco │ │ ├── search │ │ ├── svc │ │ └── text │ └── xslt ├── images (existing, shared for all themes and langs) │ ├── datatables │ └── itemtypeimg │ ├── bridge │ ├── carredart │ ├── colors │ ├── crystal-clear │ ├── liblime-kids │ ├── npl │ ├── Seshat │ └── vokal ├── lib (existing, shared for all themes and langs) │ ├── famfamfam │ │ ├── mini │ │ └── silk │ ├── greybox │ │ └── GreyBox_v5_5 │ │ ├── adobe_images │ │ ├── compression_lib │ │ ├── greybox_source │ │ │ ├── base │ │ │ ├── gallery │ │ │ ├── set │ │ │ └── window │ │ └── static_files │ ├── jquery │ │ ├── images │ │ └── plugins │ │ └── themes │ │ └── classic │ └── yui │ ├── container │ ├── menu │ └── utilities

13 22

git koha >koha 3.12.00
by Samuel Desseaux 05 Jun '13

05 Jun '13

hi, i've a git question: I've made a git remote update and a git rebase v3.12.00 on my test instance but i keep the same version( 3.11.00.203), An idea? Best regards, Samuel

3 3

Cherry-picking and SIPServer unification
by Galen Charlton 03 Jun '13

03 Jun '13

Hi, Via the magic of git cherry-pick -X ignore-space-change, it turns out that at least some patches made on Koha's fork of SipServer (a.k.a. OpenNCIP) can be brought over mostly as is. For example, consider Koha bug 3723 [1], SIPServer bug 1180479 [2], and the patch of Colin's I was able to cherry-pick as a proposed fix for SIPServer [3]. SIPServer is a GPL2+ project (though note that although the license change from GPL2 to GPL2+ has been agreed to by all significantly copyright holders, there's a patch pending to update the source files accordingly). Koha, of course, is GPL3+ and once was GPL2+. Per my reading of the GPL compatibility matrix [4], I don't see any licensing bar to cherry-picking patches over from Koha to SIPServer, because future releases of SIPServer can be "conveyed" as GPL3. Consequently, I intend to do some cherry-picking to help move us to the point where Koha can fold its fork into. If anybody sees a technical or licensing problem with this, please let me know. [1] http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3723 [2] https://bugs.launchpad.net/sipserver/+bug/1180479 [3] http://git.evergreen-ils.org/?p=working/SIPServer.git;a=commit;h=bbee352fc8… [4] http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

2 1

Re: [Koha-devel] RFC: Plugins QA
by Paul 01 Jun '13

01 Jun '13

At 01:02 PM 5/31/2013 -0400, Kyle Hall wrote (and maybe some attributions got lost): >[snip] >Agreed. Most plugin logic would make for a very good basis for an Koha >patch. [snip] > >I'm getting a bit of a twitch here -- I see the utility of this as a >workaround, but I hope that this plugin has a very short life on >account of the underlying bugs getting fixed. > >Agreed. This utility is a workaround for an as-of-yet unidentified bug. [snip] > >If I had known this would be of interest to more users, I would have >started with a patch instead of a plugin. I'd be more than happy to >patch-ify this plugin when I have the time. [snip] Tarballs, packages, gits (including vendors), stables, latest, bugs and patches, wikis (various), tools, reports, live-DVDs, mailing lists, chat, maybe more, and now plug-ins? Could we please look at what the "open source" world is doing? Apache, SendMail, Perl, PostFix, FireFox, Debian, Ubuntu, OpenOffice, LibreOffice ... are fairly stable with an established security update capability. Even Java and MySQL are simplifying. I had a "rather important" librarian from Quebec drop in, out of the blue, yesterday to talk about Koha. Her group (37 libraries) had previously been burned by a trial commercial implementation of Koha (no need to quote names), so they're using Opals, but "liked the idea" of Koha. First question: "stability?" She was well aware that we announce on our OPAC: "System change / Koha v3.8.4 on line 14 September 2012" (I think that was fairly timely) so she asked about 3.10 and 3.12; my answer "we're happy; two year cycle; look at it again in September 2014." I know that a number of you will ... whatever ... Paul's a pain in the neck, doesn't understand, does his own thing, but the bottom line is that <http://opac.navalmarinearchive.com/> is fully functional and is intrinsically Koha. It's (reasonably) secure (without https) and meets the needs of our users and librarians. It runs itself with minimal ( < 1 hour/week statistically ) intervention by IT personnel. There are very few institutions that have "happiness" in the form of unlimited budgets and unlimited IT departments. I'm personally intrigued by the creativity of the Koha community, so try and follow what's happening -- which is magnificent -- but doubt that your average library has the same passion. Koha needs the credibility and stability of a *system*, install, forget (except security), and put on your two-three year review list. </rant> Most respectfully, after nearly three years of getting to "know Koha" and some of the dedicated people involved, Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1