FrontAccounting forum — update from 2.2.5 to 2.3 rc3 issue

Re: update from 2.2.5 to 2.3 rc3 issue

null@example.com (ACHDI) — Thu, 31 Mar 2011 12:43:45 +0000

NIce to know you all.. My name : Achdi.. , Thank you for accepting me in this forum..

wbaileynzl : Thanks for the information , but how to manually loaded the sql script line by line to remove the Note notification

Re: update from 2.2.5 to 2.3 rc3 issue

null@example.com (wbaileynzl) — Wed, 01 Dec 2010 02:24:15 +0000

Resolved thank you. manually loaded the sql script line by line through phpmyadmin

Re: update from 2.2.5 to 2.3 rc3 issue

null@example.com (wbaileynzl) — Tue, 30 Nov 2010 23:14:32 +0000

Now we are getting message: "System is blocked after source upgrade until database is updated on System/Software Upgrade page" However in Software Upgrade we get: "2.3 Upgrade from version 2.2 to 2.3 alter2.3.sql Installed" How do we move forward and remove the block please?

Re: update from 2.2.5 to 2.3 rc3 issue

null@example.com (itronics) — Tue, 30 Nov 2010 09:53:06 +0000

This message is displayed when some database scheme changes planned for this release are already found in db. This message can appear when user has done partial update to some early CVS version before upgrade to 2.3RC, but should not appear for clean upgrade from 2.2.x to 2.3RC.
There were a lot of database scheme changes between 2.2 and 2.3 versions, but 4 things are tested on Upgrade Software page and are considered as upgrade milestones. Those are:
. type, id key on comments table
. sys_pref table
. sales_order.payment_terms field
. purch_order.tax_included field

If some of those changes exists (but not all) the database is considered as partially upgraded and need manual intervention.

You will find list of all changes mades during software upgrade in:
. alter2.3.sql
. alter2.3rc.slq
. alter2.3.php contains code which cannot be easily performed via simple sql queries.

Hope it helps.
Janusz

update from 2.2.5 to 2.3 rc3 issue

null@example.com (nickMolhoek) — Tue, 30 Nov 2010 06:18:23 +0000

A client was using front accounting 2.2.5 but several bugs were causing problems, so we attempted to update to the latest version "2.3 RC3". This has apparently partially worked, but failed on the database update step. On the "software update" page next to 2.3 it says:

Upgrade from version 2.2 to 2.3 alter2.3.sql Partially installed (3/4)

and then underneath the table:

Database upgrades marked as partially installed cannot be installed automatically. You have to clean database manually to enable them, or try to perform forced upgrade.

I don't know where to start manually cleaning the database, what elements would cause problems for this updated version?

Any help would be greatly appreciated.