Upgrading

Why does the acc_trans table have fewer lines after upgrading to 1.7?

Submitted by ehu on Tue, 08/27/2019 - 13:11

Short answer: Due to differences in the database schema in relation to storing foreign currency transactions.

Long answer: The database schema before 1.7 required 2 database rows in the acc_trans table to store functional currency and foreign currency amounts. As of 1.7, the schema stores these two amounts - which relate to the same journal line - into one database row. When migrating data from the old schema to the new one, the migration routine tries hard to identify pairs of rows which can be combined into a single row in the new schema.

Upgrading LedgerSMB 1.6.x to 1.6.y

Submitted by ehu on Fri, 07/27/2018 - 08:19

Upgrading tarball installations

There are two steps to upgrading a LedgerSMB 1.6.x installation to 1.6.y (x smaller than y):

  1. Upgrade the software
  2. Upgrade the company database

The last step has to be executed for each company database that's set up.

Note that all the steps below are prefixed with the 'sudo' command, but these can be executed as 'root' directly as well.

Upgrading the software

This is by far the easiest part. These are the steps to go through, assuming an installation from tarball:

Upgrade to LedgerSMB 1.6 (from 1.5 or 1.4/starman)

Submitted by ehu on Sat, 05/26/2018 - 03:19

Upgrading tarball installations

There are two steps to upgrading a LedgerSMB 1.5.x to 1.6:

  1. Upgrade the software
  2. Upgrade the company database

The last step must be executed for each company database that's set up.

These steps also apply when upgrading a 1.4 installation running Starman. To upgrade 1.4 installations not running on Starman, or to upgrade from earlier versions, please see Upgrading to Ledgersmb 1.5. Note that the default configuration for 1.4 runs CGI, not Starman.

Upgrading LedgerSMB 1.5.x to 1.5.y

Submitted by ehu on Tue, 02/28/2017 - 08:38

Upgrading tarball installations

There are two steps to upgrading a LedgerSMB 1.5.x installation to 1.5.y (x smaller than y):

  1. Upgrade the software
  2. Upgrade the company database

The last step has to be executed for each company database that's set up.

Note that all the steps below are prefixed with the 'sudo' command, but these can be executed as 'root' directly as well.

Upgrading the software

This is by far the easiest part. These are the steps to go through, assuming an installation from tarball:

Upgrading to LedgerSMB 1.5

Submitted by ehu on Fri, 12/23/2016 - 13:27

Before starting to update to 1.5, the following are differences to be aware of between 1.4 and 1.5:

  • JavaScript in the browser
  • Additional data constraints
  • PSGI / Apache configuration
  • Printed document templates (e.g. invoice templates)
  • Database schema maintenance

See below for explanations of each of these differences.

 

Important note: before trying to migrate your database to a new version of LedgerSMB, create a backup of the database!