Re: [Koha] Bulk Patron Image upload zip file giving Error 500

[Sunil Sharma]

Hi Marc,

Thanks for the valuable input.

Let me debug these lines which you had point out and get back to you if I
will get any solution with this.



On Fri, Jul 21, 2017 at 12:33 PM, Marc Véron  wrote:

> Hi Sunil
>
> I have the impression that the error occurs on line 118 of
> picture-upload.pl
>
> unless( system( "unzip", $tempfile, '-d', $dirname ) == 0 ) {
>
> It seems that the zip is extracted but the program thinks that something
> went wrong with extracting and exits (following lines).
>
> Because the error occurs since Debian 8.3 I suppose that system(...)
> returns an other value than with Debian 8.2
>
> For the return values of system see:
> http://perldoc.perl.org/functions/system.html
>
> Just my 2 cents...
>
> Marc
>
>
> Am 21.07.2017 um 06:29 schrieb Sunil Sharma:
>
>> Hello Friends,
>>
>> If someone faced the problem mentioned in my previous mail attached below
>> and having any solution, please guide.
>>
>> I am using Koha 16.05.12 with Debian 8.3 OS on my cloud server.
>>
>> Currently, I am facing a very strange problem while uploading a single
>> patron image via Koha Bulk Patron image upload tool, the image file is
>> uploading fine. But When I tried using *zip file* of all patron images
>> with
>> a mapped text file named as IDLINK.TXT, As soon as I browse the zip file
>> and try to upload the images, the images are uploaded but instead of
>> result
>> page, the page will through error 500.
>>
>> I had checked many Koha versions i.e. Koha 3.22.x, Koha 16.05.x, Koha
>> 16.11.x but same *error 500* will be the result.
>>
>> To troubleshoot the problem I had tested the same Koha versions with same
>> zip file at my local virtual machine but the strange problem which I
>> found,
>> that* all Koha* versions with bulk patron upload feature *worked fine on
>> Debian 8.2 *but *through error 500 with Debian 8.3 and onwards i.e. 8.4,
>> 8.8 etc. *
>>
>>
>> I had tested with different Apache versions but on Debian 8.2 all things
>> worked fine, but on Debian 8.3 no success (may be any security fetch or
>> something wrong is there)
>>
>> As there are a lot of other application are running on my cloud server so
>> I
>> can't change the OS. Please guide me what will I do?
>>
>> The Koha error logs are as given below:
>>
>>
>>
>>
>>
>> *[Thu Jul 12 13:43:02.2017] [http:error] [pid 16357] [client x.x.x.x]
>> AH02429: Response header name ' extracting' contains invalid characters,
>> aborting request, referer:
>> http://example.com/cgi-bin/koha/tools/picture-upload.pl
>> [Thu Jul 12
>> 13:50:38.2017] [http:error] [pid 14327] [client x.x.x.x] AH02429: Response
>> header name '  inflating' contains invalid characters, aborting request,
>> referer: http://example.com/cgi-bin/koha/tools/picture-upload.pl
>> [Thu Jul 12
>> 13:59:27.2017] [http:error] [pid 25507] [client x.x.x.x] AH02429: Response
>> header name '  inflating' contains invalid characters, aborting request,
>> referer: http://example.com/cgi-bin/koha/tools/picture-upload.pl
>> *
>>
>>
>> Any pointers would be of help.
>>
>>
>> On Fri, Jul 14, 2017 at 3:19 PM, Sunil Sharma 
>> wrote:
>>
>> Hi Ian Bays,
>>>
>>> Thank you very much for the valuable input.
>>>
>>> I had checked and you are right that all patron images are uploading
>>> correctly but was failing when trying to show the results page with the
>>> error 500 as you observed.
>>>
>>> Now, it is confirmed with your mail that something is wrong. Please guide
>>> if you will find any solution for this problem.
>>>
>>> If someone else faced this problem and having solution, please guide.
>>>
>>>
>>>
>>> On Fri, Jul 14, 2017 at 2:19 PM, Ian Bays 
>>> wrote:
>>>
>>> Hello,

 I have noticed the same problem uploading a zip file of patron images
 and
 saw similar messages in the log file.

 However on checking the patron records saw the images so I concluded
 that
 the upload was working correctly but was failing when trying to show the
 results page with the error 500.

 There is definitely something wrong but you might like to check to see
 if
 the upload actually worked OK.

 Best regards.
 Ian

 On 13/07/2017 06:32, Sunil Sharma wrote:

 Hello Friends,
>
> I am using Koha 16.05.12 with Debian 8.3 OS on my cloud server.
>
> Currently, I am facing a very strange problem while uploading a single
> patron image via Koha Bulk Patron image upload tool, the image file is
> uploading fine. But When I tried using *zip file* of all patron images
> with
> a mapped text file named as IDLINK.TXT, As soon as I browse the zip
> file
> and try to upload the file, the page will through error 500.
>
> I had checked many Koha versions i.e. Koha 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Liz Rea]

Hi,

There is currently a bug in Koha where it looks like the DB password is
being rejected, but if you click "[main page]" below the login form, you
are logged in. It's worth checking that you're not coming up against
this bug.

Cheers,
Liz


On 26/07/17 13:24, Jonathan Druart wrote:
> The credentials are in the config section, close to the database entry, not
> in the serverinfo section. The username must be something like
> 'koha_library' (if you created it using koha-create).
>
> On Tue, 25 Jul 2017 at 20:42 C.J.S. Hayward  wrote:
>
>> I think my installation is corrupt.
>>
>> (koha-password displayed a password, but it didn't work for logging in as
>> kohauser either.)
>>
>> I want to uninstall and reinstall. Any words of advice besides being
>> meticulous about the wiki instructions?
>>
>>
>> Thanks
>>
>> On Tue, Jul 25, 2017 at 6:03 PM, Jonathan Druart <
>> jonathan.dru...@bugs.koha-community.org> wrote:
>>
>>> You should not modify it, you can know the password of the database user
>>> using `sudo koha-passwd kohadev`, but the command will return the same
>>> value as the xml config file.
>>> Try to connect to mysql using `mysql -u koha_library -p` and enter the
>>> password.
>>> If it is rejected, you did something wrong when you create the instance.
>>> If
>>> it is not rejected it should not be rejected from the interface either.
>>>
>>> On Tue, 25 Jul 2017 at 19:38 C.J.S. Hayward  wrote:
>>>
 My suspicion is that you already had Listen lines predefined and you
 double-punched on at least one port.

 I moved all Listen lines to ports.conf, removing them from the sites,
>>> and
 maintaining only one Listen line per port. The behavior is, so far as I
>>> can
 tell, identical. The .../library/koha-conf.xml credentials are rejected
 every single time.

 Is there a command line way (bash or mysql) to set the password for
 kohauser?


 Thanks,

 On Tue, Jul 25, 2017 at 5:18 PM, Jonathan Druart <
 jonathan.dru...@bugs.koha-community.org> wrote:

> I tried to add the "Listen" lines and it breaks everything for me.
> What is the behaviour if you remove them? Do you access the staff
> interface
> (login form) or the opac interface (maintenance screen)?
>
> On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward 
>>> wrote:
>> Ok; I can clean that up.
>>
>> But let me see if the same symptoms appear next time I work on it; my
>> expectation is that the behavior is identical (i.e. I am not able to
> log in
>> through the web interface with credentials in library/koha-conf.xml),
> even
>> if I should move the Listen lines.
>>
>>
>> Thanks,
>>
>> On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart <
>> jonathan.dru...@bugs.koha-community.org> wrote:
>>
>>> I think the 2 "Listen" lines should go to ports.conf
>>>
>>> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward 
> wrote:
 Thank you. This server is multipurpose and has multiple webapps
>>> that
 listen on 8080 by default. My library entry in
>>> /etc/apache2/sites-enables
 reads, with /etc/hosts assigning "opac" and "library" to
