Hi Elaine,
Please check bug 30883.
This fix is in: 22.11.00, 22.05.01, 21.11.10, 21.05.17
Questions here are: Are you using ElasticSearch? And does the number of touched
biblio records exceed the merge limit ?
Regards,
Marcel
Van: Koha namens Elaine Bradtke
Ve
Hi,
Occasionally when we view/create/edit a record, the record page will not
display properly, all the field will turn blank, any update to the record just
pauses and we need to wait from minutes to hours before it fixes itself and the
record to be displayed normally again. It happens from tim
I'm in the process of adding some 610 fields to catalogue records. These
are linked to existing authority records. If I then edit the existing
authority record (usually to add (Musical group) to the 110) it doesn't
update 610 in the biblio record in which I just added the 610. However, it
updates
Dear Colleagues,
I use Koha as SRU Server (Version 22.05.03).
I can connect to the server without credentials (user and password is blank)
and with credentials from koha-conf.xml
How can I disable connection without credentials?
Example from koha-conf.xml:
/etc/koha/zebradb/ccl.pro
Hi Michael,
not sure then :(
Maybe someone else has an idea?
Katrin
On 25.08.22 18:39, Michael Kuhn wrote:
Hi Katrin
You wrote:
> the fix did prevent the problem from occurring on older versions, but
> it doesn't fix the data.
>
> Could it be the bad data was there before, maybe from using
Hi Katrin
You wrote:
> the fix did prevent the problem from occurring on older versions, but
> it doesn't fix the data.
>
> Could it be the bad data was there before, maybe from using an older
> DBMS version?
>
> The simplest fix is to delete the entries in the old_ and deleted_
> tables with th
Hi Michael,
the fix did prevent the problem from occurring on older versions, but it
doesn't fix the data.
Could it be the bad data was there before, maybe from using an older
DBMS version?
The simplest fix is to delete the entries in the old_ and deleted_
tables with the doubled up IDs and the
Hi
In our library we are using Debian 11 with MariaDB 10.5.15 and Koha
21.05.14.
When deleting bibliographic records in the staff client, some deletions
produce the message: "An error has occurred! Error 500 / This message
may have been caused by any of the following reasons: etc." In such
8 matches
Mail list logo