Re: [Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Michael Kuhn

Hi Liz

> I have set up a ko-fi at https://ko-fi.com/lizrea and you can
> contribute there

Sorry, but I don't like Paypal and I don't want to set up an account there.

But as said I will contribute immediately if you send me the necessary 
details (bank account etc).


Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Liz Rea
Oh everyone, you are really the best folks anywhere.

I have set up a ko-fi at https://ko-fi.com/lizrea and you can contribute
there

Why don't you all chip in a little and we can get this done lickety split
and tjay way nobody gets stuck with it all <3 <3

Thank you all so much!

Liz (wizzyrea)

On 6 Jun 2018 17:33, "Chris Brown"  wrote:

Liz,

I would be happy to chip in if you come up with an easy way to pay. Perhaps
you could set up a PayPal account?

Best Regards,

Chris Brown


On Tue, Jun 5, 2018 at 10:21 PM, Liz Rea  wrote:

> Hi all,
> I've been funding the koha-community web server for about 5 years now, and
> I've been happy to have the disposable income available to me to do that
> personally. As it turns out, this year I don't really have that and I could
> really use some help paying for it.
>
> The server is paid for yearly, this year it was $308 NZD It's all paid up
> until June of next year.
>
> If you'd be interested in tossing a few dollars my way to support running
> the website, I'd be really grateful. I think it would be better to have a
> community funded server anyway. I'm happy to keep looking after the server
> and website too.
>
> I don't have a plan currently for how best to receive the funds - ideas
> welcome on this front as well.
>
> Thanks for your consideration,
>
> Cheers,
> Liz
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Chris Brown
Liz,

I would be happy to chip in if you come up with an easy way to pay. Perhaps
you could set up a PayPal account?

Best Regards,

Chris Brown


On Tue, Jun 5, 2018 at 10:21 PM, Liz Rea  wrote:

> Hi all,
> I've been funding the koha-community web server for about 5 years now, and
> I've been happy to have the disposable income available to me to do that
> personally. As it turns out, this year I don't really have that and I could
> really use some help paying for it.
>
> The server is paid for yearly, this year it was $308 NZD It's all paid up
> until June of next year.
>
> If you'd be interested in tossing a few dollars my way to support running
> the website, I'd be really grateful. I think it would be better to have a
> community funded server anyway. I'm happy to keep looking after the server
> and website too.
>
> I don't have a plan currently for how best to receive the funds - ideas
> welcome on this front as well.
>
> Thanks for your consideration,
>
> Cheers,
> Liz
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] ssl for koha login

2018-06-05 Thread Mason James


On 6/06/18 4:06 pm, Mason James wrote:
>
> On 6/06/18 3:45 pm, Mason James wrote:
>> On 5/06/18 2:18 pm, Alvaro Cornejo wrote:
>>> Hi
>>>
>>> I´m trying to setup a ssl connection to Koha  (using letsEncrypt certs ) so
>>> my users, admin and opac can have a secure connection.
>>>
>>> I´ve folllowed letsEncrypt & certbot instrucctions but neither opac nor
>>> admin pages work.
>>>
>>> I´ve tried directing connections manually and configuring apache for
>>> redirect unsuccessfully.
>>>
>>> Any hints on this?
>>>
>>> This is mostly to avoid the upcoming chrome config where it will display an
>>> unsafe site warning to any site requiring login that does not use ssl
>>>
>>> Regards,
>>>
>>> Alvaro
>>> ___
>>> Koha mailing list  http://koha-community.org
>>> Koha@lists.katipo.co.nz
>>> https://lists.katipo.co.nz/mailman/listinfo/koha
>> hi Alvaro
>>
>> here's an apache config that has worked well for me
>>
>> it has some extra magic to improve it's SSL score
>>
>> the config now gets an 'A+' on the following site...
>>  https://www.ssllabs.com/ssltest
>>
>> i'll aim to add this to the Koha wiki
>>
>> cheers, Mason
>>
>>
> ...and here's a nice 'cert renew' solution, using LE's cli.ini file
>
>
> root@deb8:/# cat /etc/letsencrypt/cli.ini
> domains = demo.foo.org, demo-admin.foo.org
>
>
> root@deb8:/# cat /etc/cron.d/certbot
> # /etc/cron.d/certbot: crontab entries for the certbot package
> #
> # Upstream recommends attempting renewal twice a day
> #
> SHELL=/bin/sh
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>
> # -n for non-interactive
> 0 1 * * * root   service apache2 stop ;   perl -e 'sleep
> int(rand(3600))' &&  /usr/bin/certbot  certonly   --expand  -n   
> --standalone  --config  /etc/letsencrypt/cli.ini ;  service apache2 start

