Hi
> I see so I guess the administrators need to look into this matter.
> Should we report about this in the Bugzilla?
I suggest first to find out yourself what's the problem, but if it
persists - yes, I guess you should report this in Bugzilla.
BTW please always answer to the list so other
i logged a bug
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28616
On 23/06/21 2:16 pm, Mason James wrote:
hi Michael ,
this does seem to be a bug in 21.05 (at least)
the following command should fix the problem, if the libdata-printer-perl
package is not installed
$ sudo apt
Hi Charles
Do you know what packages have been updated ?
If apache, it might have overwritten your config. There is a different
configuration for patron and admin interfaces.
Also, have you restarted koha related services? i.e. plack, apache,
koha-common, memcached ?
Regards
Alvaro
hi Michael ,
this does seem to be a bug in 21.05 (at least)
the following command should fix the problem, if the libdata-printer-perl
package is not installed
$ sudo apt install libdata-printer-perl
On 23/06/21 4:14 am, Michael Kuhn wrote:
Hi Himanshu
> image.png
> This is the error i am
Hi Katrin,
Thanks for that. Interesting to learn about Koha's use of cookies. Doesn't
that mean that Koha should present a popup to ask for a user's consent? The
ICO (which monitors data protection compliance in the UK) says:
"You must tell people if you set cookies, and clearly explain what the
Nothing in plack-error.log?
If you have a 500 you should see something useful there.
Le mar. 22 juin 2021 à 09:48, Michael Kuhn a écrit :
>
> Hi Jonathan
>
> You wrote:
>
> > Hi Michael, what do you have in the Koha log files?
>
> When trying to delete a user, logfile
Hi Michael, what do you have in the Koha log files?
Le lun. 21 juin 2021 à 21:01, Michael Kuhn a écrit :
>
> Hi
>
> We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha
> 20.11.00 (using Shibboleth authentication).
>
> To avoid auto increment issues we have implemented the solution
Hi Jonathan
You wrote:
> Hi Michael, what do you have in the Koha log files?
When trying to delete a user, logfile "/var/log/koha/embl/plack.log" says:
192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET
/intranet/members/deletemem.pl?member=83 HTTP/1.1" 200 32438
Hi Michael,
if you are really using 20.11.00 and not 20.11.01 or newer then I think
you might be bumping into bug 27144 [1]. Please upgrade your koha
version to fix the issue.
Joonas
[1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144
On 21/06/2021 22:01, Michael Kuhn wrote:
>
Hi there.
Given that web application logs are so laconic maybe you can temporary
enable SQL query logging in your database to see which query is producing
the error.
Cheers.
Javier
On Tue, 22 Jun 2021 at 09:48, Michael Kuhn wrote:
> Hi Jonathan
>
> You wrote:
>
> > Hi Michael, what do you
Hi Jonathan
> Nothing in plack-error.log?
> If you have a 500 you should see something useful there.
No, sorry - absolutely nothing in "plack-error.log".
Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123
Hello Tasha,
I've created 2 records with
245$a Electroactive polymer (EAP) actuators as artificial muscles
and the following query returns the 2 results.
/opac-search.pl?idx==Electroactive%20polymer%20%28EAP%29%20actuators_search=1
Tried on master and 20.11.06.
Maybe a silly idea: does it
Hello, all!
Yesterday, I updated my library's entire catalog. What we did was to
exchange the CCODE and LOC. It worked fine. It took all day and part of
today, but it worked. Then I ran Linux system updates. It too worked fine
-- in staff mode.
In the patron mode, it's another story. It
The bug is "resolved fixed", they are excluded from the default search.
Le mar. 22 juin 2021 à 10:44, Michael Kuhn a écrit :
>
> Hi Joonas
>
> You wrote:
>
> > if you are really using 20.11.00 and not 20.11.01 or newer then I
> > think you might be bumping into bug 27144 [1]. Please upgrade
Maybe helpful to know, if you add ALL at the beginning of your bugzilla
search, the closed and resolved bugs will be included :)
Katrin
On 22.06.21 11:04, Jonathan Druart wrote:
The bug is "resolved fixed", they are excluded from the default search.
Le mar. 22 juin 2021 à 10:44, Michael Kuhn
Den 22.06.2021 13:02, skrev Carlo Dumontet:
Could anyone please tell me how to create a new Collection Code?
- Go to More > Administration > Authorized values
- Click on CCODE in the table
- Click on the button that says "+ New authorized value for CCODE"
Hi Joonas
You wrote:
> if you are really using 20.11.00 and not 20.11.01 or newer then I
> think you might be bumping into bug 27144 [1]. Please upgrade your
> koha version to fix the issue.
>
> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144
Yes, this sounds exactly like
Jonathan, thank you!
It does work without the parentheses.
I would suspect an encoding problem, but for that the problem only manifests in
the OPAC, and not the intranet.
I came across this issue while testing after migrating from MariaDB to Percona
MySQL. Your reply prompted me to check
Could anyone please tell me how to create a new Collection Code?
Many thanks
Carlo
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
The HTTP 500 is a generic error code. There should be more detailed info in
the log files.
Joel Coehoorn
Director of Information Technology
York College of Nebraska
On Tue, Jun 22, 2021 at 3:05 AM Charles Kelley
wrote:
> Hello, all!
>
> Yesterday, I updated my library's entire catalog.
*> There is an exception for cookies that are essential to provide an
online*
*service at someone’s request (eg to remember what’s in their online
basket,or to ensure security in online banking).*
Those are the only cookies Koha uses by default, unless you do something
like adding the Google
Hi Himanshu
> image.png
> This is the error i am getting when I click on import Patrons module.
> Koha version is 21.05. this is the reason I asked.
Error 500 is a very unspecific HTTP message that can have many different
reasons. You will have to search for the reason in the log files.
22 matches
Mail list logo