>>> 127.0.0.1:
 # Koha instance library Apache config.

 # OPAC

 Listen 7027
 
   = 2.4>
Define instance "library"
   
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 opac
SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
AssignUserID library-koha library-koha

ErrorLog/var/log/koha/library/opac-error.log
 #  TransferLog /var/log/koha/library/opac-access.log
 #  RewriteLog  /var/log/koha/library/opac-rewrite.log
 

 # Intranet
 Listen 7028
 
   = 2.4>
Define instance "library"
   
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 intranet
SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
AssignUserID library-koha library-koha

ErrorLog/var/log/koha/library/intranet-error.log
 #  TransferLog /var/log/koha/library/intranet-access.log
 #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
 
 ~


 I had earlier tried to access opac:7027 and got the reported
>>> error.
> Now
>>> I
 am trying to access intranet:7028 and I can't tell a 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Jonathan Druart]

The credentials are in the config section, close to the database entry, not
in the serverinfo section. The username must be something like
'koha_library' (if you created it using koha-create).

On Tue, 25 Jul 2017 at 20:42 C.J.S. Hayward  wrote:

> I think my installation is corrupt.
>
> (koha-password displayed a password, but it didn't work for logging in as
> kohauser either.)
>
> I want to uninstall and reinstall. Any words of advice besides being
> meticulous about the wiki instructions?
>
>
> Thanks
>
> On Tue, Jul 25, 2017 at 6:03 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> You should not modify it, you can know the password of the database user
>> using `sudo koha-passwd kohadev`, but the command will return the same
>> value as the xml config file.
>> Try to connect to mysql using `mysql -u koha_library -p` and enter the
>> password.
>> If it is rejected, you did something wrong when you create the instance.
>> If
>> it is not rejected it should not be rejected from the interface either.
>>
>> On Tue, 25 Jul 2017 at 19:38 C.J.S. Hayward  wrote:
>>
>> > My suspicion is that you already had Listen lines predefined and you
>> > double-punched on at least one port.
>> >
>> > I moved all Listen lines to ports.conf, removing them from the sites,
>> and
>> > maintaining only one Listen line per port. The behavior is, so far as I
>> can
>> > tell, identical. The .../library/koha-conf.xml credentials are rejected
>> > every single time.
>> >
>> > Is there a command line way (bash or mysql) to set the password for
>> > kohauser?
>> >
>> >
>> > Thanks,
>> >
>> > On Tue, Jul 25, 2017 at 5:18 PM, Jonathan Druart <
>> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >
>> >> I tried to add the "Listen" lines and it breaks everything for me.
>> >> What is the behaviour if you remove them? Do you access the staff
>> >> interface
>> >> (login form) or the opac interface (maintenance screen)?
>> >>
>> >> On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward 
>> wrote:
>> >>
>> >> > Ok; I can clean that up.
>> >> >
>> >> > But let me see if the same symptoms appear next time I work on it; my
>> >> > expectation is that the behavior is identical (i.e. I am not able to
>> >> log in
>> >> > through the web interface with credentials in library/koha-conf.xml),
>> >> even
>> >> > if I should move the Listen lines.
>> >> >
>> >> >
>> >> > Thanks,
>> >> >
>> >> > On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart <
>> >> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >> >
>> >> >> I think the 2 "Listen" lines should go to ports.conf
>> >> >>
>> >> >> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward 
>> >> wrote:
>> >> >>
>> >> >> > Thank you. This server is multipurpose and has multiple webapps
>> that
>> >> >> > listen on 8080 by default. My library entry in
>> >> >> /etc/apache2/sites-enables
>> >> >> > reads, with /etc/hosts assigning "opac" and "library" to
>> 127.0.0.1:
>> >> >> >
>> >> >> > # Koha instance library Apache config.
>> >> >> >
>> >> >> > # OPAC
>> >> >> >
>> >> >> > Listen 7027
>> >> >> > 
>> >> >> >   = 2.4>
>> >> >> >Define instance "library"
>> >> >> >   
>> >> >> >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 opac
>> >> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>> >> >> >AssignUserID library-koha library-koha
>> >> >> >
>> >> >> >ErrorLog/var/log/koha/library/opac-error.log
>> >> >> > #  TransferLog /var/log/koha/library/opac-access.log
>> >> >> > #  RewriteLog  /var/log/koha/library/opac-rewrite.log
>> >> >> > 
>> >> >> >
>> >> >> > # Intranet
>> >> >> > Listen 7028
>> >> >> > 
>> >> >> >   = 2.4>
>> >> >> >Define instance "library"
>> >> >> >   
>> >> >> >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 intranet
>> >> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>> >> >> >AssignUserID library-koha library-koha
>> >> >> >
>> >> >> >ErrorLog/var/log/koha/library/intranet-error.log
>> >> >> > #  TransferLog /var/log/koha/library/intranet-access.log
>> >> >> > #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
>> >> >> > 
>> >> >> > ~
>> >> >> >
>> >> >> >
>> >> >> > I had earlier tried to access opac:7027 and got the reported
>> error.
>> >> Now
>> >> >> I
>> >> >> > am trying to access intranet:7028 and I can't tell a difference.
>> >> >> >
>> >> >> > Do I need to be doing more if I reassign port numbers?
>> >> >> >
>> >> >> >
>> >> >> > Thanks,
>>
>
___

Re: [Koha] [Koha-devel] Reminder: dev meetings are essential

[David Cook]

Hi Jonathan,

 

For me, it’s just a matter of timetable. I have a toddler, so dev meetings 
outside of my work day are impossible. 

 

But… I don’t think there are many Australians with the same limitations as me, 
and I don’t think we have many active East Asian devs in the same timezone, so 
I’m mostly resigned to never attending dev meetings.  

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: koha-devel-boun...@lists.koha-community.org 
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Jonathan 
Druart
Sent: Wednesday, 26 July 2017 7:17 AM
To: koha@lists.katipo.co.nz; koha-de...@lists.koha-community.org
Subject: [Koha-devel] Reminder: dev meetings are essential

 

Hello everybody,

To me, when someone never attends any dev meetings it means:

- they do not have specific needs/priorities

- they do not have any opinions on how the development team is prioritizing / 
organising the next developments

- they do not want to get involved in the technical decisions


Is that true for you as well?
Or is it just a matter of timetable? In that case let me know and we will try 
to find a solution.

 

Cheers,

Jonathan

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

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

I think my installation is corrupt.

(koha-password displayed a password, but it didn't work for logging in as
kohauser either.)

I want to uninstall and reinstall. Any words of advice besides being
meticulous about the wiki instructions?


Thanks

