Hi,
a lot of database changes are also about adding data like new system
preferences.
But there is another way to see where your database is actually at:
Administration > System preferences > Tab Local Use > Version
Entries in Local use cannot be searched for, so you need to navigate to it.
A
¡Hola Tomas!
see below
Saludos, Harald
Am 01.04.22 um 17:57 schrieb Tomas Cohen Arazi:
Those lines are only printed if it upgraded the db correctly. So it
doesn't really look like it stopped.
What is pointing you to the conclusion something went wrong?
I have upgraded koha-common to versio
Those lines are only printed if it upgraded the db correctly. So it doesn't
really look like it stopped.
What is pointing you to the conclusion something went wrong? Is it that
Koha keeps prompting you too do an upgrade? If such is the case then it is
a caching issue and Mason's advice should fix
hi Harald
try the following commands...
$ sudo /etc/init.d/memcached restart
$ sudo koha-upgrade-schema myinstance
if it fails, it should show some errors
On 31/03/22 11:15 pm, Harald Schaefer wrote:
Dear all,
now I am promoted from a plain KOHA user to the system administrator of the
comp
Hi,
I am not sure why it stopped if the installed version is 21.11.03. Maybe
someone else has an idea?
Katrin
On 31.03.22 20:48, Harald Schaefer wrote:
Thanks for the answer.
I omitted same parts of the test run, it ends with
Upgrade to 21.11.02.004 [17:49:53]: Bug 29943 - Fix typo in
NOTIF
Thanks for the answer.
I omitted same parts of the test run, it ends with
Upgrade to 21.11.02.004 [17:49:53]: Bug 29943 - Fix typo in
NOTIFY_MANAGER notice
Upgrade to 21.11.03.000 [17:49:53]: Koha 21.11.03 release
KOHA 21.11.03 is the release I want to upgrade to
My question is:
Is it sav
Hi,
actually the test run is the one that looks a little odd:
Upgrade to 21.06.00.000 [17:49:33]: Increase DBRev for 21.06
Run, rabbit run.
Dig that hole, forget the sun,
And when at last the work is done
Don't sit down it's time to dig another one.
Is the first
se and see if that fixes the schema errors.
Scott
-Original Message-
From: Jonathan Druart
Sent: Thursday, January 07, 2021 3:44 AM
To: skaman...@gmail.com
Cc: koha
Subject: Re: [Koha] Database upgrade error from 20.06.00.000 to 20.11.00-1
Hello Scott,
The relevant part is:
"Co
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 thin
: koha@lists.katipo.co.nz
Subject: Re: [Koha] Database Upgrade
HI Mohamad,
I don't think Koha will be able to pick up your changes to the items
table without making more changes to Koha's code.
But there is another way of adding more information/custom fields to the
items table: In items the
t:* Thursday, March 7, 2019 10:05:24 PM
*To:* koha@lists.katipo.co.nz
*Subject:* Re: [Koha] Database Upgrade
HI Mohamad,
I don't think Koha will be able to pick up your changes to the items
table without making more changes to Koha's code.
But there is another way of adding more informa
HI Mohamad,
I don't think Koha will be able to pick up your changes to the items
table without making more changes to Koha's code.
But there is another way of adding more information/custom fields to the
items table: In items there is the column more_subfields_xml. This is
used to store addition
Nevermind - it was a patch that I was testing (not the fetch) and that
patch has an updatedatabase with a real number in it - that should not
happen!
Nicole
On Wed, Aug 3, 2011 at 9:07 AM, Nicole Engard wrote:
> I just did a fetch on my install of master and got the upgrade db
> page. But this
13 matches
Mail list logo