oops, a bad cut/paste

this looks like a better way, using pre/post hooks...
0 1 * * * root   perl -e 'sleep int(rand(3600))' && /usr/bin/certbot
certonly --expand -n --standalone --config /etc/letsencrypt/cli.ini
--pre-hook 'service apache2 stop' --post-hook 'service apache2 start'

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Joann Ransom
I totally love the Koha community including for reasons just like this.

J

On Wed, 6 Jun 2018, 16:52 Marc Véron,  wrote:

> Hi Liz
>
> Tanks a lot for funding the Koha community server for years.
>
> I will be happy to pay the server for this year ( $308 NZD ).
>
> Please send your banking information to me.
>
> Have a great day
>
> Marc
>
>
> Am 05.06.2018 um 23:21 schrieb Liz Rea:
> > Hi all,
> > I've been funding the koha-community web server for about 5 years now,
> and
> > I've been happy to have the disposable income available to me to do that
> > personally. As it turns out, this year I don't really have that and I
> could
> > really use some help paying for it.
> >
> > The server is paid for yearly, this year it was $308 NZD It's all paid up
> > until June of next year.
> >
> > If you'd be interested in tossing a few dollars my way to support running
> > the website, I'd be really grateful. I think it would be better to have a
> > community funded server anyway. I'm happy to keep looking after the
> server
> > and website too.
> >
> > I don't have a plan currently for how best to receive the funds - ideas
> > welcome on this front as well.
> >
> > Thanks for your consideration,
> >
> > Cheers,
> > Liz
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Michael Kuhn

Hi Liz

> The server is paid for yearly, this year it was $308 NZD It's all paid
> up until June of next year.
>
> If you'd be interested in tossing a few dollars my way to support
> running the website, I'd be really grateful. I think it would be
> better to have a community funded server anyway. I'm happy to keep
> looking after the server and website too.

I am willing to pay for that. Please send me the details (bank account etc).

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Marc Véron

Hi Liz

Tanks a lot for funding the Koha community server for years.

I will be happy to pay the server for this year ( $308 NZD ).

Please send your banking information to me.

Have a great day

Marc


Am 05.06.2018 um 23:21 schrieb Liz Rea:

Hi all,
I've been funding the koha-community web server for about 5 years now, and
I've been happy to have the disposable income available to me to do that
personally. As it turns out, this year I don't really have that and I could
really use some help paying for it.

The server is paid for yearly, this year it was $308 NZD It's all paid up
until June of next year.

If you'd be interested in tossing a few dollars my way to support running
the website, I'd be really grateful. I think it would be better to have a
community funded server anyway. I'm happy to keep looking after the server
and website too.

I don't have a plan currently for how best to receive the funds - ideas
welcome on this front as well.

Thanks for your consideration,

Cheers,
Liz
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] ssl for koha login

2018-06-05 Thread Mason James


On 6/06/18 3:45 pm, Mason James wrote:
>
> On 5/06/18 2:18 pm, Alvaro Cornejo wrote:
>> Hi
>>
>> I´m trying to setup a ssl connection to Koha  (using letsEncrypt certs ) so
>> my users, admin and opac can have a secure connection.
>>
>> I´ve folllowed letsEncrypt & certbot instrucctions but neither opac nor
>> admin pages work.
>>
>> I´ve tried directing connections manually and configuring apache for
>> redirect unsuccessfully.
>>
>> Any hints on this?
>>
>> This is mostly to avoid the upcoming chrome config where it will display an
>> unsafe site warning to any site requiring login that does not use ssl
>>
>> Regards,
>>
>> Alvaro
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
> hi Alvaro
>
> here's an apache config that has worked well for me
>
> it has some extra magic to improve it's SSL score
>
> the config now gets an 'A+' on the following site...
>  https://www.ssllabs.com/ssltest
>
> i'll aim to add this to the Koha wiki
>
> cheers, Mason
>
>

...and here's a nice 'cert renew' solution, using LE's cli.ini file


