- Koha - lists.katipo.co.nz

IRC Channel for Koha?
by Dan Haines 02 Sep '02

02 Sep '02

Hi I was wondering what the server name and channel was for the IRC channel for Koha. Cheers, Dan

2 1

New to Koha
by Marina Salcedo 02 Sep '02

02 Sep '02

Hi, I just found out about this wonderful project. I'm currently working in a small academic library (40 thousand volumes) in the Rep. of Panama. The collection is not automated and I'm looking for a cheap solution to this. Does anyone have any recommendations on barcode scanners that work well with the Koha system? Any other pointers I could get would be great too! I'm still working on my Library degree so I'm just getting my feet wet with this project. Still lots to learn. Thanks for all your help. Marina :) Marina Salcedo FSU-Panama Librarian 314-0367 ext. 234 email: marinasalcedo(a)hotmail.com _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com

3 2

Koha on OS X
by Rob Levandowski 31 Aug '02

31 Aug '02

I searched the archives and didn't find any record of Mac OS X being discussed, so I thought I'd share... I'm using Koha on Mac OS X to manage my personal book collection. I initially built it under Mac OS X 10.1.5. It ran fine under that version with the exception of the command-line client. In that version of Mac OS X, the curses library was broken (to put it mildly) and therefore the required Perl modules wouldn't compile. Now that OS X 10.2 is out, it appears that the curses library has been fixed, and I think I can get the command line working. I just haven't put the time into it yet, as the web interface meets my needs well. On a Power Macintosh G4 (dual 500MHz CPUs) with 512MB RAM, running OS X 10.2, Koha seems very responsive and doesn't appear to load the system much. This Mac is my main personal computer, so it's usually doing lots of other things too. I'm using a precompiled version of MySQL 3.23.49, and the Apache installation that comes with Mac OS X (aka "Web Sharing"). Nothing particularly special was required to get Koha working, other than adjusting the httpd.conf file keeping Apple's NeXT-like directory structure in mind. I don't have the wherewithal to do serious load testing on the setup, but based on how well the system performs other tasks, I'd bet that an Xserve (Apple's new rackmount Mac server) would make a very nice Koha server. -- Rob Levandowski robl(a)macwhiz.com

1 0

last minute irc request
by Pat Eyler 31 Aug '02

31 Aug '02

Brian Proffit, of Linux Today, is looking into an article on Koha. He'll be joining the #koha irc channel at about 1700GMT (2PM EDT, 11AM PDT, other conversionsare left as an exercise for the reader). If you're at all interested, please stop on by. -pate

2 2

Step by Step - ScriptAlias?
by Robert Maynord 31 Aug '02

31 Aug '02

Ron & Bill: Thanks for your suggestions regarding the httpd.conf file. I tried all of your ideas, and made the modifications (I learned & they were helpful) - but I found the source of the problem was elsewhere. When I saw that the browser said "Forbidden: you do not have permission" for the Intranet directory, it made me think. I finally solved the problem by changing the file permissions on all the Intranet Koha directories. Things work only when I give full permission to everybody: user, group and other. I'm not sure if this is a security risk - but it is a step, and both Intranet and Opac pages load. The dilemma I have now is that there is no access (in the browser) to the cgi-bin stuff. For example, when I try to do a search in koha I get the message "Forbidden: You don't have permission to access /cgi-bin/koha/search.pl" (I have opened all the permissions on directories and files). This tells me that for some reason the ScriptAlias command in the httpd.conf file is not working. I check httpd.conf and it reads: ScriptAlias /cgi-bin/koha/ /usr/local/koha/opac/cgi-bin just like it should. But obviously ScriptAlias is not forwarding. I have tried several feeble tricks: 1) Delete the koha/ part so there is only /cgi-bin/ 2) Create a directory in root called /cgi-bin/koha/ 3) Double check all file permissions in the cgi-bin directory. 4) I don't know how to check ScriptAlias independently to see if it is working. 5) Although the browser says it can't "access /cgi-bin/koha/search.pl", the opac-error_log says "client denied by server configuration: /usr/local/koha/opac/cgi-bin/search.pl" implying that the ScriptAlias is trying to get through. 6) search.pl does exist in /usr/local/koha/opac/cgi-bin/search.pl 7) Again - I am using Mandrake 8.2. I have noticed that this means several things are different, such as the location of apachectl Thanks again for your helpful suggestions! Step by step I am making progress... Robert Maynord