On Tue, Jul 25, 2017 at 6:03 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> You should not modify it, you can know the password of the database user
> using `sudo koha-passwd kohadev`, but the command will return the same
> value as the xml config file.
> Try to connect to mysql using `mysql -u koha_library -p` and enter the
> password.
> If it is rejected, you did something wrong when you create the instance. If
> it is not rejected it should not be rejected from the interface either.
>
> On Tue, 25 Jul 2017 at 19:38 C.J.S. Hayward  wrote:
>
> > My suspicion is that you already had Listen lines predefined and you
> > double-punched on at least one port.
> >
> > I moved all Listen lines to ports.conf, removing them from the sites, and
> > maintaining only one Listen line per port. The behavior is, so far as I
> can
> > tell, identical. The .../library/koha-conf.xml credentials are rejected
> > every single time.
> >
> > Is there a command line way (bash or mysql) to set the password for
> > kohauser?
> >
> >
> > Thanks,
> >
> > On Tue, Jul 25, 2017 at 5:18 PM, Jonathan Druart <
> > jonathan.dru...@bugs.koha-community.org> wrote:
> >
> >> I tried to add the "Listen" lines and it breaks everything for me.
> >> What is the behaviour if you remove them? Do you access the staff
> >> interface
> >> (login form) or the opac interface (maintenance screen)?
> >>
> >> On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward 
> wrote:
> >>
> >> > Ok; I can clean that up.
> >> >
> >> > But let me see if the same symptoms appear next time I work on it; my
> >> > expectation is that the behavior is identical (i.e. I am not able to
> >> log in
> >> > through the web interface with credentials in library/koha-conf.xml),
> >> even
> >> > if I should move the Listen lines.
> >> >
> >> >
> >> > Thanks,
> >> >
> >> > On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart <
> >> > jonathan.dru...@bugs.koha-community.org> wrote:
> >> >
> >> >> I think the 2 "Listen" lines should go to ports.conf
> >> >>
> >> >> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward 
> >> wrote:
> >> >>
> >> >> > Thank you. This server is multipurpose and has multiple webapps
> that
> >> >> > listen on 8080 by default. My library entry in
> >> >> /etc/apache2/sites-enables
> >> >> > reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1
> :
> >> >> >
> >> >> > # Koha instance library Apache config.
> >> >> >
> >> >> > # OPAC
> >> >> >
> >> >> > Listen 7027
> >> >> > 
> >> >> >   = 2.4>
> >> >> >Define instance "library"
> >> >> >   
> >> >> >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 opac
> >> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
> >> >> >AssignUserID library-koha library-koha
> >> >> >
> >> >> >ErrorLog/var/log/koha/library/opac-error.log
> >> >> > #  TransferLog /var/log/koha/library/opac-access.log
> >> >> > #  RewriteLog  /var/log/koha/library/opac-rewrite.log
> >> >> > 
> >> >> >
> >> >> > # Intranet
> >> >> > Listen 7028
> >> >> > 
> >> >> >   = 2.4>
> >> >> >Define instance "library"
> >> >> >   
> >> >> >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 intranet
> >> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
> >> >> >AssignUserID library-koha library-koha
> >> >> >
> >> >> >ErrorLog/var/log/koha/library/intranet-error.log
> >> >> > #  TransferLog /var/log/koha/library/intranet-access.log
> >> >> > #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
> >> >> > 
> >> >> > ~
> >> >> >
> >> >> >
> >> >> > I had earlier tried to access opac:7027 and got the reported error.
> >> Now
> >> >> I
> >> >> > am trying to access intranet:7028 and I can't tell a difference.
> >> >> >
> >> >> > Do I need to be doing more if I reassign port numbers?
> >> >> >
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> >
> >> >> > On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
> >> >> > jonathan.dru...@bugs.koha-community.org> wrote:
> >> >> >
> >> >> >> If you reach the "system maintenance" screen that means you are
> >> hitting
> >> >> >> the
> >> >> >> OPAC interface, not the staff interface.
> >> >> >> Try on :8080
> >> >> >>
> >> >> >> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward 
> >> >> wrote:
> >> >> >>
> >> >> >> > Let me send 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Jonathan Druart]

You should not modify it, you can know the password of the database user
using `sudo koha-passwd kohadev`, but the command will return the same
value as the xml config file.
Try to connect to mysql using `mysql -u koha_library -p` and enter the
password.
If it is rejected, you did something wrong when you create the instance. If
it is not rejected it should not be rejected from the interface either.

On Tue, 25 Jul 2017 at 19:38 C.J.S. Hayward  wrote:

> My suspicion is that you already had Listen lines predefined and you
> double-punched on at least one port.
>
> I moved all Listen lines to ports.conf, removing them from the sites, and
> maintaining only one Listen line per port. The behavior is, so far as I can
> tell, identical. The .../library/koha-conf.xml credentials are rejected
> every single time.
>
> Is there a command line way (bash or mysql) to set the password for
> kohauser?
>
>
> Thanks,
>
> On Tue, Jul 25, 2017 at 5:18 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> I tried to add the "Listen" lines and it breaks everything for me.
>> What is the behaviour if you remove them? Do you access the staff
>> interface
>> (login form) or the opac interface (maintenance screen)?
>>
>> On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward  wrote:
>>
>> > Ok; I can clean that up.
>> >
>> > But let me see if the same symptoms appear next time I work on it; my
>> > expectation is that the behavior is identical (i.e. I am not able to
>> log in
>> > through the web interface with credentials in library/koha-conf.xml),
>> even
>> > if I should move the Listen lines.
>> >
>> >
>> > Thanks,
>> >
>> > On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart <
>> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >
>> >> I think the 2 "Listen" lines should go to ports.conf
>> >>
>> >> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward 
>> wrote:
>> >>
>> >> > Thank you. This server is multipurpose and has multiple webapps that
>> >> > listen on 8080 by default. My library entry in
>> >> /etc/apache2/sites-enables
>> >> > reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1:
>> >> >
>> >> > # Koha instance library Apache config.
>> >> >
>> >> > # OPAC
>> >> >
>> >> > Listen 7027
>> >> > 
>> >> >   = 2.4>
>> >> >Define instance "library"
>> >> >   
>> >> >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 opac
>> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>> >> >AssignUserID library-koha library-koha
>> >> >
>> >> >ErrorLog/var/log/koha/library/opac-error.log
>> >> > #  TransferLog /var/log/koha/library/opac-access.log
>> >> > #  RewriteLog  /var/log/koha/library/opac-rewrite.log
>> >> > 
>> >> >
>> >> > # Intranet
>> >> > Listen 7028
>> >> > 
>> >> >   = 2.4>
>> >> >Define instance "library"
>> >> >   
>> >> >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 intranet
>> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>> >> >AssignUserID library-koha library-koha
>> >> >
>> >> >ErrorLog/var/log/koha/library/intranet-error.log
>> >> > #  TransferLog /var/log/koha/library/intranet-access.log
>> >> > #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
>> >> > 
>> >> > ~
>> >> >
>> >> >
>> >> > I had earlier tried to access opac:7027 and got the reported error.
>> Now
>> >> I
>> >> > am trying to access intranet:7028 and I can't tell a difference.
>> >> >
>> >> > Do I need to be doing more if I reassign port numbers?
>> >> >
>> >> >
>> >> > Thanks,
>> >> >
>> >> >
>> >> > On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
>> >> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >> >
>> >> >> If you reach the "system maintenance" screen that means you are
>> hitting
>> >> >> the
>> >> >> OPAC interface, not the staff interface.
>> >> >> Try on :8080
>> >> >>
>> >> >> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward 
>> >> wrote:
>> >> >>
>> >> >> > Let me send off this email, and I'll report a bug.
>> >> >> >
>> >> >> > N.B. Koha is installed in some sense, but when I try to access the
>> >> >> > webinstaller I got maintenance mode:
>> >> >> >
>> >> >> > System Maintenance
>> >> >> >
>> >> >> > The Koha online catalog is offline for system maintenance. We'll
>> be
>> >> back
>> >> >> > soon! If you have any questions, please contact the site
>> >> administrator
>> >> >> >
>> >> >> > A brief search turned up
>> >> >> > https://lists.katipo.co.nz/public/koha/2013-December/038208.html
>> >> which
>> >> >> > picked up in a possible email typo specifying a port as 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

My suspicion is that you already had Listen lines predefined and you
double-punched on at least one port.

I moved all Listen lines to ports.conf, removing them from the sites, and
maintaining only one Listen line per port. The behavior is, so far as I can
tell, identical. The .../library/koha-conf.xml credentials are rejected
every single time.

Is there a command line way (bash or mysql) to set the password for
kohauser?


Thanks,