root@deb8:/# cat /etc/letsencrypt/cli.ini
domains = demo.foo.org, demo-admin.foo.org


root@deb8:/# cat /etc/cron.d/certbot
# /etc/cron.d/certbot: crontab entries for the certbot package
#
# Upstream recommends attempting renewal twice a day
#
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# -n for non-interactive
0 1 * * * root   service apache2 stop ;   perl -e 'sleep
int(rand(3600))' &&  /usr/bin/certbot  certonly   --expand  -n   
--standalone  --config  /etc/letsencrypt/cli.ini ;  service apache2 start


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] ssl for koha login

2018-06-05 Thread Mason James


On 5/06/18 2:18 pm, Alvaro Cornejo wrote:
> Hi
>
> I´m trying to setup a ssl connection to Koha  (using letsEncrypt certs ) so
> my users, admin and opac can have a secure connection.
>
> I´ve folllowed letsEncrypt & certbot instrucctions but neither opac nor
> admin pages work.
>
> I´ve tried directing connections manually and configuring apache for
> redirect unsuccessfully.
>
> Any hints on this?
>
> This is mostly to avoid the upcoming chrome config where it will display an
> unsafe site warning to any site requiring login that does not use ssl
>
> Regards,
>
> Alvaro
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

hi Alvaro

here's an apache config that has worked well for me

it has some extra magic to improve it's SSL score

the config now gets an 'A+' on the following site...
 https://www.ssllabs.com/ssltest

i'll aim to add this to the Koha wiki

cheers, Mason



root@deb8:/etc/apache2/sites-available# cat  demo.conf
# --
# OPAC


= 2.4>
   Define instance "demo"
  

   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
   Include /etc/koha/apache-shared-opac.conf

   ServerName demo.foo.org
  
   SetEnv KOHA_CONF "/etc/koha/sites/demo/koha-conf.xml"
   AssignUserID demo-koha demo-koha


  RewriteEngine On
  RewriteCond %{HTTPS} off
  RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

   ErrorLog    /var/log/koha/demo/opac-error.log
#  TransferLog /var/log/koha/demo/opac-access_log
#  RewriteLog  /var/log/koha/demo/opac-rewrite.log



# --


= 2.4>
   Define instance "demo"
  

   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
  Include /etc/koha/apache-shared-opac-plack.conf
   Include /etc/koha/apache-shared-opac.conf

   ServerName demo.foo.org
  
   SetEnv KOHA_CONF "/etc/koha/sites/demo/koha-conf.xml"
   AssignUserID demo-koha demo-koha

   ErrorLog    /var/log/koha/demo/opac-error.log
#  TransferLog /var/log/koha/demo/opac-access_log
#  RewriteLog  /var/log/koha/demo/opac-rewrite.log


# SSL config here!
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/demo.foo.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/demo.foo.org/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/demo.foo.org/fullchain.pem

 SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
 SSLProtocol All -SSLv2 -SSLv3
 SSLHonorCipherOrder On

 Header always set Strict-Transport-Security "max-age=1728; preload"
 Header always set Content-Security-Policy "upgrade-insecure-requests"



# --
# Intranet / redirect to https


= 2.4>
   Define instance "demo"
  

   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
   Include /etc/koha/apache-shared-intranet.conf

   ServerName demo-admin.foo.org

  RewriteEngine On
  RewriteCond %{HTTPS} off
  RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

   ErrorLog    /var/log/koha/demo/intranet-error.log
#  TransferLog /var/log/koha/demo/intranet-access_log
#  RewriteLog  /var/log/koha/demo/intranet-rewrite.log



# --


= 2.4>
   Define instance "demo"
  

   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
  Include /etc/koha/apache-shared-intranet-plack.conf
   Include /etc/koha/apache-shared-intranet.conf

   ServerName demo-admin.foo.org

   SetEnv KOHA_CONF "/etc/koha/sites/demo/koha-conf.xml"
   AssignUserID demo-koha demo-koha

   ErrorLog    /var/log/koha/demo/intranet-error.log
#  TransferLog /var/log/koha/demo/intranet-access_log
#  RewriteLog  /var/log/koha/demo/intranet-rewrite.log