2 2

From the Kaitiaki
by Pat Eyler 30 Aug '02

30 Aug '02

Aug 30, 2002 To the Koha community Welcome. This has been a busy two weeks, both personally and for the Koha project. I hope that I can do justice to the different things that have happened. If I've missed something, I apologize, please feel free to email me (kaitiaki(a)koha.org) a reminder. The best news over the last two weeks is that more and more libraries are choosing Koha (see the announcements below). If you've recently made the decision to move to Koha, or are currently finishing a migration, please let me know. We have a couple of projects in the works which we could use your help with. 1.2 1.2.3 should be out in September. It will include templating throughout the OPAC, maybe online help, and some installation improvements. It is currently in testing, and we would welcome feedback from current Koha users. If you need help setting up a testing environment, please contact the developers mailing list, there are several people who would be glad to help. 1.2.4 should be out by the end of 2002. It will be the last 'new feature' release in the 1.2 cycle. (We may make more 1.2 releases, but they will contain nothing but bug fixes.) 1.4 We're on the verge of releasing 1.3.0 ... this will be the first alpha release of the 1.4 series. We'll continue making 1.3 series releases until we hit a level of completeness and stability that warrants making 1.4.0, hopefully late in 2002 or early in 2003. If you're interested in the future of Koha, this is where to look. 1.4 development will get a boost with a financial contribution from Nelsonville Public Library. They have chosen to migrate their ILS to Koha, and are going to be paying for some of the MARC Support development work that is central to the 1.4 release. I'm encouraging Koha developers (and other Perl developers) to look at their announcement at http://pate.eylerfamily.org/geek/MARCRFP.txt and consider making a proposal. Translations The french and german teams are coalescing, and both have email lists at this point. Chris Cormack, of Katipo, will have a demo of the templating code being used for translation shortly. Once that is in hand, the translators can go to town! We've also got some translations in for the Bengali and Hindi languages. Community Nelsonville Public Library (7 branches, 36,000 active patrons, and over 250,000 items in their collection) has decided to migrate to Koha. A press release has gone out, and additional stories seem to be brewing. With the kind of interest that this has generated, I'd like to continue to produce press releases for other libraries moving to Koha. If you've recently decided to make the switch, and wouldn't mind a little publicity, please contact me and we'll see what we can put together. I'm really impressed with all of the dedication and effort that have been made over the last 3 months. I think we're starting to see the fruits of our labors. happy hacking, Pat Eyler Kaitiaki/manager the Koha project

1 0

irc meeting today 2200GMT
by Pat Eyler 29 Aug '02

29 Aug '02

Hello all, this is the final reminder that we're going to be having our (irregularly scheduled) irc meeting today at 2200 GMT. Due to a job interview (yay!!!), I'll not be able to attend (boo!!!). I'd expect that you'll not miss me too much. Perhaps Si or Nick can conduct the meeting. I'd recommend something like this for the agenda (if I've missed something, please speak up). This does look a little bit long, if it's too long, perhaps we should hit part of it this week and part via email. :::proposed agenda::: Coding Issues Templating issues finding ppl to help paul with 1.4 possible shift to savannah new developers ewan's work on documenting Koha Requirements creating Bundle::KohaSupport for installing needed Perl modules Is this something we ought to pursue? Nelsonville Public Library projects Is this kind of involvement a good thing? (I think so) How do we integrate projects like these? How do we encourage more libraries to do the same kind of thing? Is there a better method than RFPs? (Maybe posting a bounty for successful completion of certain milestones?) Translations templating Tools OK on "2 person" rule for a supported translation translations list Documentation Ideas/suggestions, comments on update procedure Installer vs. manual Current "open support topics": stand-alone machines/semi-standalones, windows config. New document idea -- 'Migrating to Koha' Should we put together a guide to migrating to Koha? I'm thinking that it should start out with general issues, then move on to specifics on a system by system basis. Misc Features timetable Handling support When to start deprecating work on 1.2.X and shunting ppl to 1.4 Oct 23-24 Ohio Library Association Meeting Nelsonville is going to be making a report on using Open Source in libraries, and will be featuring Koha. How can we help them? Publicity Linux Journal has expressed interest in a story about libraries using Koha. They've requested pictures and have offered up cover story status for a sufficiently compelling piece/picture. pate will work on outlining and writing, but would like to drop in some interview bits and some timelines from successfule implementations (input/advice/criticism/etc. welcomed). Press Page Do we want to put a press page (contacts, links to stories, etc) on www.koha.org?