On Tue, Jul 25, 2017 at 5:18 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> I tried to add the "Listen" lines and it breaks everything for me.
> What is the behaviour if you remove them? Do you access the staff interface
> (login form) or the opac interface (maintenance screen)?
>
> On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward  wrote:
>
> > Ok; I can clean that up.
> >
> > But let me see if the same symptoms appear next time I work on it; my
> > expectation is that the behavior is identical (i.e. I am not able to log
> in
> > through the web interface with credentials in library/koha-conf.xml),
> even
> > if I should move the Listen lines.
> >
> >
> > Thanks,
> >
> > On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart <
> > jonathan.dru...@bugs.koha-community.org> wrote:
> >
> >> I think the 2 "Listen" lines should go to ports.conf
> >>
> >> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward 
> wrote:
> >>
> >> > Thank you. This server is multipurpose and has multiple webapps that
> >> > listen on 8080 by default. My library entry in
> >> /etc/apache2/sites-enables
> >> > reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1:
> >> >
> >> > # Koha instance library Apache config.
> >> >
> >> > # OPAC
> >> >
> >> > Listen 7027
> >> > 
> >> >   = 2.4>
> >> >Define instance "library"
> >> >   
> >> >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 opac
> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
> >> >AssignUserID library-koha library-koha
> >> >
> >> >ErrorLog/var/log/koha/library/opac-error.log
> >> > #  TransferLog /var/log/koha/library/opac-access.log
> >> > #  RewriteLog  /var/log/koha/library/opac-rewrite.log
> >> > 
> >> >
> >> > # Intranet
> >> > Listen 7028
> >> > 
> >> >   = 2.4>
> >> >Define instance "library"
> >> >   
> >> >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 intranet
> >> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
> >> >AssignUserID library-koha library-koha
> >> >
> >> >ErrorLog/var/log/koha/library/intranet-error.log
> >> > #  TransferLog /var/log/koha/library/intranet-access.log
> >> > #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
> >> > 
> >> > ~
> >> >
> >> >
> >> > I had earlier tried to access opac:7027 and got the reported error.
> Now
> >> I
> >> > am trying to access intranet:7028 and I can't tell a difference.
> >> >
> >> > Do I need to be doing more if I reassign port numbers?
> >> >
> >> >
> >> > Thanks,
> >> >
> >> >
> >> > On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
> >> > jonathan.dru...@bugs.koha-community.org> wrote:
> >> >
> >> >> If you reach the "system maintenance" screen that means you are
> hitting
> >> >> the
> >> >> OPAC interface, not the staff interface.
> >> >> Try on :8080
> >> >>
> >> >> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward 
> >> wrote:
> >> >>
> >> >> > Let me send off this email, and I'll report a bug.
> >> >> >
> >> >> > N.B. Koha is installed in some sense, but when I try to access the
> >> >> > webinstaller I got maintenance mode:
> >> >> >
> >> >> > System Maintenance
> >> >> >
> >> >> > The Koha online catalog is offline for system maintenance. We'll be
> >> back
> >> >> > soon! If you have any questions, please contact the site
> >> administrator
> >> >> >
> >> >> > A brief search turned up
> >> >> > https://lists.katipo.co.nz/public/koha/2013-December/038208.html
> >> which
> >> >> > picked up in a possible email typo specifying a port as 8008. This
> >> >> > suggestion appears to be irrelevant because if the OP had tried to
> >> >> access
> >> >> > Koha on 8008 and hadn't added anything else listening on that port,
> >> the
> >> >> > error would be "Connection refused", not "System maintenance".
> >> >> >
> >> >> > On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
> >> >> > jonathan.dru...@bugs.koha-community.org> wrote:
> >> >> >
> >> >> >> Try with --create-db:
> >> >> >>   koha-create --create-db library
> >> >> >>
> >> >> >> The doc says that --create-db is the default value, but it does
> not
> >> >> seem
> >> >> >> to
> >> >> >> work.
> >> >> >> 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Jonathan Druart]

I tried to add the "Listen" lines and it breaks everything for me.
What is the behaviour if you remove them? Do you access the staff interface
(login form) or the opac interface (maintenance screen)?

On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward  wrote:

> Ok; I can clean that up.
>
> But let me see if the same symptoms appear next time I work on it; my
> expectation is that the behavior is identical (i.e. I am not able to log in
> through the web interface with credentials in library/koha-conf.xml), even
> if I should move the Listen lines.
>
>
> Thanks,
>
> On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> I think the 2 "Listen" lines should go to ports.conf
>>
>> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward  wrote:
>>
>> > Thank you. This server is multipurpose and has multiple webapps that
>> > listen on 8080 by default. My library entry in
>> /etc/apache2/sites-enables
>> > reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1:
>> >
>> > # Koha instance library Apache config.
>> >
>> > # OPAC
>> >
>> > Listen 7027
>> > 
>> >   = 2.4>
>> >Define instance "library"
>> >   
>> >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 opac
>> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>> >AssignUserID library-koha library-koha
>> >
>> >ErrorLog/var/log/koha/library/opac-error.log
>> > #  TransferLog /var/log/koha/library/opac-access.log
>> > #  RewriteLog  /var/log/koha/library/opac-rewrite.log
>> > 
>> >
>> > # Intranet
>> > Listen 7028
>> > 
>> >   = 2.4>
>> >Define instance "library"
>> >   
>> >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 intranet
>> >SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>> >AssignUserID library-koha library-koha
>> >
>> >ErrorLog/var/log/koha/library/intranet-error.log
>> > #  TransferLog /var/log/koha/library/intranet-access.log
>> > #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
>> > 
>> > ~
>> >
>> >
>> > I had earlier tried to access opac:7027 and got the reported error. Now
>> I
>> > am trying to access intranet:7028 and I can't tell a difference.
>> >
>> > Do I need to be doing more if I reassign port numbers?
>> >
>> >
>> > Thanks,
>> >
>> >
>> > On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
>> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >
>> >> If you reach the "system maintenance" screen that means you are hitting
>> >> the
>> >> OPAC interface, not the staff interface.
>> >> Try on :8080
>> >>
>> >> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward 
>> wrote:
>> >>
>> >> > Let me send off this email, and I'll report a bug.
>> >> >
>> >> > N.B. Koha is installed in some sense, but when I try to access the
>> >> > webinstaller I got maintenance mode:
>> >> >
>> >> > System Maintenance
>> >> >
>> >> > The Koha online catalog is offline for system maintenance. We'll be
>> back
>> >> > soon! If you have any questions, please contact the site
>> administrator
>> >> >
>> >> > A brief search turned up
>> >> > https://lists.katipo.co.nz/public/koha/2013-December/038208.html
>> which
>> >> > picked up in a possible email typo specifying a port as 8008. This
>> >> > suggestion appears to be irrelevant because if the OP had tried to
>> >> access
>> >> > Koha on 8008 and hadn't added anything else listening on that port,
>> the
>> >> > error would be "Connection refused", not "System maintenance".
>> >> >
>> >> > On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
>> >> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >> >
>> >> >> Try with --create-db:
>> >> >>   koha-create --create-db library
>> >> >>
>> >> >> The doc says that --create-db is the default value, but it does not
>> >> seem
>> >> >> to
>> >> >> work.
>> >> >> Could you report the bug?
>> >> >>
>> >> >> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward 
>> >> wrote:
>> >> >>
>> >> >> > Thank you. I've used koha-remove, and uninstalled and reinstalled
>> >> >> > koha-common, including setting an a2enmod.
>> >> >> >
>> >> >> > Right now I have an /etc/koha heirarchy that has a lot of stuff in
>> >> it,
>> >> >> but
>> >> >> > /etc/koha/sites is an empty directory *after* trying to run
>> >> "koha-create
>> >> >> > library":
>> >> >> >
>> >> >> > toolchest sites # koha-create library
>> >> >> > failed to load external entity
>> >> "/etc/koha/sites/library/koha-conf.xml"
>> >> >> >
>> >> >> > How can I create or get an appropriate koha-conf.xml? I notice
>> that
>> >> >> there
>> >> >> > is an /etc/koha/koha-conf-site.xml.in; what can or 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Jonathan Druart]

I think the 2 "Listen" lines should go to ports.conf

On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward  wrote:

