Hello.
I continue about my test over SIP2 and last test; The SIP server and
processes are working 2:30 hours and no clients connect to SIP. Meanwhile,
First client connect to SIP ports and I see the carachters are corrupted.
Thanks
Ahmet Melih
___
Hi Mehvish
Quick questions:
a) what version of Koha are you using and how was it installed - (i)
deb package or tarball?
b) what is the full path to this folder that you mention has all the
permissions for everyone?
c) Have you linked your selected MARC21 framework's 856 $u field to
the
I am not able to upload ebooks in the designated folder.it says check
permissions although the destination folder is open to everyone.
--
*Mehvish*
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
I knew that our e-mail system modified all the URLs in incoming messages for
extra security, but I didn't realize it did the same to outgoing messages. My
apologies. Try this:
www(dot)philobiblios(dot)info:81/authcatResults(dot)xsl
www(dot)philobiblios(dot)info:81/authcatDetail(dot)xsl
Hi to all,
Il 05/12/2016 18:18, Jonathan Druart ha scritto:
On a side note, we lack testers. Patches are in the queue to support new
versions of MySQL (out of the box, because you can still use MariaDB or
tweak the MySQL config to make it works).
in fact if you want try Koha on Ubuntu 16 LTS
Hey Fred,
Thanks for your help and sharing your resources, however I think there's
been a misunderstanding.
I have already done that and altered those template files to my needs in
order to define how and what fields are shown in the *normal* detail view.
I misinterpreted you and thought what
Sorry about the site being down. I rebooted the server and it’s working again.
One of these days I’ll look into why that happens, but not today.
As far as I can tell, all you need to do is configure the XSLT files to have
the right file names so they can find each other. Then go into Koha
At 04:56 PM 12/5/2016 +, Jonathan Druart wrote:
Paul,
Hum sounds like I already answered you the same things a few months ago...
I'll reply off-list to Jonathan as it could possibly only create on-list
noise...
P.
___
Koha mailing list
Paul,
Hum sounds like I already answered you the same things a few months ago...
Well, you are still comparing 3.8 with 3.18, last release is 16.11, with
plack and memcached support.
What you missed (living in the past):
Bug 15342 - Performance 3.22 - Omnibus
Bug 7172 - Omnibus for Plack
At 01:28 PM 12/5/2016 +, Raymund Delahunty wrote:
I ran repeated tests for up to 48 hours or more. I think the indexes were
partly updated- 7K out of 13K "remained". I have two files to deal with
tomorrow (3K, and 30K small MARC records- bibs and items). I am tempted to
try the Undo again
Hello librarians and developers,
Koha 16.11 and its Debian packages have now been released [1].
As Mirko noted Debian Wheezy is no longer supported and Debian packages
won't be provided for 3.22 [2].
I should also added that some important bugs have been reported recently
and it may be better
At 02:02 PM 12/4/2016 +, Marcel de Rooy wrote:
Please note:
Staying at Koha 3.8 is not recommended. The current release (16.11 ==
3.26) is already 9(!) release cycles behind..
And I would not advise others to do so.
Marcel -- I don't know how you could read my comments as a
I ran repeated tests for up to 48 hours or more. I think the indexes were
partly updated- 7K out of 13K "remained". I have two files to deal with
tomorrow (3K, and 30K small MARC records- bibs and items). I am tempted to try
the Undo again to see if it works. I am asking our support company
Hi,
Have you waited long enough for zebra to re-index your catalogue ? To
me, what you are describing is not faulty. Once you reverted an imported
batch, it takes time to zebra to remove the records from the indexes.
Especially if you work with large files.
If you waited long enough and the
Thanks all for your help,
Yes, I do have a test server and I'm doing all the changes in a Docker
container, so if something goes wrong I just rollback to where it was
initially.
Also, all the changes I make to core including XSLT files modifications go
in the Dockerfile and hence are documented
That is exactly the way I have used the feature many times in the past- well,
once to correct an incorrectly modified batch a few moments after the data was
loaded, when I spotted a second necessary correction I had missed (much to my
annoyance), and maybe 2 dozen times to rip out previously
This is a bug, I have opened a new bug report and will try to attach a
patch soon.
See bug 17096.
On Sun, 4 Dec 2016 at 11:05 Abdulsalam Yousef wrote:
> Hello all,
>
> We have an error appears during navigation through ( patron pages) in koha
> 16.11
> for example when
17 matches
Mail list logo