Ann,
The problem certainly comes from the $ in the currency code.
If you have access to the database, you could try and change "$NZ"
with "NZ". I am pretty sure it will fix the issue.
It's a bug, you can open a new bug report on bugs.koha-community.org.
Regards,
Jonathan
2015-11-01 20:38
Hey all, apologies for the long delay. I'm going to just respond in this
thread instead of cluttering with a new one.
To recap, I have an older computer running a new Koha, and I just want to
make sure that there's no configuration problems before I go out and buy
better hardware with my tiny
Aparrish schreef op do 05-11-2015 om 11:43 [-0700]:
> PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
>
> 28682 www-data 20 0 358772 119388 11720 R 29.9 3.9 0:03.49 404.pl
>
> 28684 www-data 20 0 355888 116532 11692 R 29.2 3.9 0:03.26 404.pl
Andrew Parrish schreef op do 05-11-2015 om 18:20 [-0500]:
> wow, thanks. I hate to be a bother, but do you think you could point
> me where to look to find this path that is set incorrectly? Is this a
> Koha-internal problem or something between apache and koha?
>
I don't know what it would be
So I've been continuing to poke around tonight and it seems my problem is a
long list of 404 errors caused by requesting the visual elements of the Koha
installation in a place where they're not. Anyone want to help a script
kiddie find the trouble spot?
more info: All the 404s being returned are
I, too, am seeing these two MySQL errors (1060 & 1062) thrown when trying to
update from 3.18.11 --> 3.18.12. There never seemed to be a resolution posted
to this issue. Is it benign as Doug suggested or something about which concern
should be raised?
The installation here is Ubuntu 14.04.3
Hi all,
I'm trying to export my collection from an older version of Koha :
Koha version:3.01.00.145OS version ('uname -a'):Linux koha3 2.6.26-2-686 #1
SMP Thu Aug 19 03:44:10 UTC 2010 i686 GNU/LinuxPerl interpreter:
/usr/bin/perlPerl version:5.010001
and get the MARC file for import into a new
7 matches
Mail list logo
