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
_
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 em
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_NAMESP
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/
O
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 an
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 (memcach
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
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 t
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&iso=20170726T14
Please add anything yo
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: Tu
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
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-commo
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 t
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
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 ac
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,
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 instanc
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
I
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
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
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
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 w
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 <
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’
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-pass
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 credent
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
27 matches
Mail list logo