# SSL config here!
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/demo.foo.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/demo.foo.org/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/demo.foo.org/fullchain.pem

 Header always set Strict-Transport-Security "max-age=1728; preload"
 Header always set Content-Security-Policy "upgrade-insecure-requests"



___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Search error

2018-06-05 Thread Paul Hoffman
On Tue, Jun 05, 2018 at 03:15:37PM +0530, Thirunagalingam S.S. wrote:
> We are from India. We are using 3.20.08.000 on Ubuntu server. We encounter
> the below mentioned error when we search the catalogue.
> 
> Software error:
> 
> Illegal division by zero at
> /usr/share/koha/intranet/cgi-bin/catalogue/search.pl line 631.
> 
> For help, please send mail to the webmaster ([no address given]), giving
> this error message and the time and date of the error.
> 
> 
> Need help urgently.

Can you please post the output of this command?

cat -n /usr/share/koha/intranet/cgi-bin/catalogue/search.pl | sed -n 620,642p

Thank you,

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Help with funding the koha-community.org webserver

2018-06-05 Thread Liz Rea
Hi all,
I've been funding the koha-community web server for about 5 years now, and
I've been happy to have the disposable income available to me to do that
personally. As it turns out, this year I don't really have that and I could
really use some help paying for it.

The server is paid for yearly, this year it was $308 NZD It's all paid up
until June of next year.

If you'd be interested in tossing a few dollars my way to support running
the website, I'd be really grateful. I think it would be better to have a
community funded server anyway. I'm happy to keep looking after the server
and website too.

I don't have a plan currently for how best to receive the funds - ideas
welcome on this front as well.

Thanks for your consideration,

Cheers,
Liz
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Framework warnings on upgrade to 18.05 (From 17.11.04)

2018-06-05 Thread Elaine Bradtke
I've  exported all the frameworks from production and imported them to
test.  Next step is to try the upgrade again to see if we get any warning
messages.

Elaine Bradtke
VWML
English Folk Dance and Song Society | http://www.efdss.org
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
---
"Writing about music is like dancing about architecture"
--Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)

On Mon, Jun 4, 2018 at 10:35 AM, Elaine Bradtke  wrote:

> Anyone?
>
> Elaine Bradtke
> VWML
> English Folk Dance and Song Society | http://www.efdss.org
> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
> Song Society in London, England. If you wish to phone me personally, send
> an e-mail first. I work off site)
> --
> Registered Company No. 297142
> Charity Registered in England and Wales No. 305999
> 
> ---
> "Writing about music is like dancing about architecture"
> --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
>
> On Thu, May 31, 2018 at 11:34 AM, Elaine Bradtke  wrote:
>
>> Background:  We have a test system that we run on a different server.
>> When we first installed Koha (3.?) many years ago, I managed to corrupt the
>> default framework.  I then overwrote the default framework with a clean one
>> in the production site.  We periodically clone the database from production
>> to the test site to keep it fairly current.  However, it appears that the
>> framework isn't being copied (otherwise, I don't know how to explain the
>> differences - the items in the list are not things we've changed, but may
>> have resulted when the framework was corrupted).
>>
>> Below is a message generated while upgrading the test site to 18.05.
>> Comparing this list to the production site, I find that the production site
>> is 'standard' and test site deviates from this.
>>
>> *Question 1:*  If I import the (standard) Default framework from
>> production and overwrite the one in test, will this correct the problem, or
>> do I need to import and overwrite all the frameworks? Do we need to do
>> anything with the system to implement the changes in the subsidiary
>> frameworks?
>>
>> *Question 2:* If you clone the database, does it not include the
>> frameworks? (warning, I'm not the one who does this task, so I don't fully
>> understand it). Is there something we need to do to make sure that it does
>> copy the frameworks?
>>
>> Here's the message from the test site:
>>
>> WARNING: The Default framework is now considered as authoritative for
>> Koha to MARC mappings. We have found that your additional frameworks
>> contained 43 mapping(s) that deviate from the standard mappings. Please
>> look at the following list and consider if you need to add them again in
>> Default (possibly as a second mapping).
>> Field 250$a in framework ART: Mapping to biblioitems.volume has been
>> adjusted.
>> Field 250$b in framework ART: Mapping to biblioitems.number has been
>> adjusted.
>> Field 490$a in framework ART: Mapping to biblio.seriestitle has been
>> adjusted.
>> Field 650$a in framework ART: Mapping has been reset.
>> Field 700$a in framework ART: Mapping has been reset.
>> Field 942$e in framework ART: Mapping has been reset.
>> Field 942$k in framework ART: Mapping has been reset.
>> Field 942$s in framework ART: Mapping has been reset.
>> Field 952$f in framework ART: Mapping has been reset.
>> Field 700$a in framework BKS: Mapping has been reset.
>> Field 942$e in framework BKS: Mapping has been reset.
>> Field 942$k in framework BKS: Mapping has been reset.
>> Field 650$a in framework CF: Mapping has been reset.
>> Field 942$e in framework CF: Mapping has been reset.
>> Field 942$k in framework CF: Mapping has been reset.
>> Field 245$b in framework FA: Mapping has been reset.
>> Field 952$x in framework FA: Mapping to items.paidfor has been adjusted.
>> Field 245$b in framework PRG: Mapping has been reset.
>> Field 650$a in framework PRG: Mapping has been reset.
>> Field 700$a in framework PRG: Mapping has been reset.
>> Field 774$w in framework PRG: Mapping to biblio.biblionumber has been
>> adjusted.
>> Field 942$e in framework PRG: Mapping has been reset.
>> Field 942$k in framework PRG: Mapping has been reset.
>> Field 952$f in framework PRG: Mapping has been reset.
>> Field 264$a in framework RDA: Mapping to biblioitems.place has been
>> adjusted.
>> Field 