> Thank you. This server is multipurpose and has multiple webapps that
> listen on 8080 by default. My library entry in /etc/apache2/sites-enables
> reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1:
>
> # Koha instance library Apache config.
>
> # OPAC
>
> Listen 7027
> 
>   = 2.4>
>Define instance "library"
>   
>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 opac
>SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>AssignUserID library-koha library-koha
>
>ErrorLog/var/log/koha/library/opac-error.log
> #  TransferLog /var/log/koha/library/opac-access.log
> #  RewriteLog  /var/log/koha/library/opac-rewrite.log
> 
>
> # Intranet
> Listen 7028
> 
>   = 2.4>
>Define instance "library"
>   
>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 intranet
>SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>AssignUserID library-koha library-koha
>
>ErrorLog/var/log/koha/library/intranet-error.log
> #  TransferLog /var/log/koha/library/intranet-access.log
> #  RewriteLog  /var/log/koha/library/intranet-rewrite.log
> 
> ~
>
>
> I had earlier tried to access opac:7027 and got the reported error. Now I
> am trying to access intranet:7028 and I can't tell a difference.
>
> Do I need to be doing more if I reassign port numbers?
>
>
> Thanks,
>
>
> On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> If you reach the "system maintenance" screen that means you are hitting
>> the
>> OPAC interface, not the staff interface.
>> Try on :8080
>>
>> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward  wrote:
>>
>> > Let me send off this email, and I'll report a bug.
>> >
>> > N.B. Koha is installed in some sense, but when I try to access the
>> > webinstaller I got maintenance mode:
>> >
>> > System Maintenance
>> >
>> > The Koha online catalog is offline for system maintenance. We'll be back
>> > soon! If you have any questions, please contact the site administrator
>> >
>> > A brief search turned up
>> > https://lists.katipo.co.nz/public/koha/2013-December/038208.html which
>> > picked up in a possible email typo specifying a port as 8008. This
>> > suggestion appears to be irrelevant because if the OP had tried to
>> access
>> > Koha on 8008 and hadn't added anything else listening on that port, the
>> > error would be "Connection refused", not "System maintenance".
>> >
>> > On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
>> > jonathan.dru...@bugs.koha-community.org> wrote:
>> >
>> >> Try with --create-db:
>> >>   koha-create --create-db library
>> >>
>> >> The doc says that --create-db is the default value, but it does not
>> seem
>> >> to
>> >> work.
>> >> Could you report the bug?
>> >>
>> >> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward 
>> wrote:
>> >>
>> >> > Thank you. I've used koha-remove, and uninstalled and reinstalled
>> >> > koha-common, including setting an a2enmod.
>> >> >
>> >> > Right now I have an /etc/koha heirarchy that has a lot of stuff in
>> it,
>> >> but
>> >> > /etc/koha/sites is an empty directory *after* trying to run
>> "koha-create
>> >> > library":
>> >> >
>> >> > toolchest sites # koha-create library
>> >> > failed to load external entity
>> "/etc/koha/sites/library/koha-conf.xml"
>> >> >
>> >> > How can I create or get an appropriate koha-conf.xml? I notice that
>> >> there
>> >> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be
>> doing to
>> >> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml
>> (and
>> >> > anything else that should be in /etc/koha/sites/library/)?
>> >> >
>> >> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden 
>> >> wrote:
>> >> >
>> >> > > If you installed using the packages I believe you can use
>> koha-remove
>> >> .
>> >> > > See here:
>> https://wiki.koha-community.org/wiki/Commands_provided_by_
>> >> > > the_Debian_packages#koha-remove
>> >> > >
>> >> > > Doug
>> >> > >
>> >> > > -Original Message-
>> >> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
>> >> C.J.S.
>> >> > > Hayward
>> >> > > Sent: Tuesday, July 25, 2017 11:18 AM
>> >> > > To: koha@lists.katipo.co.nz
>> >> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
>> >> > > installing stable under Mint
>> >> > >
>> >> > > I have a virtual machine that may have two conflicting Koha
>> >> > installations.
>> >> > >
>> >> > > What, if anything, can I do that will wipe all Koha installations
>> >> > > 

[Koha] Reminder: dev meetings are essential

[Jonathan Druart]

Hello everybody,

To me, when someone never attends any dev meetings it means:
- they do not have specific needs/priorities
- they do not have any opinions on how the development team is prioritizing
/ organising the next developments
- they do not want to get involved in the technical decisions

Is that true for you as well?
Or is it just a matter of timetable? In that case let me know and we will
try to find a solution.

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

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

Thank you. This server is multipurpose and has multiple webapps that listen
on 8080 by default. My library entry in /etc/apache2/sites-enables reads,
with /etc/hosts assigning "opac" and "library" to 127.0.0.1:

# Koha instance library Apache config.

# OPAC

Listen 7027

  = 2.4>
   Define instance "library"
  
   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 opac
   SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
   AssignUserID library-koha library-koha

   ErrorLog/var/log/koha/library/opac-error.log
#  TransferLog /var/log/koha/library/opac-access.log
#  RewriteLog  /var/log/koha/library/opac-rewrite.log


# Intranet
Listen 7028

  = 2.4>
   Define instance "library"
  
   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 intranet
   SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
   AssignUserID library-koha library-koha

   ErrorLog/var/log/koha/library/intranet-error.log
#  TransferLog /var/log/koha/library/intranet-access.log
#  RewriteLog  /var/log/koha/library/intranet-rewrite.log

~


I had earlier tried to access opac:7027 and got the reported error. Now I
am trying to access intranet:7028 and I can't tell a difference.

Do I need to be doing more if I reassign port numbers?


Thanks,


On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> If you reach the "system maintenance" screen that means you are hitting the
> OPAC interface, not the staff interface.
> Try on :8080
>
> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward  wrote:
>
> > Let me send off this email, and I'll report a bug.
> >
> > N.B. Koha is installed in some sense, but when I try to access the
> > webinstaller I got maintenance mode:
> >
> > System Maintenance
> >
> > The Koha online catalog is offline for system maintenance. We'll be back
> > soon! If you have any questions, please contact the site administrator
> >
> > A brief search turned up
> > https://lists.katipo.co.nz/public/koha/2013-December/038208.html which
> > picked up in a possible email typo specifying a port as 8008. This
> > suggestion appears to be irrelevant because if the OP had tried to access
> > Koha on 8008 and hadn't added anything else listening on that port, the
> > error would be "Connection refused", not "System maintenance".
> >
> > On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
> > jonathan.dru...@bugs.koha-community.org> wrote:
> >
> >> Try with --create-db:
> >>   koha-create --create-db library
> >>
> >> The doc says that --create-db is the default value, but it does not seem
> >> to
> >> work.
> >> Could you report the bug?
> >>
> >> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward 
> wrote:
> >>
> >> > Thank you. I've used koha-remove, and uninstalled and reinstalled
> >> > koha-common, including setting an a2enmod.
> >> >
> >> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
> >> but
> >> > /etc/koha/sites is an empty directory *after* trying to run
> "koha-create
> >> > library":
> >> >
> >> > toolchest sites # koha-create library
> >> > failed to load external entity "/etc/koha/sites/library/koha-
> conf.xml"
> >> >
> >> > How can I create or get an appropriate koha-conf.xml? I notice that
> >> there
> >> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing
> to
> >> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml
> (and
> >> > anything else that should be in /etc/koha/sites/library/)?
> >> >
> >> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden 
> >> wrote:
> >> >
> >> > > If you installed using the packages I believe you can use
> koha-remove
> >> .
> >> > > See here: https://wiki.koha-community.
> org/wiki/Commands_provided_by_
> >> > > the_Debian_packages#koha-remove
> >> > >
> >> > > Doug
> >> > >
> >> > > -Original Message-
> >> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
> >> C.J.S.
> >> > > Hayward
> >> > > Sent: Tuesday, July 25, 2017 11:18 AM
> >> > > To: koha@lists.katipo.co.nz
> >> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
> >> > > installing stable under Mint
> >> > >
> >> > > I have a virtual machine that may have two conflicting Koha
> >> > installations.
> >> > >
> >> > > What, if anything, can I do that will wipe all Koha installations
> >> > > completely, and install a new stable from scratch, following
> >> > > https://wiki.koha-community.org/wiki/Debian?
> >> > >
> >> > > I don't know if I *exactly* need to go so far as to delete details
> >> like
> >> > the
> >> > > Koha repository in aptitude... but I am willing to do so if I am
> >> > advised. I
> >> > > do think 

