Hello,
Please have a look at bug 23425
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23425
If you can, apply the patch and report the MARCXML error you get.
Regards,
Jonathan
Le mar. 30 juil. 2019 à 02:13, Sahadeo Taware
a écrit :
>
> Dear Sir
> I am using koha software (version
Hello Carlos,
There is a pref for that: todaysIssuesDefaultSortOrder
Regards,
Jonthan
Le lun. 11 nov. 2019 à 00:36, Carlos Lopez a écrit :
>
> Hi folks
>
> When we return items on Koha we get the last-scanned item appearing at the
> top of the list. However, when we issue items they appear in
There are the keywords: "No space left on device"
Le lun. 11 nov. 2019 à 18:09, Victor Barroso Oliveira
a écrit :
>
> Good afternoon
> After an upgrade from ubuntu 18.04.3 koha is experiencing an error in
> mariadb. The error below follows.
>
> root@SEDSRVPRSCB01:/# service mysql restart
> Job
Hi Doug,
The koha-plack --enable command did not work.
Can you post the result of the following command:
$ sudo grep Include /etc/apache2/sites-available/main.conf
Regards,
Jonathan
Le mer. 6 nov. 2019 à 01:00, Doug Dearden a écrit :
>
> Hey Michael,
>
> OK, this is weird.
> (Instance is
Hello Yatheesh,
Which exact version of Koha are you using?
Do not you have another error (referring to a Koha file)?
Did you create a currency?
Regards,
Jonathan
Le ven. 15 nov. 2019 à 05:03, Yatheesh lis a écrit :
>
> Hi
>
> I am getting following error when i am try to create new vendor or
>
> improved for easier everyday usage in libraries. Because if something is
> clear and easy everybody do it without fear and stress.
>
> Thank You
>
> Michal
>
> čt 21. 11. 2019 v 17:14 odesílatel Jonathan Druart
> napsal:
>>
>> Hello everybody,
>>
can set as "anonymized" and store them
> separately from "live" borrowers, because we want to see them as results from
> borrower searches. What do You think about this?
>
> Michal
>
> pá 22. 11. 2019 v 15:41 odesílatel Jonathan Druart
> napsal:
>&g
ation of their records? I think that must be done only in case that we
> want to anonymize borrower. Not before this day. Because if we will copy all
> translation into new table we'll maka database bigger wi same data. Do I
> understand it clear?
>
> Michal
>
>
Thanks for the feedback Aaron, I will try and make it flexible,
keeping it mind your need :)
Le ven. 22 nov. 2019 à 00:47, asakov...@hmcpl.org
a écrit :
>
> Jonathan,
>
> First of, wow, thank you SO much for taking on this task!
>
> Option 1 looks really good to me. One thing, however: we’re
Hello everybody,
I have been contracted by KohaLa to work on some GDPR requirements.
The main idea is to "anonymize" patron's data but letting the library
access the transactions' statistics.
I am going to present you what I am planning to implement, in order to
collect ideas and answers.
There
applied in the correct order,
on my gitlab repo:
https://gitlab.com/joubu/Koha/commits/bug_24151
Cheers,
Jonathan
Le jeu. 21 nov. 2019 à 17:13, Jonathan Druart
a écrit :
>
> Hello everybody,
>
> I have been contracted by KohaLa to work on some GDPR requirements.
> The main idea i
Hello Mohammad,
Which version of Koha are you using?
Regards,
Jonathan
Le mer. 16 oct. 2019 à 10:30, Mohammad Nashbat a écrit :
>
>
> Dear All,
>
> We faced a problem in koha that is Patron categories won't be renewed to a
> new date, if we renew any patron it's coming again with an old date
Hello Steve,
It means that the itemtype of the item has been removed (items.itype
of biblioitems.itemtype does not exist in the itemtypes table).
There is a script to catch such inconsistencies, see
misc/maintenance/search_for_data_inconsistencies.pl
Regards,
Jonathan
Le mar. 22 oct. 2019 à
à 21:06, Mike D. a écrit :
>
> Hello Jonathan,
> I understand. You're right. So, can we document plan for new GDPR
> improvements on wiki? Next steps?
>
> Michal
>
> pá 22. 11. 2019 v 16:53 odesílatel Jonathan Druart
> napsal:
>>
>> The anonymized_borrowe
Christos, I am not sure you read the answers we gave you.
To start the install process you will need the credential of the
MySQL/MariaDB user.
If you are on a debian-based system you should use the debian packages
and use the koha-create command to setup everything for you (config
file, DB user,
Hello Christos,
After you installed Koha via the debian packages you should see the
webinstaller. At the end of the install process there is a tool that
will guide you through different steps to create a library, a patron's
category, and a superlibrarian user.
If you have not done the
values for branches.branchcode or categories.categorycode
> available? An ack(-grep) in /etc/koha for branches, branchcode, and
> categorycode did not turn up information scent.
>
> On Thu, Nov 28, 2019 at 2:38 AM Jonathan Druart
> wrote:
>>
>> Hello Christos,
>>
>> Aft
Hi Luis,
Make sure you have a default circulation rule.
Regards,
Jonathan
Le jeu. 19 sept. 2019 à 18:16, Luis Moises Rojas
a écrit :
>
> Hello everybody,
>
> In Circulation Module, when we search we are having the following error:
> Can't call method "lengthunit" on an undefined value at
>
Bruck,
My understanding of the error is that you have a field that is mapped
with the "authorised value" branches (that's not a real authorised
value). But at least one of those field has a value that is not a
branchcode defined in your system.
The weird thing is that, by default, only item's
}->{'authorised_value'} eq
> "branches" ) {
> warn $value;
> return Koha::Libraries->find($value)->branchname;
> }
>
> Thanks,
> Bruck T.
>
> -Original Message-
> From: Jonathan Druart
> Sent: Wednesday, Decembe
ditem.pl, referer:
> http://koha.wider.unu.edu:8080/cgi-bin/koha/catalogue/detail.pl?biblionumber=8418=scs_1576671122887
>
> *****
> -Original Message-
> From: Jonathan Druart
> Sent: Wednesday, December 18, 2019 3:15 PM
> To: Tadesse, Bruck
Hi Carlos,
We are not very far from supporting Postgresql I think.
You can find relevant bug reports linked to the umbrella bug 7365
(Koha should support PostgreSQL)
There is no active work currently done directly on that.
But refactoring and moving our code to the Koha namespace, as well as
Hi Mohamad,
They are hardcoded indeed, they cannot be modified without modifying the code.
We have damaged and lost, so I guess it makes sense to have withdrawn as well.
Can you open an enhancement request on our bug tracker?
https://bugs.koha-community.org/
Regards,
Jonathan
Le mer. 4 mars
How did you upgrade?
This column (reserves.item_level_hold) has been added by 19.06.00.005,
you should have it in 19.11.
Le lun. 24 févr. 2020 à 08:21, Admire Mutsikiwa
a écrit :
>
> Hi
>
> I did an upgrade from Koha version 19.05 to Koha version 19.11 on Ubuntu
> 18.04. Om search the OPAC or
Hello Admire,
Can you check the value of borrowers.dateexpiry for this patron?
(directly in DB if possible)
SELECT dateexpiry FROM borrowers WHERE borrowernumber=?;
Regards,
Jonathan
Le lun. 24 févr. 2020 à 08:55, Admire Mutsikiwa
a écrit :
>
> Hi
>
> I am running Koha 19.11.02 on Ubuntu 18.04
Column "item_level_hold" of the table "reserves".
Le lun. 24 févr. 2020 à 11:37, Admire Mutsikiwa
a écrit :
>
> Thank you for the information. Could you have an idea of which table it
> was added to?
>
>
> Regards,
>
> Admire
>
> On 24/2/2020 11:
Hello Admire,
Go to the admin home page, you will see a new accounting section:
Accounting
Debit types
Define debit types.
Credit types
Define credit types.
Le lun. 24 févr. 2020 à 11:49, Admire Mutsikiwa
a écrit :
>
> I have upgraded to Koha 19.11.02 on Ubuntu 18.04 LTS. I have
Hi Caitlin,
I recreate the problem, I opened a bug report:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24542
I am going to submit a patch.
Thanks for reporting it!
Regards,
Jonathan
Le jeu. 30 janv. 2020 à 02:20, Caitlin Watkins
a écrit :
>
> Checkout page - Can't locate object
Hello Rob,
Here is what you were looking for:
use Modern::Perl;
use Koha::AuthUtils;
use C4::Auth;
# Generate the hash
my $hashed_pwd = Koha::AuthUtils::hash_password('Your password');
# Compare it with a new login
my $login_pwd = 'Your password';
say C4::Auth::checkpw_hash( $login_pwd,
If you are writing PHP code and that the function works as you expect,
then use it :)
Le ven. 21 févr. 2020 à 12:36, robm a écrit :
>
> Hi Jonathan.
> Thank you.
> But tell me: some special reason for not using the php function? Because
> it's working ok ...
>
>
>
>
> --
> Sent from:
Hi Michael,
Did you see bug 23402? It seems related to translation.
Note that you should use the latest 19.05.x anyway (which is 19.05.06)
Regards,
Jonathan
Le mar. 21 janv. 2020 à 18:13, Michael Kuhn a écrit :
>
> Hi
>
> Using Koha 19.05.02 (was installed like this, no update from previous
>
Michael, it's a known bug, see:
Bug 8331 - Hidden field does not hide from plain MARC view
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8331
Regards,
Jonathan
Le mar. 21 janv. 2020 à 21:54, Michael Kuhn a écrit :
>
> Hi
>
> Field MARC 856 $u usually does contain an electronic
Hello,
Debian 10 is not supported yet. Please use Debian 9 instead.
Regards,
Jonathan
Le ven. 10 janv. 2020 à 12:51, Clogher Historical Society
a écrit :
>
> Hi,
>
> I'm trying to install Koha on Debian 10. I've tried a number of walk
> through's such as
happy holidays.
>
> Thank you
>
>
>
>
>
> Sent from my Samsung Galaxy smartphone.
> Original message ----
> From: muirunyeri
> Date: 23/11/2019 07:58 (GMT+03:00)
> To: Jonathan Druart
> Cc: koha , Koha Devel
>
> Subject: [koha] Edite
Hello Michael,
What you describe is related to bug 24215 (Warnings about guarantor
relationships show ARRAY errors) and bug 24263 (borrowers.relationship
should not contain an empty string).
One is already in 19.11.02, the other one is waiting for QA.
Regards,
Jonathan
Le dim. 5 janv. 2020 à
From the website: "We have vast experience in Software development for
Koha ILS having more than 5 years."
Can you give us an example? I failed to find the company in the git
log, bug tracker, contributor list...
Le mar. 7 avr. 2020 à 15:13, ZINET Software Solutions a écrit :
>
> Dear Sir
Hi Holger,
You could backup the content of the letter and then delete it. That's
certainly the easiest way.
Otherwise you can play with borrower_message_preferences, backup then
delete the relevant rows (I'd say where message_attribute_id=4, but
could depend on the rows in message_attributes).
Hi Michal,
It depends on the plugin :)
A plugin can do almost everything it wants, so you should only install
plugins you really trust.
And you should give the permissions to manage them to librarians you
really trust as well.
I should add that plugins are almost never reviewed (by the QA team
Hello Quynh,
Use the script misc/admin/set_password.pl
Regards,
Jonathan
Le sam. 16 mai 2020 à 09:47, Quỳnh Vũ Đỗ a écrit :
>
> Hello everyone,
> Thanks to useful advice provided by the list community, I was able to
> upgrade from Koha 3.18 to Koha 19.11.05
>
> I could open the Staff login
Hello,
I would focus on indexer-output.log and the "Connection refused" error.
How often this error appears?
When you feel that "it is slow", did you try to `htop` and see which
processes were consuming the resources (ram and/or cpu, maybe IO as
well)?
The following error seems related to local
How lucky you are to have gotten this hardware problem, you will have
the lastest Koha version :)
You only need to reinstall the system, install Koha using the debian
packages, drop and recreate the DB, inject your dump into the empty
DB.
Restart the koha-common service, hit the intranet page and
sh" : "aa751e09be0a5072e8570670309b1f12348f023b",
> "build_date" : "2020-02-29T00:15:25.529771Z",
> "build_snapshot" : false,
> "lucene_version" : "8.4.0",
> "minimum_wire_compatibility_version" : "6.8.0",
> &quo
Which version of elasticsearch did you install?
Le mar. 17 mars 2020 à 21:33, Tom Hanstra a écrit :
>
> Well, that obviously is an important switch. Ant that takes me one step
> closer. Thank you.
>
> Now, of course, I'm getting no results. Koha says that I did not specify
> any search criteria
There is a bug report in the pipe that will certainly answer your need:
Bug 22784 - Archiving Purchase Suggestions
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22784
Le ven. 20 mars 2020 à 11:25, Stephen Graham a écrit :
>
> Hi All - we've just switched the purchase suggestion form
Tom,
The error is bad, I guess it comes from get_all_biblios_iterator.
What are you developer skill? I'd try to know if it comes from wrong/bad
data from a record, or something else.
It seems that you are back to version 7 ("To be compatible with 7.0..." in
the logs)?
You can certainly ignore
e 2020 às 10:28, Jonathan Druart
> escreveu:
>>
>> Tom,
>>
>> The error is bad, I guess it comes from get_all_biblios_iterator.
>> What are you developer skill? I'd try to know if it comes from wrong/bad
>> data from a record, or something else.
>>
>> I
What version of Elasticsearch is known to work?
>
> Tom
>
> On Fri, Mar 20, 2020 at 9:27 AM Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Tom,
>>
>> The error is bad, I guess it comes from get_all_biblios_iterator.
>> What are you develop
Hi Peter,
The foreign key is on branchcode, not branchname.
Regards,
Jonathan
Le mer. 20 mai 2020 à 14:44, Peter Korsten a écrit :
>
> Hi,
>
> First message on this list. My company is installing a Koha installation
> for a customer, and I've been graced with the task. Everything is working,
>
If you find a bug the placing a hold on, it's a known bug that will be
fixed soon, see bug 25556.
Le ven. 22 mai 2020 à 14:45, Renvoize, Martin <
martin.renvo...@ptfs-europe.com> a écrit :
> Hi all,
>
> As we've got a number of improvements in the translations and packaging
> processes in this
It's not stuck at 17.12.00.000 (Tē tōia, tē haumatia), but the next
one: 17.12.00.001 (Bug 19724 - Add [deleted]biblio_metadata.timestamp)
It can be a bit long depending on the size of your DB. Try again and
be patient :)
Le ven. 11 sept. 2020 à 09:57, vinod mishra a écrit :
>
> Hello
>
> Why
Late hi!
Yes Nigel, your upgrade steps are exactly what need to be done.
However step "10" must be "restart all the things", which is:
memcached, apache2 and plack.
And, optionally, 11. check the about page if everything is ok ("server
information" and "system information" tabs)
Enjoy the new
Hello Vinod,
Yes it's a known bug, there is a javascript syntax error on the page.
See bug 26361
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26361
Hopefully we are going to release new versions for 20.05.x and 19.11.x
(which is affected too).
Regards,
Jonathan
Le sam. 5 sept. 2020
Alvaro,
There is a missing commit in 19.05.09. The one to tell the new version.
That's why you see 19.05.08 everywhere but don't worry you have the
patches from 19.05.09.
Regards,
Jonathan
Le sam. 5 sept. 2020 à 22:31, Alvaro Cornejo
a écrit :
>
> Hi Tomas,
>
> Thanks for your answer.
>
>
Hello Stephan,
Can you confirm the file does not exist? Can you try to (re)install
the de-DE language files?
`koha-translate --install de-DE`
To "reset the language" you need to remove the "language" cookie, but
I would not recommend continuing the installation if it crashed before
the end of
This is a temporary (given its name) directory used by Zebra. It looks
like you can remove it, but I have really no idea why it's so big.
Le lun. 5 oct. 2020 à 11:29, vinod mishra a écrit :
>
> Hello
>
> I found the size of file "tmp" is very high at
> /var/lib/koha/library/biblios/tmp which
Hello everybody,
Here is the timeline I plan to follow for the 20.11 release:
* Oct 30th - "Soft" feature freeze, nothing big or with high risk of
side-effects will be included into the final release if not marked as
Passed QA
* Nov 3-6 - "Hard" feature freeze, nothing considered as an
Hi Tomasso,
Can you open a new bug report and describe how we could simply
recreate the problem?
If a memcached restart is missing it's a bug somewhere.
Regards,
Jonathan
Le mer. 26 août 2020 à 22:53, tommaso spazzali a écrit :
>
> Thanks Alvaro,
>
> I was sure my backup was complete (I
Hello,
No, the tool only modifies the due date of the issue(s), nothing else.
Regards,
Jonathan
Le dim. 23 août 2020 à 08:44, vinod mishra a écrit :
>
> Hello
>
> Please confirm the " batch_extend_due_dates" option under tool also waive
> off the files? I mean the fine accumulated due to
You can move it at the top of the page with, in IntranetUserJS :
var div = $("#area-pending").parent().parent();
$(div).insertBefore($(div).prev());
Le sam. 15 août 2020 à 00:10, Alvaro Cornejo
a écrit :
>
> Hi
>
> Is there a way to move/duplicate the pending notification area to, for
> example
You certainly need to rebuild the Elasticsearch index. Use the
koha-elasticsearch command.
Le lun. 17 août 2020 à 16:54, Luis Moises Rojas
a écrit :
>
> Hello,
> We have Koha 19.11.08.000 on ubuntu 18.04.1 LTS, zebra version Zebra
> 2.0.59
> We want to upgrade to zebra 2.1.14 to see if we can
Hum, weird, can you restart memcached (then koha-common) to see if it
fixes the problem?
Le mer. 30 sept. 2020 à 15:03, tommaso spazzali a écrit :
>
> Hi everybody
>
> I have installed italian (it-IT) package in my Koha 20.05 on Ubuntu 20
>
> but
>
> in the preference tab i18n_l10n
>
> I have
Hi Elaine,
The biblioitems.marcxml field has been moved to biblio_metadata.metadata.
Does this query work as you want:
SELECT CONCAT('',b.biblionumber,'')
AS biblionumber
FROM biblio b
LEFT JOIN biblioitems bi ON b.biblionumber= bi.biblionumber
LEFT JOIN biblio_metadata bm ON
Hello Kerrie,
I am not sure this is what you want, but if you create a SQL report
with this query you will see the patrons with outstanding loans:
SELECT b.borrowernumber, concat(b.surname, ' ', b.firstname), count(*)
FROM issues
LEFT JOIN borrowers b on b.borrowernumber=issues.borrowernumber
l
> relationship divorced from spiritual is body without soul" -- Mahatma Gandhi
>
>
> On Wed, Jul 22, 2020 at 1:14 PM Jonathan Druart
> wrote:
>>
>> Hi Vinod,
>>
>> The bug you mention has been fixed by bug 20783
>> https://bugs.koha-community.
Hi Vinod,
The bug you mention has been fixed by bug 20783
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20783
Regards,
Jonathan
Le mer. 22 juil. 2020 à 09:15, vinod mishra a écrit :
>
> Dear All
>
> I know koha 16.11.11 is not a supported version but can anyone confirm if
> YouTube
t; *q *Recycle always / Recicla siempre / Recyclez toujours
> P Print only if absolutely necessary / Imprime solo si es necesario /
> Imprimez seulement si nécessaire
>
>
> Le mar. 21 juil. 2020 à 02:38, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> a écrit :
>
Hi Victor,
It's coming from this string:
https://translate.koha-community.org/pt_BR/20.05/translate/pt-BR-staff-prog.po#search=CAN_user_tools_manage_csv_profiles=source,target
It has been updated 7 hours ago so I think it's fixed (for the next release).
If you want to patch locally you must edit
Hello Cindy,
We faced this error for the table borrowers (bug 24986).
I am quite surprised you got it for the branches table, especially for
a "DROP COLUMN" statement.
Do you have a ton of entries in this table?
Regards,
Jonathan
Le mer. 29 juil. 2020 à 19:05, Cindy Murdock Ames a écrit :
>
>
did you enable HTML5MediaEnabled ?
Le mer. 29 juil. 2020 à 20:38, vinod mishra a écrit :
>
> Hello David
>
> We have videos on Intranet and in MP4 format, but it seems current
> provision is for YouTube only and it fetches/embed the video nicely in Koha
> but not mine on Intranet.
>
> Please
Hi Charles,
Did you try the script misc/migration_tools/remove_unused_authorities.pl?
Regards,
Jonathan
Le mar. 4 août 2020 à 11:02, Charles Kelley a écrit :
>
> Hello, all!
>
> I have been trying to detect, isolate, and delete orphaned authority
> headings, i.e., authority records to
Hi Elaine,
Are you sure you get a "404 not found" on the same bibliographic
records when you tried from different computers?
What you describe is similar to bug 25826.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25826
Regards,
Jonathan
Le jeu. 6 août 2020 à 18:34, Elaine Bradtke
This is a known bug for 20.05.
libcpan-meta-perl must be version 2.150010. If not you can try
`sudo apt install libcpan-meta-perl`. Better would be to upgrade the
system of course.
Le jeu. 6 août 2020 à 02:23, zefanja a écrit :
>
> Hi,
>
> > Hi Stephan, which exact version of Koha are you using?
Hello devs,
I have been in touch with Biblibre's sysop, Laurent. We are planning
an upgrade of the mailing list server (move), in order to fix the
problems we are facing for several months.
It will make all the mailing lists listed there unavailable:
Hi Stephan, which exact version of Koha are you using?
Le mer. 5 août 2020 à 16:26, zefanja a écrit :
>
> Hi,
>
> if I enter an ISBN in "Search the catalog", on the next page, the
> "Z39.50/SRU search" button is not working (it does not open the popup
> for the Z39.50/SRU search). In the web
uage:
>
> Uncaught SyntaxError: expected expression, got ';' search.pl:636:29
>
> (when I enter an ISBN in "Search the catalog", on the next page, the
> "Z39.50/SRU search" button is not working (it does not open the popup
> for the Z39.50/SRU search).)
>
> Regar
It's done now :)
Le ven. 7 août 2020 à 15:26, Jonathan Druart
a écrit :
>
> Hello devs,
>
> I have been in touch with Biblibre's sysop, Laurent. We are planning
> an upgrade of the mailing list server (move), in order to fix the
> problems we are facing for several months.
&g
Hello José,
Set the syspref SessionStorage to "MySQL DB" instead of temporary files.
Also you should upgrade to the latest 18.11 (v18.11.16).
Regards,
Jonathan
Le mer. 17 juin 2020 à 02:32, Jose Ricardo Quaglio
a écrit :
>
> Hello everybody,
>
>
>
> Again, the Koha version 18.11.03.000 server
Hello everybody,
The Koha Community is proud to announce the release of Koha 20.05.01
This is a maintenance release.
The full release notes can be found at:
https://koha-community.org/koha-20-05-01-released/
Debian packages will be available shortly.
Thanks to everyone involved,
Jonathan (on
Hi Monica,
How did they upgrade? Using the debian packages?
They should make sure the services have been restart correctly:
sudo service memcached restart ;
sudo service apache2 restart ;
sudo service koha-common restart;
If it does not fix the problem, edit $KOHA_CONF and add (if
Hello Nirakar,
You must use koha-foreach, so you (1) solution.
The relevant error is "Connection error from localhost on port 25 ()
at /usr/share/koha/bin/cronjobs/process_message_queue.pl line 92."
Make sure your MTA is configured correctly, and running on port 25.
You can use the sendmail
Hi David,
It should be quite fast, like ~1 minute.
Did you try to extend the value of the Apache server's timeout?
Regards,
Jonathan
Le mar. 23 juin 2020 à 19:19, David Schaller
a écrit :
>
> Hello,
>
> I have set up a server with Koha 20.05 and made it as far as the first
> several screens of
TQT - Vice-recteur chargé de la coopération
> internationale - Vice-Rector in charge of International Cooperation
> Web: http://thanglong.edu.vn/
>
>
> Vào Th 3, 9 thg 6, 2020 vào lúc 19:35 Jonathan Druart
> đã viết:
>>
>> Hi everybody,
>>
>> IMPORTANT
Hello Tigran,
Yes that must be possible. I am adding Bernardo, he is in charge of
the translation part.
In case you don't receive answer here, there is a more appropriate
mailing list for translation: koha-transl...@lists.koha-community.org
Regards,
Jonathan
PS: I also added a subject to this
Hello,
mariadb-server is in 'universe'. Edit your sources.list file and make
sure you have "universe"
https://help.ubuntu.com/community/Repositories/Ubuntu
Regards,
Jonathan
Le lun. 15 juin 2020 à 10:49, Farasat Shafi ullah
a écrit :
>
> Kia Ora every one
>
> I was trying to test Koha 20.05
Hi Mark,
You should have restarted/flushed memcached first. The koha-conf file
is cached there.
Regards,
Jonathan
Le ven. 5 juin 2020 à 14:27, Mark Alexander a écrit :
>
> It turned out that the configuration issue was a missing tmp_path
> entry in koha-conf.xml. There was some information
Hi Dawson,
There was a change in 20.05. Before we silently ignored wrong
permissions, now we force the logging system to be setup correctly
(bug 25172)
We should certainly deal with that problem during the upgrade process.
I will see what can be done.
The solution suggested by Alvaro is the
personal thanks to a fantastic team.
>
> Special thanks go out to Mason James, Tomas Cohen and Jonathan Druart, all
> who stepped in during the final weeks of the cycle to ensure the packaging
> would work as expected for Debian 10 as well as finding and fixing bugs right
> up to th
Hi Victor,
Try:
$ chown -R USER:USER /var/log/koha/INSTANCE
Regards,
Jonathan
Le mar. 9 juin 2020 à 14:20, Victor Barroso Oliveira
a écrit :
>
> Good Morning
> After updating to 20.05 this error appeared when trying to save a record
>
> "Can't open /var/log/koha/biblio/opac-error.log
Hello Fadhili,
Have you been through the update database process? Did you notice an
error when you upgraded?
You have a missing table. I would suggest to use a backup of your
database, restart memcached then koha-common and hit the intranet
page.
You should then see the upgrade page.
If none of
By any chances do you still have the log of the upgrade process?
Can you check if you have the column 'anonymized' in the 'borrowers' table?
Le lun. 8 juin 2020 à 11:52, Fadhili Ngalawa a écrit :
>
> Thank you so much Jonathan Druart for your quick response.
> I added the columns
Hi Alvaro,
Can you confirm you tried the following cmds:
koha-plack --enable INSTANCE
koha-plack --start INSTANCE
service apache2 restart
Regards,
Jonathan
Le jeu. 4 juin 2020 à 03:32, Alvaro Cornejo a écrit :
>
> Hi
>
> We have noticed slow koha since last update of koha
>
> Koha
It's known to work with MariaDB 10.1 and 10.3, not the latest MariaDB (10.5.4)
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26042
This is the versions our CI are running, I cannot tell for 10.4
Le lun. 27 juil. 2020 à 15:35, Isabel Pineda a écrit :
>
> Hi. I don't want to shred
bian 9 or
> Ubuntu 18.
>
> It works.
>
> Philippe Blouin,
> Directeur de la technologie
>
> Tél. : (833) 465-4276, poste 230
> philippe.blo...@inlibro.com
>
> inLibro | pour esprit libre | www.inLibro.com
> On 2020-07-27 10:07 a.m., Jonathan Druart wrote:
>
&g
Hi Alvaro,
Which terms do you use for the search? What is the full openlibrary url?
Regards,
Jonathan
Le jeu. 16 juil. 2020 à 01:39, Alvaro Cornejo
a écrit :
>
> Hi
>
> Since some time, I'm getting an error when enabling openlibrary searches:
>
> I get this on chrome debugger:
>
>
Stay safe / Cuídate/ Reste sécurisé
> 7 Switch off as you go / Apaga lo que no usas / Débranchez au fur et à
> mesure.
> q Recycle always / Recicla siempre / Recyclez toujours
> P Print only if absolutely necessary / Imprime solo si es necesario /
> Imprimez seulement si nécessaire
&g
Hello Vinod,
You lost all the "metadata"/marcxml for the deleted bibliographic records.
If you want to recover them you will have to use a backup and rerun
the update database process.
Before you do it, make sure you don't have several times the same
biblionumber in the deletedbiblioitems table.
tral Library (BPCL),
>> > NIT Rourkela,
>> > Sundergadh-769008,
>> > Odisha,
>> > India.
>> > Mob:91+9439420860
>> > ORCID ID: http://orcid.org/-0003-4666-7874
>> >
>> > "Spiritual relationship is far more precious
It seems that we assume permanent_location must be set.
I would recommend updating your data and set the
items.permenant_location=items.location when it's not defined.
Le mar. 11 août 2020 à 17:47, Stephen Graham a écrit :
>
> Hi All - like a lot of libraries we've been testing the Cart
Hello Scott,
The relevant part is:
"Configuration not defined at /usr/share/perl5/Log/Log4perl/Config.pm line
579."
Can you confirm you don't have a "log4perl_conf" entry in the
koha-conf.xml file that is defined and pointing to a valid log4perl
configuration file?
You should have one to make
Hello everybody,
It is with great pleasure that the Koha community announces the
release of Koha 20.11, a major release of the Koha open source
integrated library system.
Read the full release notes here:
https://koha-community.org/koha-20-11-released/
The Debian packages for this new version
501 - 600 of 763 matches
Mail list logo
