Hi David
That did it, thank you! Switching from 2FA back to Password, and then
reenabling 2FA in the interface works perfectly. Thank you very much for this.
It does indeed look like an unintended consequence of that change – so I’ll
file a bug.
Thanks again,
Martin
From: David Nind
Date:
Hi Martin
This is what I tried, not sure whether this helps or not as it is not
something I know a great deal about.
Using the koha-testing-docker (or KTD, the environment used for testing by
many in the Koha Community), I set an encryption key, enabled the
two-factor authentication system pr
I’ve actually spotted one other error:
Error decoding what should be base32 data:
vg¥ o¯Ët©¹ìd`½Ï¯ïE¤9¯yïWŽ¼«{† at /usr/share/koha/lib/C4/Auth.pm line 886.
2023/11/10-15:12:36 Received QUIT. Running a graceful shutdown
Sending children hup signal
2023/11/10-15:12:37 Worker processes cleaned u
Hi Martin,
I believe that should have worked especially after your reboot. I would
add the key back, as you should not leave it with the placeholder string.
Maybe someone else has an idea?
Katrin
On 10.11.23 20:11, Martin Morris wrote:
Hello Katrin,
Thanks for your help. I edited koha-co
Hi,
there is a command line script to create a new superlibrarian user, see:
http://kohageek.blogspot.com/2018/07/create-super-librarian-by-command-line.html
Hope this helps,
Katrin
On 10.11.23 16:35, Aida Djikic wrote:
Hi Anke,
I thought borrowers in this case meant users other than superu
Hello Katrin,
Thanks for your help. I edited koha-conf.xml in
/etc/koha/sites//koha-conf.xml, so I think that’s the right place?
I’m also using 2FA in case that helps.
Martin
- - - - - -
Hi Martin,
in which file did you replace it?
You were on the right track there, but make
Hi,
I can see a few things that could cause you issues:
952
$2 = Koha expects the code of the classification scheme here, not the
description. You can find all the available codes under administration >
classification configuration. For DDC it's ddc.
$d = The accession is probably the wrong fo
Hi Martin,
in which file did you replace it?
You were on the right track there, but make sure to add the entry to the
koha-conf.xml file used by your koha instances/sites. You might have
changed the template instead of the used file.
Hope this helps,
Katrin
On 10.11.23 16:02, Martin Morris wr
Hi Anke,
I thought borrowers in this case meant users other than superuser; I should
have skipped that as I did before. But the zebraidx was doing nothing, and
I could not even quit the database; I had to close Putty.
It's good to know there's a way to re-create the super user; I'll try to
find t
Hello all,
I’m having trouble logging into our staff interface this morning. Here’s
what’s happening:
* I’m running koha 23.05.04
* I get an Error 500 page after putting in my credentials
* The only error message I can see in any log file is in plack-error.log
* Exception 'K
Hi Aida, you may have accidentally deleted your super user if you truncated the
borrowers table.
There is a workaround to re-create the super user, afaik, but I'm not sure
where I got this info. Perhaps s.o. else can help?
Otherwise, if you haven't yet invested lots of work in customizing the
Hello Anke and others,
I tried this again today; truncated the zebraqueue, and reset the zebra
index as listed on the wiki:
Reset Zebra index
zebraidx -c /etc/koha/sites/your_koha_library/zebra-authorities-dom.cfg -g
iso2709 -d authorities init
zebraidx -c /etc/koha/sites/your_koha_library/zebr
Hi,
What is your Koha version, operating system, installation mode ?
Great to see ITER uses Koha :D
Best regards,
Le 09/11/2023 à 06:06, Olcese Martina EXT a écrit :
Dear Ladies and Sirs,
Following the exchange on the Koha mailing list on bulk upload, I wish to
request your advice regarding
13 matches
Mail list logo