Re: [Koha] koha password recovery

[Andrews, John]

It will work with only login ID if there is an email address associated with 
the account. You can use CSS to hide the email field so they only enter the 
login ID.

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Suresh Kumar 
Tejomurtula
Sent: Tuesday, July 25, 2017 6:38 AM
To: koha
Subject: [Koha] koha password recovery

Hi,

In koha password recovery, it asks for Login:,  Email:.
I want our members to enter only loginid and they should get email to the 
members registered email id their password without asking for entering their 
email.

Is this option possible?

--
Regards
T. Suresh Kumar
___
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] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Jonathan Druart]

If you reach the "system maintenance" screen that means you are hitting the
OPAC interface, not the staff interface.
Try on :8080

On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward  wrote:

> Let me send off this email, and I'll report a bug.
>
> N.B. Koha is installed in some sense, but when I try to access the
> webinstaller I got maintenance mode:
>
> System Maintenance
>
> The Koha online catalog is offline for system maintenance. We'll be back
> soon! If you have any questions, please contact the site administrator
>
> A brief search turned up
> https://lists.katipo.co.nz/public/koha/2013-December/038208.html which
> picked up in a possible email typo specifying a port as 8008. This
> suggestion appears to be irrelevant because if the OP had tried to access
> Koha on 8008 and hadn't added anything else listening on that port, the
> error would be "Connection refused", not "System maintenance".
>
> On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Try with --create-db:
>>   koha-create --create-db library
>>
>> The doc says that --create-db is the default value, but it does not seem
>> to
>> work.
>> Could you report the bug?
>>
>> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward  wrote:
>>
>> > Thank you. I've used koha-remove, and uninstalled and reinstalled
>> > koha-common, including setting an a2enmod.
>> >
>> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
>> but
>> > /etc/koha/sites is an empty directory *after* trying to run "koha-create
>> > library":
>> >
>> > toolchest sites # koha-create library
>> > failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
>> >
>> > How can I create or get an appropriate koha-conf.xml? I notice that
>> there
>> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
>> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
>> > anything else that should be in /etc/koha/sites/library/)?
>> >
>> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden 
>> wrote:
>> >
>> > > If you installed using the packages I believe you can use koha-remove
>> .
>> > > See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
>> > > the_Debian_packages#koha-remove
>> > >
>> > > Doug
>> > >
>> > > -Original Message-
>> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
>> C.J.S.
>> > > Hayward
>> > > Sent: Tuesday, July 25, 2017 11:18 AM
>> > > To: koha@lists.katipo.co.nz
>> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
>> > > installing stable under Mint
>> > >
>> > > I have a virtual machine that may have two conflicting Koha
>> > installations.
>> > >
>> > > What, if anything, can I do that will wipe all Koha installations
>> > > completely, and install a new stable from scratch, following
>> > > https://wiki.koha-community.org/wiki/Debian?
>> > >
>> > > I don't know if I *exactly* need to go so far as to delete details
>> like
>> > the
>> > > Koha repository in aptitude... but I am willing to do so if I am
>> > advised. I
>> > > do think it would be better to wipe any Koha-created directory
>> > heirarchies,
>> > > and drop any Koha-related databases.
>> > >
>> > > (Note: My system doesn't contain any valuable information *in* Koha;
>> the
>> > > only loss would be the time and energy to delete and rebuild the
>> > > installation.)
>> > >
>> > > --
>> > > christos Jonathan Seth Hayward,
>> > > An Orthodox Christian author.
>> > > Amazon  - email
>> > >  - website <
>> https://cjshayward.com/
>> > >.
>> > > ___
>> > > Koha mailing list  http://koha-community.org
>> > > Koha@lists.katipo.co.nz
>> > > https://lists.katipo.co.nz/mailman/listinfo/koha
>> > >
>> >
>> >
>> >
>> > --
>> > christos Jonathan Seth Hayward,
>> > An Orthodox Christian author.
>> > Amazon  - email
>> >  - website <
>> https://cjshayward.com/>.
>> > ___
>> > 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
>>
>
>
>
> --
> christos Jonathan Seth Hayward,
> An Orthodox Christian author.
> Amazon  - email
>  - website .
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

I've filed a bug at
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18983

On Tue, Jul 25, 2017 at 11:17 PM, C.J.S. Hayward 
wrote:

> Let me send off this email, and I'll report a bug.
>
> N.B. Koha is installed in some sense, but when I try to access the
> webinstaller I got maintenance mode:
>
> System Maintenance
>
> The Koha online catalog is offline for system maintenance. We'll be back
> soon! If you have any questions, please contact the site administrator
>
> A brief search turned up https://lists.katipo.co.nz/
> public/koha/2013-December/038208.html which picked up in a possible email
> typo specifying a port as 8008. This suggestion appears to be irrelevant
> because if the OP had tried to access Koha on 8008 and hadn't added
> anything else listening on that port, the error would be "Connection
> refused", not "System maintenance".
>
> On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Try with --create-db:
>>   koha-create --create-db library
>>
>> The doc says that --create-db is the default value, but it does not seem
>> to
>> work.
>> Could you report the bug?
>>
>> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward  wrote:
>>
>> > Thank you. I've used koha-remove, and uninstalled and reinstalled
>> > koha-common, including setting an a2enmod.
>> >
>> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
>> but
>> > /etc/koha/sites is an empty directory *after* trying to run "koha-create
>> > library":
>> >
>> > toolchest sites # koha-create library
>> > failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
>> >
>> > How can I create or get an appropriate koha-conf.xml? I notice that
>> there
>> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
>> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
>> > anything else that should be in /etc/koha/sites/library/)?
>> >
>> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden 
>> wrote:
>> >
>> > > If you installed using the packages I believe you can use koha-remove
>> .
>> > > See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
>> > > the_Debian_packages#koha-remove
>> > >
>> > > Doug
>> > >
>> > > -Original Message-
>> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
>> C.J.S.
>> > > Hayward
>> > > Sent: Tuesday, July 25, 2017 11:18 AM
>> > > To: koha@lists.katipo.co.nz
>> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
>> > > installing stable under Mint
>> > >
>> > > I have a virtual machine that may have two conflicting Koha
>> > installations.
>> > >
>> > > What, if anything, can I do that will wipe all Koha installations
>> > > completely, and install a new stable from scratch, following
>> > > https://wiki.koha-community.org/wiki/Debian?
>> > >
>> > > I don't know if I *exactly* need to go so far as to delete details
>> like
>> > the
>> > > Koha repository in aptitude... but I am willing to do so if I am
>> > advised. I
>> > > do think it would be better to wipe any Koha-created directory
>> > heirarchies,
>> > > and drop any Koha-related databases.
>> > >
>> > > (Note: My system doesn't contain any valuable information *in* Koha;
>> the
>> > > only loss would be the time and energy to delete and rebuild the
>> > > installation.)
>> > >
>> > > --
>> > > christos Jonathan Seth Hayward,
>> > > An Orthodox Christian author.
>> > > Amazon  - email
>> > >  - website <
>> https://cjshayward.com/
>> > >.
>> > > ___
>> > > Koha mailing list  http://koha-community.org
>> > > Koha@lists.katipo.co.nz
>> > > https://lists.katipo.co.nz/mailman/listinfo/koha
>> > >
>> >
>> >
>> >
>> > --
>> > christos Jonathan Seth Hayward,
>> > An Orthodox Christian author.
>> > Amazon  - email
>> >  - website <
>> https://cjshayward.com/>.
>> > ___
>> > 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
>>
>
>
>
> --
> christos Jonathan Seth Hayward,
> An Orthodox Christian author.
> Amazon  - email
>  - website .
>