2 1

OPAC up - Apache forbids Intranet
by Robert Maynord 29 Aug '02

29 Aug '02

Dear William and Koha Folks: I am still working on setting up Koha for my school. Thanks William for your suggestions! I tried them - but unfortunately no change. Since then, I have been tweaking in Webmin. It seems that Apache or Mandrake sets up two virtual servers as default. Then the Koha servers are added - making four. I disabled the two non-Koha servers and made port 80 the default. Then I was able to get to the first page of OPAC Koha (no cgi yet). However, when I try to access the Koha Intranet site, I receive the message "Forbidden: You don't have permission to access / on this server". I thought this might have something to do with the user database in mySQL so I added root as a user, but no change. Some tidbits: 1) I used the install.pl script to install koha. 2) According to some Apache info, the "permission" message may occur when there is no index.html file. However, there is on in koha/intranet 3) Although i have been using the IP 192.168.0.4 for the library computer, I am ablr to access koha OPAC with library.ihm-school.org. 4) I have attached a copy of my httpd.conf file if that is helpful. I am sure that I am short on skills for setting up Koha (Apache, mySQL, perl, AuthenDBI, etc) but I am trying anyway because I believe it is important for our library, and also because I believe in open source software. Thanks! Robert Maynord ### Main Configuration Section ### You really shouldn't change these settings unless you're a guru ### ServerType standalone ServerRoot /etc/httpd #ServerName localhost #LockFile /etc/httpd/httpd.lock PidFile /var/run/httpd.pid ScoreBoardFile /etc/httpd/httpd.scoreboard ErrorLog logs/error_log LogLevel warn ResourceConfig /dev/null AccessConfig /dev/null DocumentRoot /var/www/html ### Dynamic Shared Object (DSO) Support ### ### #LoadModule mmap_static_module modules/mod_mmap_static.so LoadModule env_module modules/mod_env.so LoadModule config_log_module modules/mod_log_config.so LoadModule agent_log_module modules/mod_log_agent.so LoadModule referer_log_module modules/mod_log_referer.so #LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule mime_module modules/mod_mime.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule status_module modules/mod_status.so LoadModule info_module modules/mod_info.so LoadModule includes_module modules/mod_include.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule dir_module modules/mod_dir.so LoadModule cgi_module modules/mod_cgi.so LoadModule asis_module modules/mod_asis.so LoadModule imap_module modules/mod_imap.so LoadModule action_module modules/mod_actions.so #LoadModule speling_module modules/mod_speling.so LoadModule userdir_module modules/mod_userdir.so LoadModule proxy_module modules/libproxy.so LoadModule alias_module modules/mod_alias.so LoadModule rewrite_module modules/mod_rewrite.so LoadModule access_module modules/mod_access.so LoadModule auth_module modules/mod_auth.so LoadModule anon_auth_module modules/mod_auth_anon.so #LoadModule dbm_auth_module modules/mod_auth_dbm.so #LoadModule db_auth_module modules/mod_auth_db.so LoadModule digest_module modules/mod_digest.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule expires_module modules/mod_expires.so LoadModule headers_module modules/mod_headers.so LoadModule usertrack_module modules/mod_usertrack.so #LoadModule example_module modules/mod_example.so #LoadModule unique_id_module modules/mod_unique_id.so LoadModule setenvif_module modules/mod_setenvif.so <IfDefine HAVE_PHP4> LoadModule php4_module extramodules/libphp4.so </IfDefine> <IfDefine HAVE_SSL> LoadModule ssl_module extramodules/libssl.so </IfDefine> LoadModule vhost_alias_module modules/mod_vhost_alias.so # Reconstruction of the complete module list from all available modules # (static and shared ones) to achieve correct module execution order. # [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO] ClearModuleList #AddModule mod_mmap_static.c AddModule mod_env.c AddModule mod_log_config.c AddModule mod_log_agent.c AddModule mod_log_referer.c #AddModule mod_mime_magic.c AddModule mod_mime.c AddModule mod_negotiation.c AddModule mod_status.c AddModule mod_info.c AddModule mod_include.c AddModule mod_autoindex.c AddModule mod_dir.c AddModule mod_cgi.c AddModule mod_asis.c AddModule mod_imap.c AddModule mod_actions.c #AddModule mod_speling.c AddModule mod_userdir.c AddModule mod_proxy.c AddModule mod_alias.c AddModule mod_rewrite.c AddModule mod_access.c AddModule mod_auth.c AddModule mod_auth_anon.c #AddModule mod_auth_dbm.c #AddModule mod_auth_db.c AddModule mod_digest.c #AddModule mod_cern_meta.c AddModule mod_expires.c AddModule mod_headers.c AddModule mod_usertrack.c #AddModule mod_example.c #AddModule mod_unique_id.c AddModule mod_so.c AddModule mod_setenvif.c <IfDefine HAVE_PHP4> AddModule mod_php4.c </IfDefine> <IfDefine HAVE_SSL> AddModule mod_ssl.c </IfDefine> AddModule mod_vhost_alias.c ### ### Global Configuration ### # We now support multiple apache configurations on the same server. In # common.conf, we put all directives that are common to all implementations # (httpd, httpd-perl, etc.) Include conf/commonhttpd.conf ### ### IP Address/Port and Proxied configuration section ### # The APACHEPROXIED setting can be set in /etc/rc.d/init.d/httpd if you # are using a proxy or accelerator, like the Apache-SGI or khttpd, so that # the fast web server serves static content while Apache handles the # cgi or php files #BindAddress * <IfDefine APACHEPROXIED> Port 8080 Listen 8080 </IfDefine> <IfDefine !APACHEPROXIED> Port 80 Listen *:80 </IfDefine> # Likewise, we can set apache as the server by default and send perl # requests via ProxyPass to apache-mod_perl. It increases performance # since the perl interpreter is only used for perl and the standard apache # does all the html and image files, with a smaller footprint. # # If you install apache and apache-mod_perl, this is the default config. # If you don't want two web servers to use perl, uninstall apache, and # apache-mod_perl will not be proxied. <IfDefine PERLPROXIED> RewriteEngine on RewriteRule ^proxy:.* - [F] RewriteRule ^(.*\/perl\/.*)$ http://%{HTTP_HOST}:8200$1 [P] RewriteRule ^(.*\/cgi-perl\/.*)$ http://%{HTTP_HOST}:8200$1 [P] </IfDefine> ### ### Log configuration Section ### #Single logfile with access, agent and referer information #This is the default, if vlogs are not defined for the main server CustomLog logs/access_log combined env=!VLOG #If VLOG is defined in conf/vhosts/Vhost.conf, we use this entry CustomLog "|/usr/sbin/advxsplitlogfile" vhost env=VLOG ### ### Virtual Hosts ### # We include different templates for Virtual Hosting. Have a look in the # vhosts directory and modify to suit your needs. Include conf/vhosts/Vhosts.conf #Include conf/vhosts/DynamicVhosts.conf #Include conf/vhosts/VirtualHomePages.conf ### ### Performance settings Section ### # # Timeout: The number of seconds before receives and sends time out. # TimeOut 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive on # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 # # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 15 # # Server-pool size regulation. Rather than making you guess how many # server processes you need, Apache dynamically adapts to the load it # sees --- that is, it tries to maintain enough server processes to # handle the current load, plus a few spare servers to handle transient # load spikes (e.g., multiple simultaneous requests from a single # Netscape browser). # # It does this by periodically checking how many servers are waiting # for a request. If there are fewer than MinSpareServers, it creates # a new spare. If there are more than MaxSpareServers, some of the # spares die off. The default values are probably OK for most sites. # MinSpareServers 4 MaxSpareServers 10 # # Number of servers to start initially --- should be a reasonable ballpark # figure. # StartServers 3 # # Limit on total number of servers running, i.e., limit on the number # of clients who can simultaneously connect --- if this limit is ever # reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW. # It is intended mainly as a brake to keep a runaway server from taking # the system with it as it spirals down... # MaxClients 150 # # MaxRequestsPerChild: the number of requests each child process is # allowed to process before the child dies. The child will exit so # as to avoid problems after prolonged use when Apache (and maybe the # libraries it uses) leak memory or other resources. On most systems, this # isn't really needed, but a few (such as Solaris) do have notable leaks # in the libraries. For these platforms, set to something like 10000 # or so; a setting of 0 means unlimited. # # NOTE: This value does not include keepalive requests after the initial # request per connection. For example, if a child process handles # an initial request and 10 subsequent "keptalive" requests, it # would only count as 1 request towards this limit. # MaxRequestsPerChild 500 Include conf/addon-modules/php.conf Include conf/ssl/mod_ssl.conf Include conf/ssl/ssl.default-vhost.conf # Ports to listen to for Koha Listen *:8080 # NameVirtualHost is used by one of the optional configurations detailed below #NameVirtualHost 11.22.33.44 # KOHA's OPAC Configuration <VirtualHost 192.168.0.4:80> ServerAdmin rmaynord(a)ihm-school.org DocumentRoot /usr/local/koha/opac/htdocs ScriptAlias /cgi-bin/koha/ /usr/local/koha/opac/cgi-bin/ ErrorLog logs/opac-error_log TransferLog logs/opac-access_log SetEnv PERL5LIB "/usr/local/koha/intranet/modules" Options +Includes AddHandler server-parsed .html </VirtualHost> # KOHA's INTRANET Configuration #<VirtualHost 192.168.0.4:8080> <VirtualHost 192.168.0.4:8080> ServerAdmin rmaynord(a)ihm-school.org DocumentRoot /usr/local/koha/intranet/htdocs ScriptAlias /cgi-bin/koha/ "/usr/local/koha/intranet/cgi-bin/" ErrorLog logs/koha-error_log TransferLog logs/koha-access_log SetEnv PERL5LIB "/usr/local/koha/intranet/modules" Options +Includes AddHandler server-parsed .html <Directory "/usr/local/koha/intranet/htdocs"> # AllowOverride None # Options Multiviews -Indexes Includes FollowSymLinks # Order allow,deny # Allow from all </Directory> </VirtualHost> <Directory "/usr/local/koha/opac/htdocs"> allow from all </Directory> # If you want to use name based Virtual Hosting: # 1. remove the two Listen lines # 2. replace 192.168.0.4:80 wih your.opac.domain.name # 3. replace ServerName 192.168.0.4 wih ServerName your.opac.domain.name # 4. replace 192.168.0.4:8080 wih your intranet domain name # 5. replace ServerName 192.168.0.4 wih ServerName your.intranet.domain.name # # If you want to use NameVirtualHost'ing (using two names on one ip address): # 1. Follow steps 1-5 above # 2. Uncomment the NameVirtualHost line and set the correct ip address

