Hi,
Mark Tompsett schrieb am 08.10.2015
> Greetings,
>
> We owe them the best solution.
I don't think I owe anyone anything when it comes to free community
support. But I'd rather not decide what is the best solution for
everyone.
> requires Apache and Networking configuration knowledge.
>
Dear bybak ,
I suppose it may be zebra index errors.
you can exceute following operations,
change zebra owner , maybe koha ,
export KOHA_CONF=/etc/koha/koha-conf.xmlexport PERL5LIB=/usr/share/koha/lib
# rebuild koha index
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl
try again ,
Hello all,
Thank you all for the suggestions. I had already disabled 000-config and
enabled koha, and actually deleted the default site on the recommendation of
another set of instructions, which was why I was confused. However, upon
opening the web browser again this morning the OPAC catalog is
Hello all,
Fresh install of Koha on a Debian Jessie computer. The machine has three
gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm
going to assume I just need a better PC, but this Koha instance (a local
test server through 127.0.1.1) is so slow it's literally
Greetings,
Version 3.22 is still a month or so away from release. Because from a
software perspective, I think Koha running Plack is your only hope. And that
will be a feature available out of the box, if I am not mistaken.
However, your assumption of new hardware is a good place to start,
Aparrish schreef op do 08-10-2015 om 09:22 [-0700]:
> but this Koha instance (a local
> test server through 127.0.1.1) is so slow it's literally impossible to
> use,
> both staff and opac side. It takes about twenty seconds to resolve any
> request at all.
What is slow? Loading the main page,
Bob Ewart schreef op do 08-10-2015 om 15:59 [-0400]:
> However, I'm still having the original problem of the people on the
> circulation desk being logged out when trying to check an item out.
> The item is checked out!
How do they connect to the Koha server? Is there a proxy in the middle
Hi there
It's a permissions thing. I'm sorry I cannot get to the settings at the
moment but what I did was set circulation users to super librarian
permission settings and then turned each one off until I hit the crucial
one, then reset everything else accordingly. Start at the bottom.
Regards
>"Version 3.22 is still a month or so away from release. Because from a
>software perspective, I think Koha running Plack is your only hope. And that
>will be a feature available out of the box, if I am not mistaken."
Really? This is fantastic. I'll hold off on troubleshooting my current Plack
Greetings,
I wrote:
"Version 3.22 is still a month or so away from release.
Because from a software perspective,
I think Koha running Plack is your only hope.
And that will be a feature available out of the box, if I am not
mistaken."
Craig Butosi replied:
Really?
-- Really.
Hi Liz
That fixed bug 14952 and it works on a small test case I built using the
default data.
There were a number of differences in my database structure from the
fresh created one, so I wrote a little perl program to fix them. My
'permissions' and 'userflags' tables had some differences
11 matches
Mail list logo