Re: Upgrade issues from 1.2.21 to 1.3.5

On 3 December 2011 22:16, Chris Travers <..hidden..> wrote:

On Sat, Dec 3, 2011 at 1:10 AM, Robert Fraser <..hidden..> wrote:
> Hi All
>
> I am having trouble upgrading to 1.3
>
> I run through the process, and it appears that all the tables in the
> database have been truncated - I can log into LedgerSMB after the upgrade
> and there's no transactions, no chart of accounts etc.
>
> I am testing this on a freshly installed VM with a copy of my live database
> ( Debian Squeeze, Postgresql 8.4)
>
> I am unsure what needs to be entered to commence the db upgrade - I used
>
> * NZ for the country code (New Zealand)
>
> * and two unused account numbers for the AR and AP fields - I wasn't sure
> if they'd be created automatically or not.

No, these should be your existing accounts.

Ah, OK.

One common cause of problems is a lack of contrib modules (locate tablefunc).

No, I had this parameter correctly entered, but once I put in the correct AR and AP accounts the latest import seems to have worked fine

Will now do some side by side comparisons against my 1.2.21 installation.

Is this part of the upgrade documented? I couldn't find anything outside of a previous list email that mentioned what should be entered in some of those fields. I'd be happy to write something up if it helps.

Cheers
Rob