Re: [Koha] ssl for koha login

2018-06-05 Thread Mark Alexander
Excerpts from Alvaro Cornejo's message of 2018-06-04 21:18:57 -0500:
> I´m trying to setup a ssl connection to Koha  (using letsEncrypt certs ) so
> my users, admin and opac can have a secure connection.
> 
> I´ve folllowed letsEncrypt & certbot instrucctions but neither opac nor
> admin pages work.

I used certbot on Debian 8 to get the OPAC and staff clients to use
SSL.  If I recall correctly, certbot attempted to modify my Apache
config file to add references to the LetsEncrypt certificate files,
but I think it chose the wrong file to modify.  So I hand-modified the
Koha-specific config file to point to the certificates.

Below is the resulting /etc/apache2/sites-available/LIB.conf.  Replace
LIB with the actual Koha instance name, and replace KOHA.MYLIBRARY.COM
with the actual hostname.  Note also that I chose port 81 for the OPAC
and port 82 for the staff client; you will probably need to change
those numbers.

# Koha instance LIB Apache config.

# OPAC

  = 2.4>
   Define instance "LIB"
  
   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
  Include /etc/koha/apache-shared-opac-plack.conf
   Include /etc/koha/apache-shared-opac.conf

   ServerName KOHA.MYLIBRARY.COM
   SetEnv KOHA_CONF "/etc/koha/sites/LIB/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
   SetEnv MEMCACHED_NAMESPACE "koha_LIB"
   AssignUserID LIB-koha LIB-koha

   ErrorLog/var/log/koha/LIB/opac-error.log
#  TransferLog /var/log/koha/LIB/opac-access.log
#  RewriteLog  /var/log/koha/LIB/opac-rewrite.log
SSLCertificateFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf


# Intranet

  = 2.4>
   Define instance "LIB"
  
   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
  Include /etc/koha/apache-shared-intranet-plack.conf
   Include /etc/koha/apache-shared-intranet.conf
   
   ServerName KOHA.MYLIBRARY.COM
   SetEnv KOHA_CONF "/etc/koha/sites/LIB/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
   SetEnv MEMCACHED_NAMESPACE "koha_LIB"
   AssignUserID LIB-koha LIB-koha

   ErrorLog/var/log/koha/LIB/intranet-error.log
#  TransferLog /var/log/koha/LIB/intranet-access.log
#  RewriteLog  /var/log/koha/LIB/intranet-rewrite.log
SSLCertificateFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Search error

2018-06-05 Thread Thirunagalingam S.S.
Hi,

We are from India. We are using 3.20.08.000 on Ubuntu server. We encounter
the below mentioned error when we search the catalogue.

Software error:

Illegal division by zero at
/usr/share/koha/intranet/cgi-bin/catalogue/search.pl line 631.

For help, please send mail to the webmaster ([no address given]), giving
this error message and the time and date of the error.


Need help urgently.


SIDO
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha