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

koha installation
by Shebina K 19 Jan '05

19 Jan '05

hi.... as i found errors in koha upgradation to 2.2 (in searhing ,and in opac) i want to know whether i can install it directly and use the previous data ( that is in 2.0.2) i have the backup created by backup.sh is there any other way???? plz help me soon shebina

1 0

abt koha
by shebina 18 Jan '05

18 Jan '05

hi............ i upgraded koha 2.0.2 to koha2.2 but some searching are not working properly...like barcode and i think opac is not upgraded shebina

1 0

abt koha
by Shebina K 17 Jan '05

17 Jan '05

hi......... i am going to upgrade koha 2.0.2 to koha 2.2.0 and i want know how can i use ldap server some borrower details are stored in an another system but not in the order....(not entered into koha 2.0.2) so plz help me.... shebina

1 0

Koha 2.2.1 roadmap
by Paul POULAIN 14 Jan '05

14 Jan '05

Hi (again...) Here are my actual release notes for the future 2.2.1 version : BUGFIXES ============================ ***** Critical * fix for http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=811 : The OPAC requires uses to log in to view virtual shelves, and it requires a user with librarian privileges ***** Minor * in serials module >> add subscription >> select biblio : The next / previous page were invalid. * in serials module >> add subscription >> select biblio : impossible to report the biblio when there is a quote in it (' was not escaped) * issn were not stored correctly in non-MARC DB on biblio modification * in catalogue, modifs were not stored properly the non-MARC item DB. Affect only libraries without barcodes. * in thesaurus structure, deleting a tag delete the tag in each authtype, not only in the selected authtype. * plugin unimarc_225a (seriestitle) did not show the seriestitle list, when there was no ISBN IMPROVEMENTS ***** Major * serial subscriptions : modifs to handdle correctly more than 1 subscription of the same biblio. Enter subscription detail in subscription notes (like "for branch XX" or "for 2nd floor"). The subscription details are all shown in OPAC. * serial subscriptions : you can now delete a subscription that is not yet active (= has only 1 issue in "waiting" state) * adding series title and publication year limits in opac-search form. * improvements and fixes in Nelsonville templates **** Minor * adding publicationyear and series title in opac advanced search form * in biblio basket, adding the possibility to open a biblio (in the main window) by clicking on the title * circulation >> issue : showing borrowernumber code just after the borrower name. * the search on barcodes has been changed to "start" instead of "contains". It's more logic =============================== (+ some improvements in french translation) That's good, but no need to release a 2.2.1 urgently. I plan to release the 2.2.1 at the beginning of February. Any opinion on this roadmap ? Don't hesitate to open other bugs on bugzilla if needed. Don't hesitate to commit other bugfixes or minor improvements. NOTE : For nelsonville & translators : I think I'll try to add a flag on each line to say : * CODE : the fix is in code only, no need to do anything on templates * TMPL : the fix changed at least a template. Need to rerun translation and/or modify non default templates. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Owen, about some of your commits
by Paul POULAIN 14 Jan '05

14 Jan '05

Hi owen et al, I've seen your commits. Most of them are both in rel_2_2 and HEAD. Except the nice member-quick-search.pl, that is in HEAD only. As this seems to me a nice feature, and does not affect DB stability, I think you should commit it in rel_2_2 too. My opinion as Release Maintainer about rel_2_2 / HEAD : * if something changes a lot the DB & code => in HEAD, without any doubt. * if something improves a feature or add a minor one (like member-quick-search) => in rel_2_2 undoubtfully too. For other cases (minor change in the DB or major feature), I think the best way is to ask me (on koha-dev). Depending on the common interest for the idea, we can decide : * to put it in HEAD * to put it in HEAD until it's stable enough then backport it to rel_2_2 * to put it in rel_2_2. This last case meaning a new official 2.2.x will not be release 1 or 2 days after the commit, to have enough time to test it ;-) I begin immediatly by asking the list in another mail on a requested feature done by a french library. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

KOHA on FC3, OK?
by Bruffey, Mark 11 Jan '05

11 Jan '05

Will KOHA run OK on FC3? I'm installing clean from FC1. I'm assuming I'll install the new 2.2 [!] I'm hoping existing data can move over easily. Thanks, Mark L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264 mbruffey(a)centralseminary.edu Central Seminary www.centralseminary.edu <http://www.centralseminary.edu/> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org/> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts <http://www.centralseminary.edu/wcts> *************************************** Have you experienced the good news? "Every one who calls on the name of the Lord will be saved!" [Romans 10:13] ***************************************

2 1

A couple of search bugs in koha2.2
by T & J Kotula 11 Jan '05

11 Jan '05

Hi, I just started playing with Koha2.2, running FC3 and noticed a couple of error entries in the koha-error_log. 1. When I search for <Any word> 'searchword', from search.marc/search.pl?type=intranet I get the following: [error] Q : select distinct m1.bibid from biblio,biblioitems,marc_biblio,marc_word as m1 where biblio.biblionumber=marc_biblio.biblionumber and biblio.biblionumber=biblioitems.biblionumber and m1.bibid=marc_biblio.bibid and (m1.word like 'searchword') order by biblio.title at /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 272. 2. When I search for <Title> 'searchword', from search.marc/search.pl?type=intranet in addition to the above error I also get: [error] , and, , contains, , 0,20,biblio.title at /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 169. In both cases if I search for a meaningful word I get some search results. Thanks tomasz kotula.

2 1

Re: [Koha-devel] Patron Search Results: Edit link broken
by Owen Leonard 10 Jan '05

10 Jan '05

> What I think is really strange is that > all edit links point to this address > "memberentry.pl?bornum=20375&modify=edit" Just a stupid mistake in the template, sorry! It's updated in CVS, or I can email an updated copy if you need it. -- Owen

1 0

Re: [Koha-devel] Patron Search Results: Edit link broken
by Klaus Weidenbach 10 Jan '05

10 Jan '05

Heihei, > Did you get a response to this? No, I got no response yet to this. *gg* > It sounds like a template error to me, it will have a hard coded link, > rather than a querry link or similar. > > Is that enough info to point you in the right direction? > > Or do you need to know what the code should be? Well, I am just having Koha here as a test environment to see if it is possible to use it at my school's library, but I am not sure yet if it is useable for our environment, also because the teachers are not really used to computers. ;((( So I don't need to have this working yet and also didn't take a closer look on it, because I have also bit bad time at the moment. I found also several other things, but I think they are mostly related to the NPL-template only or on problems that arise if you change the template or language in the settings. Well, but I think I should test bit more about it before reporting maybe wrong things and so on.... Just thought to mention the first things I had realiced, that it can get fixed before the next release maybe. ;)) Regards, Klaus -- take care! xo,klaus

1 0

Re: Re: [Koha] a few koha errors
by Joshua Ferraro 09 Jan '05

09 Jan '05

SELinux users, There's a better way. Instead of disabling SELinux for httpd just change the context for the Koha directories. The utility for doing this is called 'chcon' (and I see I forgot to include information on this in the install guide). Here's a brief description of how to use it: First, check the context for the directories that you know work for httpd: [root@koha]# ls -Z /var/www/ drwxr-xr-x root root system_u:object_r:httpd_sys_script_exec_t cgi-bin drwxr-xr-x root root system_u:object_r:httpd_sys_content_t error drwxr-xr-x root root system_u:object_r:httpd_sys_content_t html drwxr-xr-x root root system_u:object_r:httpd_sys_content_t icons drwxr-xr-x root root system_u:object_r:httpd_sys_content_t manual drwxr-xr-x webalize root system_u:object_r:httpd_sys_content_t usage Then, use the chcon utility to label the koha subdirs as for their counterparts in /var/www. Here's the syntax: chcon <context> /usr/local/koha/<subdirectory> For more info on SELinux check out the FC3 FAQ: http://fedora.redhat.com/docs/selinux-faq-fc3/ Hope that helps. Post here if you have any questions, etc. (Stephen could you add the above to the "Installing Koha on Fedora Core" manual?) Joshua On Sat, Jan 08, 2005 at 08:37:52AM +0100, Giuseppe.Angilella(a)ct.infn.it wrote: > On Fri, 7 Jan 2005, Sebastian Krieg wrote: > > >Hello Giuseppe, > > > >I also use Koha with FC3. Your error´s reason is selinux. > > > >Go to command prompt an type: /usr/bin/system-config-securitylevel as root. > >There is "SELinux" and mark the entry > >"HTTPD-Service | Disable SELinux protection for httpd daemon" > > > >You can also do the same with the entry > >"SELinux Service Protection | Disable SELinux protectionfor mysqld daemon" > > > >I hope it´s the right way for you. > > > >Sebastian > > Dear Sebastian, > > it worked! Many, many thanks! > > I didn't use to have anything like that in RedHat 9.0, and was completely > stymied. > > (Incidentally, I do have the httpd entry in SELinux, but not the mysqld > one.) > > I made a lot of other trials (which I am not going to report in full > here), but observed a strange behavior. I could not execute _any_ script > located in _any_ subdir of the path /usr/local/koha/intranet/cgi-bin, even > when correctly defined in httpd.conf, whereas I _could_ execute such > scripts, if copied to /var/www/cgi-bin (or subdirs), i.e. httpd's default > location for cgi's. > > Therefore, I was beginning to fancy that a possible workaround to my > problem was to perform a new installation of koha under /var/www/koha, but > I didn't try - THANKS to your most precious suggestion! > > Many thanks again, > > Giuseppe.

1 0