-- 
christos Jonathan Seth Hayward,
An Orthodox Christian author.
Amazon  - email
 - website .
___
Koha mailing list  http://koha-community.org

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

Let me send off this email, and I'll report a bug.

N.B. Koha is installed in some sense, but when I try to access the
webinstaller I got maintenance mode:

System Maintenance

The Koha online catalog is offline for system maintenance. We'll be back
soon! If you have any questions, please contact the site administrator

A brief search turned up
https://lists.katipo.co.nz/public/koha/2013-December/038208.html which
picked up in a possible email typo specifying a port as 8008. This
suggestion appears to be irrelevant because if the OP had tried to access
Koha on 8008 and hadn't added anything else listening on that port, the
error would be "Connection refused", not "System maintenance".

On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Try with --create-db:
>   koha-create --create-db library
>
> The doc says that --create-db is the default value, but it does not seem to
> work.
> Could you report the bug?
>
> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward  wrote:
>
> > Thank you. I've used koha-remove, and uninstalled and reinstalled
> > koha-common, including setting an a2enmod.
> >
> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
> but
> > /etc/koha/sites is an empty directory *after* trying to run "koha-create
> > library":
> >
> > toolchest sites # koha-create library
> > failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
> >
> > How can I create or get an appropriate koha-conf.xml? I notice that there
> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
> > anything else that should be in /etc/koha/sites/library/)?
> >
> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden  wrote:
> >
> > > If you installed using the packages I believe you can use koha-remove .
> > > See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
> > > the_Debian_packages#koha-remove
> > >
> > > Doug
> > >
> > > -Original Message-
> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
> C.J.S.
> > > Hayward
> > > Sent: Tuesday, July 25, 2017 11:18 AM
> > > To: koha@lists.katipo.co.nz
> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
> > > installing stable under Mint
> > >
> > > I have a virtual machine that may have two conflicting Koha
> > installations.
> > >
> > > What, if anything, can I do that will wipe all Koha installations
> > > completely, and install a new stable from scratch, following
> > > https://wiki.koha-community.org/wiki/Debian?
> > >
> > > I don't know if I *exactly* need to go so far as to delete details like
> > the
> > > Koha repository in aptitude... but I am willing to do so if I am
> > advised. I
> > > do think it would be better to wipe any Koha-created directory
> > heirarchies,
> > > and drop any Koha-related databases.
> > >
> > > (Note: My system doesn't contain any valuable information *in* Koha;
> the
> > > only loss would be the time and energy to delete and rebuild the
> > > installation.)
> > >
> > > --
> > > christos Jonathan Seth Hayward,
> > > An Orthodox Christian author.
> > > Amazon  - email
> > >  - website <
> https://cjshayward.com/
> > >.
> > > ___
> > > Koha mailing list  http://koha-community.org
> > > Koha@lists.katipo.co.nz
> > > https://lists.katipo.co.nz/mailman/listinfo/koha
> > >
> >
> >
> >
> > --
> > christos Jonathan Seth Hayward,
> > An Orthodox Christian author.
> > Amazon  - email
> >  - website  >.
> > ___
> > 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
>



-- 
christos Jonathan Seth Hayward,
An Orthodox Christian author.
Amazon  - email
 - website .
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Jonathan Druart]

Try with --create-db:
  koha-create --create-db library

The doc says that --create-db is the default value, but it does not seem to
work.
Could you report the bug?

On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward  wrote:

> Thank you. I've used koha-remove, and uninstalled and reinstalled
> koha-common, including setting an a2enmod.
>
> Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but
> /etc/koha/sites is an empty directory *after* trying to run "koha-create
> library":
>
> toolchest sites # koha-create library
> failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
>
> How can I create or get an appropriate koha-conf.xml? I notice that there
> is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
> ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
> anything else that should be in /etc/koha/sites/library/)?
>
> On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden  wrote:
>
> > If you installed using the packages I believe you can use koha-remove .
> > See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
> > the_Debian_packages#koha-remove
> >
> > Doug
> >
> > -Original Message-
> > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of C.J.S.
> > Hayward
> > Sent: Tuesday, July 25, 2017 11:18 AM
> > To: koha@lists.katipo.co.nz
> > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
> > installing stable under Mint
> >
> > I have a virtual machine that may have two conflicting Koha
> installations.
> >
> > What, if anything, can I do that will wipe all Koha installations
> > completely, and install a new stable from scratch, following
> > https://wiki.koha-community.org/wiki/Debian?
> >
> > I don't know if I *exactly* need to go so far as to delete details like
> the
> > Koha repository in aptitude... but I am willing to do so if I am
> advised. I
> > do think it would be better to wipe any Koha-created directory
> heirarchies,
> > and drop any Koha-related databases.
> >
> > (Note: My system doesn't contain any valuable information *in* Koha; the
> > only loss would be the time and energy to delete and rebuild the
> > installation.)
> >
> > --
> > christos Jonathan Seth Hayward,
> > An Orthodox Christian author.
> > Amazon  - email
> >  - website  >.
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
>
>
>
> --
> christos Jonathan Seth Hayward,
> An Orthodox Christian author.
> Amazon  - email
>  - website .
> ___
> 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] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

Thank you. I've used koha-remove, and uninstalled and reinstalled
koha-common, including setting an a2enmod.

Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but
/etc/koha/sites is an empty directory *after* trying to run "koha-create
library":

toolchest sites # koha-create library
failed to load external entity "/etc/koha/sites/library/koha-conf.xml"

How can I create or get an appropriate koha-conf.xml? I notice that there
is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
anything else that should be in /etc/koha/sites/library/)?

On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden  wrote:

> If you installed using the packages I believe you can use koha-remove .
> See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
> the_Debian_packages#koha-remove
>
> Doug
>
> -Original Message-
> From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of C.J.S.
> Hayward
> Sent: Tuesday, July 25, 2017 11:18 AM
> To: koha@lists.katipo.co.nz
> Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
> installing stable under Mint
>
> I have a virtual machine that may have two conflicting Koha installations.
>
> What, if anything, can I do that will wipe all Koha installations
> completely, and install a new stable from scratch, following
> https://wiki.koha-community.org/wiki/Debian?
>
> I don't know if I *exactly* need to go so far as to delete details like the
> Koha repository in aptitude... but I am willing to do so if I am advised. I
> do think it would be better to wipe any Koha-created directory heirarchies,
> and drop any Koha-related databases.
>
> (Note: My system doesn't contain any valuable information *in* Koha; the
> only loss would be the time and energy to delete and rebuild the
> installation.)
>
> --
> christos Jonathan Seth Hayward,
> An Orthodox Christian author.
> Amazon  - email
>  - website .
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
christos Jonathan Seth Hayward,
An Orthodox Christian author.
Amazon  - email
 - website .
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[Doug Dearden]

If you installed using the packages I believe you can use koha-remove .  See 
here: 
https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-remove
 

Doug

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward
Sent: Tuesday, July 25, 2017 11:18 AM
To: koha@lists.katipo.co.nz
Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing 
stable under Mint

I have a virtual machine that may have two conflicting Koha installations.

What, if anything, can I do that will wipe all Koha installations
completely, and install a new stable from scratch, following
https://wiki.koha-community.org/wiki/Debian?

I don't know if I *exactly* need to go so far as to delete details like the
Koha repository in aptitude... but I am willing to do so if I am advised. I
do think it would be better to wipe any Koha-created directory heirarchies,
and drop any Koha-related databases.

(Note: My system doesn't contain any valuable information *in* Koha; the
only loss would be the time and energy to delete and rebuild the
installation.)

-- 
christos Jonathan Seth Hayward,
An Orthodox Christian author.
Amazon  - email
 - website .
___
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] Meeting reminder: Development IRC meeting 26 July 2017, 14 UTC

[Nick Clemens]

Hi All,

Tomorrow is our next Koha Development meeting:

Agenda is here:
https://wiki.koha-community.org/wiki/Development_IRC_meeting_26_July_2017

