X-Git-Url: https://delta.frontaccounting.com/gitweb/?a=blobdiff_plain;f=update.html;h=4b7f7f78ee07b42580651e1de701bf2a9ebb6c8b;hb=5d8f36d15260bfd9215315935af86b7d96065489;hp=3af13a0ed2c90e66fd6986353990c285d0cd2036;hpb=90b3d069d96b99671af51726e2953352738abb75;p=fa-stable.git diff --git a/update.html b/update.html index 3af13a0e..4b7f7f78 100644 --- a/update.html +++ b/update.html @@ -1,49 +1,191 @@ - - - FrontAccounting Update - - - -

FrontAccounting -Update

-

Important Notes for release 2.3.5.

Change in the behaviour of Recurrent Invoices.

Important Notes

Upgrade process can be done only by administrator of the first company created during FrontAccounting installation. This person is considered as a site admin who have granted access to potentially dangerous setup options, like Setup/Software Upgrade.

-

In the following description sections related to older FA versions are -prefixed with [color tags] +

In the following description sections related to older FA +versions are +prefixed with [color +tags] . You can skip tagged fragment safely if currently FA application is newer than the version in tag.

-

Upgrade process consists of up to four stages, some of them are +

Upgrade process consists of up to four stages, some of them +are optional:

    -
  1. Application source files update -

    -
  2. Database upgrade – this step is needed only during - upgrade which involves change in major application version number - (e.g. from 2.2.x to 2.3.x), and sometimes during upgrade from beta - release to stable version. Otherwise this step can be skipped.

    -
  3. Final cleanup – is needed when some old source files, - obsoleted by new release should be removed.

    -
  4. New features configuration – this is optional step - needed for most major releases and some minor ones. -

    -
-

Before starting upgrade ensure nobody +

  • +

    Application source files update

    +
  • +
  • +

    Database upgrade – this step is needed only during upgrade +which involves change in major application version number (e.g. from +2.2.x to 2.3.x), and sometimes during upgrade from beta release to +stable version. Otherwise this step can be skipped.

    +
  • +
  • +

    Final cleanup – is needed when some old source files, +obsoleted by new release should be removed.

    +
  • +
  • +

    New features configuration – this is optional step needed +for most major releases and some minor ones.

    +
  • + +

    Before starting upgrade +ensure nobody is using the application and make database backup for all companies. To be on safe side backup also old source files, especially those locally customized (if any).

    @@ -61,25 +203,28 @@ release upgrade you can skip next step and go directly to cleanup.

    Compare new config.default.php -file with the old +file with the +old config.php and add all new settings (if any).

    -

    [<FA +

    [<FA 2.2beta]

    -

    $show_users_online = 0;

    +

    $show_users_online += 0;

    $def_print_destination = 0;

    $dflt_date_fmt=0;

    $dflt_date_sep=0;

    $table_style,table_style2 changed

    -

    [<FA +

    [<FA 2.3beta]

    $alternative_tax_include_on_doc=0;

    -

    $suppress_tax_rates = 0;

    -

    [<FA +

    $suppress_tax_rates += 0;

    +

    [<FA 2.3RC1]

    Application version @@ -90,13 +235,27 @@ application version displayed in footer is defined in $version variable unless this is set in config.php file. If you want current release version to be displayed on every FA update just remove or comment out $version variable in config.php.

    -

    [<FA +

    [<FA 2.3RC2]

    -

    $save_report_selections  = 0;  // A value > 0 means days to save the report selections.

    [<FA -2.3]

    $save_po_item_codes  = 0;  //  show item codes on purchase order 

    $def_print_destination = 0; //  default print destination. 0 = PDF/Printer, 1 = Excel

    $alternative_tax_include_on_docs = 0; //  1 = print Subtotal tax excluded, tax and Total tax included

    $suppress_tax_rates = 0; //  suppress tax rates on documents. 0 = no, 1 = yes.

    - -

    2. Database upgrade

    -

    This step can be skipped +

    $save_report_selections + = 0;  // A value > 0 means days to save the +report selections.

    +

    [<FA +2.3]

    +

    $save_po_item_codes + = 0;  //  show item codes on purchase +order 

    +

    $def_print_destination += 0; //  default print destination. 0 = PDF/Printer, 1 = Excel

    +

    $alternative_tax_include_on_docs += 0; //  1 = print Subtotal tax excluded, tax and Total tax +included

    +

    $suppress_tax_rates += 0; //  suppress tax rates on documents. 0 = no, 1 = yes.

    + +

    2. Database upgrade

    +

    This step can be +skipped for small version updates i.e. when you have already installed FrontAccounting version 2.3.1 or later. Before database upgrade is done on all company databases backup file is created automatically to @@ -117,19 +276,21 @@ restore databases from backup and retry normal installation. To run upgrade in forced mode check box 'Force Upgrade', and press 'Upgrade System' again.

    3. Final cleanup

    -

    Remove or rename install folder in main FrontAccounting directory. +

    Remove or rename install folder in main FrontAccounting +directory.

    -

    After upgrade is installed you can remove files obsoleted by new +

    After upgrade is installed you can remove files obsoleted by +new FrontAccounting version. Also old, unused settings can -be removed from config.php +be removed from config.php file.

    a. Source files cleanup

    -

    [<FA +

    [<FA 2.2beta]

    -

    /includes/reserved.inc +

    /includes/reserved.inc – removed.

    -

    [<FA +

    [<FA 2.1]

    /admin/db/v_banktrans.inc @@ -137,12 +298,11 @@ Source files cleanup

    b. Config.php cleanup

    -

    [<FA +

    [<FA 2.2RC1]

    $security_headings, -$security_groups arrays – moved to database (see Access Setup) - +$security_groups arrays – moved to database (see Access Setup)

    $def_app – moved to user configuration in database.

    @@ -157,8 +317,10 @@ neutral for end users as possible, however sometimes site or company admin intervention can be necessary to set thing after changes to their best state. Below you will find description of new settings available after upgrade.

    -



    +


    +

    ----------------------

    -
      +
        +
      \ No newline at end of file