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

installed the 3.0.2 version , appears without CSS style sheet
by ccalle 14 Jan '10

14 Jan '10

Hello Friends I write from Bolivia, I have installed the 3.0.2 version of Koha, and I have the following problem. The first you see when I install everything works fine and Spanish, and when my machine reboot KOHA change the interface switches to English and appears without CSS style sheet. Install Ubuntu. Can anyone help me please. Thank you. Christian Jhonny Calle Jahuira La Paz - Bolivia

1 0

Zebra crashes
by Marcel de Rooy 14 Jan '10

14 Jan '10

Hi all, I did already mail to the zebra list, but does anyone of you have experience with zebrasrv segfaulting? Like this: Jan 14 10:11:43 localhost kernel: zebrasrv[32625]: segfault at 88 ip 0000003d45a0e37c sp 00007fffa7cca610 error 4 in libyaz_server.so.3.0.0[3d45a00000+11000] Versions are: Zebra 2.0.37 and YAZ 3.0.34 If so, did upgrading to higher versions of Zebra and/or YAZ resolve your problem? Thanks. Marcel

1 0

zebra for new item types
by Christopher Curry 13 Jan '10

13 Jan '10

FYI: Also posted to koha(a)lists.katipo.co.nz. Hello all, I added three new item types and imported records from those item types. Only records with the existing "BK" item type are showing up in a search. I didn't get any errors during indexing. I wonder if it's necessary to configure zebra so it sees the new item types? Can anyone point me in the right direction? I've been looking at this page in the manual, but it doesn't reference which configuration files to edit: http://koha.org/documentation/manual/3.0/searching/guide-to-searching/index… In addition, I imported 215,000 BK, but the following search: cgi-bin/koha/opac-search.pl?idx=kw&op=and&idx=kw&op=and&idx=kw&limit=mc-itype%3ABK&sort_by=relevance&do=Search only returns 135,906 results. I haven't yet determined the common properties (if any) of the 79,000 missing records. Any pointers to zebra configuration documentation would be greatly appreciated. -- Cheers, Christopher Curry Assistant Technical Librarian / Assistant IT Officer American Philosophical Society 105 South Fifth Street Philadelphia, PA 19106-3386 Tel. (215) 599-4299 ccurry(a)amphilsoc.org <mailto:ccurry@amphilsoc.org> *For technical support, please use helpdesk(a)amphilsoc.org <mailto:helpdesk@amphilsoc.org>* Main Library number: (215)440-3400 APS website: http://www.amphilsoc.org

1 0

Re: [Koha-devel] [Koha] New Koha Offline Circulation tool
by Kathy Rippel 13 Jan '10

13 Jan '10

3 5

Re: [Koha-devel] [Koha] New Koha Offline Circulation tool
by Kathy Rippel 13 Jan '10

13 Jan '10

1 0

Re: [Koha-devel] Road Types
by Nicole Engard 13 Jan '10

13 Jan '10

I love that idea!! I'm going to submit it as a suggested enhancement via bugs.koha.org. Nicole On Wed, Jan 13, 2010 at 12:24 AM, Pablo A. Bianchi <pbianchi(a)fi.uba.ar> wrote: > On Mon, Jan 4, 2010 at 1:37 PM, Nicole Engard <nengard(a)gmail.com> wrote: >> >> We need a consensus of sorts on an issue that has a few bugs >> associated with it. In America addresses go 'street number' 'street >> name' 'street type' -- in France it goes 'street number' 'street type' >> 'street name' > > in Spanish it goes 'street type' 'street name' 'street number'. > >> >> This is coming across as a display problem on the patron records. So >> I'm wondering if there is a way that we can set up the templates to >> display the address in the way that the librarian chooses. Right now >> there are a few bugs related to the fact that the street number >> and/order street type doesn't even display - when I went to fix them I >> realize (with Owen's help) that I might be causing some >> internationalization issues - so I wanted to consult with you all on >> what we think is the best way to tackle this. > > There are only 6 ( factorial(3) ) possibilities. A drop-down menu on system > preferences? (I18N/L10N?) > >

1 0

Web crawlers hammered our Koha multi server
by Rick Welykochy 13 Jan '10

13 Jan '10

Hi all We are running several instances of Koha on the one box using Linux Vserver. The other night the server was brought to its knees and mysql ran out of free connections. Further investigation found over 80 instances of perl + Apache running OPAC search queries. There were many attendant instances of Zebra spawned as well, seeing to these searches. Once our daily backup kicked in at the same time, all hades broke lose. We were DoS'd at one stage and had to remote reboot the thing. How did the web crawlers find our obscure site? Probably due to a URL containing a search being posted to a web site. After some thought, two of us came up with a simple solution to solve this situation. The Problem: the OPAC search and OPAC advanced searches are accessible by the public from the Koha OPAC home page. Consequently, an over zealous web crawler indexing the site using the opac-search.pl script can impact the performance of the Koha system. In the extreme, an under- resourced system can experience a DoS when the number of searches exceeds the capacity of the system. The Solution: modify the opac-search.pl script in the following manner: (A) Only allow queries using the POST method; otherwise if GET is used return a simple page with "No search result found". (B) Exception: do allow GET queries but only if the HTTP_REFERER matches the SERVER_NAME. This allows all the searches to work via web site links. Here is the small code segment added to opac-search.pl, immediately after the BEGIN block: if ($ENV{HTTP_REFERER} !~ /$ENV{SERVER_NAME}/ && $ENV{REQUEST_METHOD} ne "POST") { print "Content-type: text/html\n\n"; print "<h1>Search Results</h1>Nothing found.\n"; exit; } CAVEAT: This solution does not allow one to paste an "opac_search.pl" link into the browser and have it work as previously expected. But this was the cause of the problem in the first place. A better solution is to require a user to login to the OPAC before allowing a search. Addendum: also install a robots.txt file at the following location in the Koha source tree: opac/htdocs/robots.txt The robots.txt file should contain the following contents, which deny all access to indexing engines. You can learn more about robots.txt on the web, and configure it to allow some indexing if you wish. ----------------------------- User-agent: * Disallow: / ----------------------------- I plan to submit a bug report regarding this situation, but first open it up for discussion here. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services If you have any trouble sounding condescending, find a Unix user to show you how it's done. -- Scott Adams

4 6

Use of TMPL_IF EXPR
by Owen Leonard 12 Jan '10

12 Jan '10

Re: Bug 2670 (http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2670) Is it possible to set up guidelines under which EXPR is allowed? If we can confirm that variables will be output under all circumstances would an EXPR be allowed? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

5 5

Stack smashing resolved -- we think
by Chadwick, John, DCA 11 Jan '10

11 Jan '10

Okay, it looks like the stack smashing issue has been resolved through increased allocation of memory in several places on the MySQL server. Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would the optimal memory allocation for Zebra to use for indexing (or reindexing). Thanks, John Chadwick John.Chadwick(a)state.nm.us http://www.nmstatelibrary.org <http://www.nmstatelibrary.org/> Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. ______________________________________________________________________ Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. This email has been scanned using Webroot Email Security. ______________________________________________________________________

3 5

koha with better support for postgresql
by ricardo mendoza 11 Jan '10

11 Jan '10

Hi all, at this time how to improve support for koha to use postgresql, someone could explain that you can do to make fully functional koha with postgresql.I see that postgresql offers many features than can koha use managed to improve its performance. I like to explore the possibility of starting to develop the necessary code for koha to make a complete and functional use of all PostgreSQL features, with the help of experienced developers. Thank you, Ricardo

6 10