s/Thread/Threat/
-- Forwarded message -
Van: Marcel de Rooy
Date: do 27 aug. 2020 om 08:26
Subject: Office365 and Koha selfregistration verification mails
To: Koha
FYI
The Office365 Advanced Thread Protection feature rewrites URLs and verifies
them when you click on them. When
FYI
The Office365 Advanced Thread Protection feature rewrites URLs and verifies
them when you click on them. When you try to register in Koha with an
Office365 email address, you will have a problem.
This has a nasty side-effect on selfregistration mails when you enabled
verification mails.
What
Hi, I suggest you make a clean install, create a fresh instance, and then
load the DB and var lib files.
That will give you better results even in a happy restore case, as several
files will be generated with newer defaults.
El mié., 26 ago. 2020 17:54, tommaso spazzali
escribió:
> Thanks Alvar
Thanks Alvaro,
I was sure my backup was complete (I already made a restore with it) so
looking a little deeper in the internet I found this:
https://kohageek.blogspot.com/2020/06/dbixclassstoragedbicatch-dbi-connection.html
and it worked very well
I removed the wrong library and before doing a
We have a new Library Director, and the question has come up again.
But now, I can't find
"Home > Administration > Columns settings
OPAC
OPAC table, biblio detail
item_status (check in the box to make it hidden by default) "
I also looked under OPAC and couldn't find anything to change the column
Hi Tommaso
In my case, for an unknown issue, the database backup with the koha backup
util was not complete thus, load failed.
I had to run backup using the mysqldump and that worked fine.
I followed this instructions
http://kohageek.blogspot.com/2015/08/move-old-koha-database-to-new.html
The
Hi Alvaro, hi everybody,
did you solved this error?
unfortunately I have the same behaviour moving with koha-backup /
kpha-restore from ubuntu 16 to ubuntu 20.
The strange thing is that I tried succesfully the same operation on a
test server, now, in the production server I get the error ...
any
Hi Carlos.
Your SQL does not need type-casting. It is just missing an @ and a
couple of " in the ExtractValue for the 100 tag.
It should be:
WHERE ExtractValue(metadata,
'//datafield[@tag="100"]/subfield[@code="9"]') IN
rather than
WHERE ExtractValue(metadata, '//datafield[tag=10
8 matches
Mail list logo