Local date and time here:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting=20170726T14

Please add anything you wish to discuss to the agenda and add your name to
the apologies if you can't make it.

Hope to see you all soon!

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

[Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

I have a virtual machine that may have two conflicting Koha installations.

What, if anything, can I do that will wipe all Koha installations
completely, and install a new stable from scratch, following
https://wiki.koha-community.org/wiki/Debian?

I don't know if I *exactly* need to go so far as to delete details like the
Koha repository in aptitude... but I am willing to do so if I am advised. I
do think it would be better to wipe any Koha-created directory heirarchies,
and drop any Koha-related databases.

(Note: My system doesn't contain any valuable information *in* Koha; the
only loss would be the time and energy to delete and rebuild the
installation.)

-- 
christos Jonathan Seth Hayward,
An Orthodox Christian author.
Amazon  - email
 - website .
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Insitu borrower

[Luis Moises Rojas]

Hello everybody.

When a user use a book insitu, on the issues table, the fields
onsite_checkout =1
and the date_due is set to one hour later, but as soon as the book is
RETURN, the fields onsite_checkout is set to 0.

Questions:

1. Why the date_due is set to one hour and how to avoid this?
2. how to avoid the onsite_checkout =0? This is because we need to generate
some reports with onsite_checkout =1, it mean: insitu.

Thanks

-- 
*Luis Moisés Rojas P.*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 17.05 and memcached

[Jonathan Druart]

Wait guys, you are certainly doing something wrong here.

With Koha 17.05 you should use Plack, and if you are using Plack the
MEMCACHED* variables you will define in your apache config files will not
be used.
You should setup plack correctly, fill the 2 entries in your koha-conf.xml
files (memcached_servers and memcached_namespace), and nothing else.
Plack will bring much more performance than Memcached (
https://wiki.koha-community.org/wiki/Benchmark_for_16.11).

Regards,
Jonathan

On Tue, 25 Jul 2017 at 12:15 Adrian  wrote:

> Thank you very much Guille!
> Finally I made it work, but is a weird configuration... the only way to
> make
> it work at least on 17.05, was to have part of the config in the xml file,
> and the rest on the apache-configured file:
>
> ...
>   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
>   SetEnv MEMCACHED_NAMESPACE "koha-intra"
> ...
>
> I receive a warning on the about koha page (Config read from ENV and
> koha-conf.xml), but the Status is green and running.
>
> Thank you for your help!
>
>
>
> --
> View this message in context:
> http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p5940951.html
> Sent from the Koha-general mailing list archive at Nabble.com.
> ___
> 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] Koha 17.05 and memcached

[Adrian]

So this is the relevant part of my apache config

   SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
   SetEnv MEMCACHED_NAMESPACE "koha-intra"


And here is what I have on the /etc/koha/sites/library/koha-conf.xml


127.0.0.1:11211



Is it any faster? Not sure yet I'll need to get a word from our librarian...



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p5940967.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 17.05 and memcached

[vinod mishra]

Hello

Can you please share entire process to make it workable and how effectively
it made your Koha fast?


With Regards,

Vinod Kumar Mishra,
Assistant Librarian,
Biju Patnaik Central Library (BPCL),
NIT Rourkela,
Sundergadh-769008,
Odisha,
India.
Mob:91+9439420860
Website: http://mishravk.com/
ORCID ID: http://orcid.org/-0003-4666-7874

*"Spiritual relationship is far more precious than physical. Physical
relationship divorced from spiritual is body without soul" -- Mahatma
Gandhi*

On Tue, Jul 25, 2017 at 8:45 PM, Adrian  wrote:

> Thank you very much Guille!
> Finally I made it work, but is a weird configuration... the only way to
> make
> it work at least on 17.05, was to have part of the config in the xml file,
> and the rest on the apache-configured file:
>
> ...
>   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
>   SetEnv MEMCACHED_NAMESPACE "koha-intra"
> ...
>
> I receive a warning on the about koha page (Config read from ENV and
> koha-conf.xml), but the Status is green and running.
>
> Thank you for your help!
>
>
>
> --
> View this message in context: http://koha.1045719.n5.nabble.
> com/Koha-17-05-and-memcached-tp5939903p5940951.html
> Sent from the Koha-general mailing list archive at Nabble.com.
> ___
> 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] Koha 17.05 and memcached

[Adrian]

Thank you very much Guille!
Finally I made it work, but is a weird configuration... the only way to make
it work at least on 17.05, was to have part of the config in the xml file,
and the rest on the apache-configured file:

...
  SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
  SetEnv MEMCACHED_NAMESPACE "koha-intra"
...

I receive a warning on the about koha page (Config read from ENV and
koha-conf.xml), but the Status is green and running.

Thank you for your help!



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p5940951.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] koha password recovery

[Indranil Das Gupta]

Hi Suresh,

On Jul 25, 2017 7:08 PM, "Suresh Kumar Tejomurtula" 
wrote:
>
> Hi,
>
> In koha password recovery, it asks for Login:,  Email:.
> I want our members to enter only loginid and they should get email to the
> members registered email id their password without asking for entering
> their email.
>
> Is this option possible?

YES - if you write or get the code developed.

NO - if are looking at an in-situ Siliguri.

Regards
idg

PS. It is not a very difficult enhancement.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] koha password recovery

[Suresh Kumar Tejomurtula]

Hi,

In koha password recovery, it asks for Login:,  Email:.
I want our members to enter only loginid and they should get email to the
members registered email id their password without asking for entering
their email.

Is this option possible?

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

[Koha] request help for bulk import of Library Books Catalog in Koha

[Rajesh Shelar]

Dear  Sir/Madam,
   I request help for bulk import of Library Books Catalog  in Koha.

Kindly guide and suggest  solutions for the following

   1. Importing Books all Feilds
   2. Preparing marc file  for our accession register attached.


I have used the following tags? Are they correct...if yes theer seems to be
a problem especially for Tag 952.
*TAG*

Accession No. 001
Barcode 952 p
Accession Date. 952 d
Author 100 $ a
Title 245 $ a
Purchase Bill NO. 024 $ a
Purchase Bill Date. 952 $ w
Page No. 300 $ a
Book Supplier 952 $ e
Book Price 952 $ g
Call No. 082 $ a
ISBN 020 $ a
Edition 250 $ a
Publication Place 260 $ a
Publisher Name 260 $ b
Book Publish Year 260 $ c
Library Shelf Location 952 $ c
Subject



*Use Of Version*

Koha version:16.05.05.000
OS version ('uname -a'):Linux koha-server 3.16.0-33-generic
#44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 x86_64
Perl interpreter:/usr/bin/perlPerl version:5.018002Perl
@INC:/usr/share/koha/lib
/etc/perl
/usr/local/lib/perl/5.18.2
/usr/local/share/perl/5.18.2
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.18
/usr/share/perl/5.18
/usr/local/lib/site_perl
.
MySQL version:mysql Ver 14.14 Distrib 5.5.53, for debian-linux-gnu (x86_64)
using readline 6.3Apache version:Server version: Apache/2.4.7 (Ubuntu)Zebra
version:Zebra 2.0.44 (C) 1994-2010, Index Data ApS Zebra is free software,
covered by the GNU General Public License, and you are welcome to change it
and/or distribute copies of it under certain conditions. SHA1 ID:
419ad759807269fdfa379799a051ed3a551c6541 Using ICU

I humbly request your guidance and express my gratitude in anticipation of
your help


-- 
*​**Thanks & Regards*



*Mr. Rajesh R.Shelar*
*Sadhu Vaswani Institute Of Management Studies For Girl's ( MBA )*
*Koregaon Road,Pune*
*Mob.No.8380941380*

*Save Water..Conserve Life.*



-- 
*​**Thanks & Regards*



*Mr. Rajesh R.Shelar*
*Sadhu Vaswani Institute Of Management Studies For Girl's ( MBA )*
*Koregaon Road,Pune*
*Mob.No.8380941380*

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