Thanks MJ, I've managed to get the perl dependencies installed as well as Koha downloaded and compiled, however it is failing the make test because C4 can't find the other perl modules. Here's a sample from the error messages I'm getting: # Failed test 'use C4::Barcodes::PrinterConfig;' # at t/Barcodes_PrinterConfig.t line 12. # Tried to use 'C4::Barcodes::PrinterConfig'. # Error: Can't locate PDF/API2.pm in @INC (@INC contains: /home/prcsaca/koha/koha-3.00.00/blib/PERL_MODULE_DIR /home/prcsaca/koha/koha-3.00.00/blib/arch /usr/lib/perl5/5.8.8/x86_64-linux /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/5.8.8/x86_64-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl .) at /home/prcsaca/koha/koha-3.00.00/blib/PERL_MODULE_DIR/C4/Barcodes/PrinterConfig.pm line 21. I think this has something to do with the way I had to install the perl modules with my webhosting company (Bluehost) -- I had to use their cPanel to install the modules, which tells me: You will need to add |/home/prcsaca/perl| to the include path. You can do this by adding the following code to your script: || BEGIN { my $homedir = ( getpwuid($>) )[7]; my @user_include; foreach my $path (@INC) { if ( -d $homedir . '/perl' . $path ) { push @user_include, $homedir . '/perl' . $path; } } unshift @INC, @user_include; } Now I guess my question is whether anyone knows of a fast way of dealing with this without having to manually insert that code into every perl script/module that is packaged with Koha. Or am I completely off base in thinking that this is the problem... This is starting to get into areas that I'm not to familiar with... Thanks, Dwayne Collins MJ Ray wrote:

Dwayne Collins <dcollins@prcsa.ca> wrote:

...

Bluehost.com). Does anyone have experience in this area and/or know of a guide to setting up Koha on a shared server (or even better, specifically on Bluehost?) Everything I've been able to find so far only seems to deal with a standard install.

This will need to be a "single" install rather than a "standard" install, but if you have shell access and a compiler, or a cooperative sysadmin, it should be possible to install on a shared server. If the sysadmin won't install Zebra for you, I'd try NoZebra because running something like zebrasrv as a user isn't ideal, unless someone on the lists sees a problem with that.

Hope that helps,

Hi all, Thanks for the information, Joe. I made the changes you suggested and things still weren't working for me. With a little further investigation, I've discovered another problem -- Bluehost does not allow me to make alterations to apache to make the linkages to koha's conf file. Is there a way to use .htaccess to circumvent this? I'm beginning to think I should stick to running koha off a server in the backroom... Cheers, Dwayne Joe Atzberger wrote:

I don't think you want to use their code. The version they gave you is an inefficient form that applies to all their users.

All you want to do is add /home/prcsaca/perl to the "SetEnv PERL5LIB..." lines in your .conf file.

So you might have something like: SetEnv PERL5LIB "/home/prcsaca/perl:/home/prcsaca/kohaclone"

--joe

On Tue, Aug 12, 2008 at 12:48 PM, Dwayne Collins <dcollins@prcsa.ca <mailto:dcollins@prcsa.ca>> wrote:

You will need to add |/home/prcsaca/perl| to the include path. You can do this by adding the following code to your script: ||

BEGIN { my $homedir = ( getpwuid($>) )[7]; my @user_include; foreach my $path (@INC) { if ( -d $homedir . '/perl' . $path ) { push @user_include, $homedir . '/perl' . $path; } } unshift @INC, @user_include; }

If you can't set 2 environmental variables, then you can't run Koha at all. If your Apache processes run as your own user, you might be able to set the environmental variables in a profile. This seems unlikely though. You also might be able to use .htaccess, but do you know whether Bluehost actually supports .htaccess? and supports SetEnv in .htaccess? Really your host should tell you how to accomplish this: it's a very common configuration. --joe On Wed, Aug 13, 2008 at 11:16 AM, Dwayne Collins <dcollins@prcsa.ca> wrote:

Hi all,

Thanks for the information, Joe. I made the changes you suggested and things still weren't working for me. With a little further investigation, I've discovered another problem -- Bluehost does not allow me to make alterations to apache to make the linkages to koha's conf file.

Is there a way to use .htaccess to circumvent this?

I'm beginning to think I should stick to running koha off a server in the backroom...

Cheers, Dwayne

Joe Atzberger wrote:

I don't think you want to use their code. The version they gave you is an inefficient form that applies to all their users.

All you want to do is add /home/prcsaca/perl to the "SetEnv PERL5LIB..." lines in your .conf file.

So you might have something like: SetEnv PERL5LIB "/home/prcsaca/perl:/home/prcsaca/kohaclone"

--joe

On Tue, Aug 12, 2008 at 12:48 PM, Dwayne Collins <dcollins@prcsa.ca>wrote:

...

You will need to add /home/prcsaca/perl to the include path. You can do this by adding the following code to your script:

BEGIN { my $homedir = ( getpwuid($>) )[7]; my @user_include; foreach my $path (@INC) { if ( -d $homedir . '/perl' . $path ) { push @user_include, $homedir . '/perl' . $path; } } unshift @INC, @user_include; }