1 0

An RFP for work on Koha
by Pat Eyler 29 Aug '02

29 Aug '02

I'm not sure if anyone here is interested in responding to this, but I'd guess you're all interested. This is a copy of an email I've been sending to various mailing lists today. ------------------------------------------------------------------------- The Nelsonville, Ohio, Public Library has recently announced that they will be migrating to Koha, a GPL'd library software system (<http://www.koha.org>) which is written in Perl. They have decided to contribute to the ongoing development of Koha and have released an RFP to solicit bids to work on full MARC support for the 1.4 release, the RFP is available at <http://pate.eylerfamily.org/geek/MARCRFP.txt> (a copy is also included below). I'd encourage interested parties to read carefully through the RFP and to join the koha-devel mailing list (<http://lists.sourceforge.net/lists/listinfo/koha-devel>). It may also be worthwhile to join the #koha channel at irc.katipo.co.nz to discuss the project in general or MARC support specifically. If you know anyone else that might be interested in responding to the RFP, please feel free to forward it as appropriate. Further background on Nelsonville's announcement is at <http://www.linuxpr.com/releases/5053.html>. For more information, please feel free to contact me by email at info(a)koha.org. thanks, -pate Pat Eyler Kaitiaki/manager the Koha project http://www.koha.org REQUEST For PROPOSAL -- MARC 21 record support for Koha (www.koha.org) The Nelsonville Public Library invites all interested parties to submit proposals in response to the following request. Proposals may be submitted in any format, but should carefully answer all questions in the request. Proposals should be sent to Stephen Hedges, Director, Nelsonville Public Library, e-mail nelpl(a)athenscounty.lib.oh.us, fax 740-753-3543, mail 95 W. Washington Street, Nelsonville, Ohio 45764. Proposals are due no later than 8:00 A.M. Eastern Daylight Time, September 30, 2002. Any responses made in proposals from interested parties may be incorporated as part of a final agreement. BACKGROUND The Nelsonville Public Library is a public library system consisting of seven libraries serving the residents of Athens County, Ohio, USA, with 36,000 active borrowers and over 250,000 items in the collections. The library has made plans to switch from its current library automation system to Koha, but only if Koha has certain required capabilities. Among these is the ability to store and retrieve item records in MARC 21 format at the (Full) National Record Level. Accordingly, the Library is seeking proposals from parties who are capable of modifying the current Koha code to provide this capability. Proposals will be evaluated by a committee of five Library staff members, and a contract will be negotiated with the submitter of the successful proposal. Please note that the Nelsonville Public Library does not expect to fund the entire development process, but is instead offering a financial reward to encourage development of Koha to be able to handle MARC 21 format. Nelsonville Public Library may elect to share some of this financial burden with other agencies as it sees fit. SPECIAL CONSIDERATIONS Nelsonville Public Library realizes that several people/groups may wish to combine resources to fulfill the requirements of this RFP. The Library is aware of the special nature of Open Source software projects, which encourages wide participation in the development process, and is thus amenable to proposals which divide the work between parties. In such a case, however, the Library prefers to receive only one combined proposal, with payment going to only one person or organization. If no acceptable combined proposal is received, then the library will entertain partial proposals from several persons or organizations that can demonstrate a plan to coordinate their efforts toward achieving the intended goal. SELECTION CRITERA Proposals will be evaluated on the basis of cost, qualifications of the programmer(s), time to delivery, ease of integration of the proposed code into the current Koha software, and ease of upgrading the delivered software to incorporate future changes to the MARC formats. The Library also intends to share information from proposals with the current Koha development team, in order to better judge the compatibility of the proposals with the overall Koha development plan. REQUIRED INFORMATION - How will you modify current Koha tables and/or scripts to accomodate MARC 21 National (Full) Level Record Requirements? (See http://lcweb.loc.gov/marc/bibliographic/nlr/) Please provide enough detail so that the committee may judge the viability of your plan, but do not submit sample tables and/or scripts. - Who will undertake this work? - What are the qualifications of the person(s) doing this work? - How have you been involved in previous Koha development? - How long will it take to complete this work? - How much will you charge for this work? (in US Dollars, please) - How will you coordinate your work with the existing work on MARC for the 1.4 release of Koha?

1 0

C4 Error I think
by Don Wright 28 Aug '02

28 Aug '02

I just installed Koha version 1.2.2 using the installer.pl that came with the distribution. I keep getting a 500 error on every cgi file. In addition the log file looks like this for every cgi file. [Tue Aug 27 15:37:24 2002] [error] (2)No such file or directory: exec of /usr/local/koha/intranet/cgi-bin/loadmodules.pl failed [Tue Aug 27 15:37:24 2002] [error] [client 204.184.247.120] Premature end of script headers: /usr/local/koha/intranet/cgi-bin/loadmodules.pl I put the C4 directory in the /usr/lib/perl5/site_perl/5.6.1 directory so it looks like this /usr/lib/perl5/site_perl/5.6.1/C4/*.pm I also have the env in Apache and the include in koha.conf. Any assistance would be greatly appreciated. Thanks, Don Wright Aurora Schools

3 3