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] -. 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 -optional:
-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).
-Log into admin account of first company. If -you use a theme other than the standard 3 (aqua, cool or default), -switch to one of these before going further.
+Updatea. Source files update
+Extract distribution zip/tar.gz file in empty directory, and copy all the files to your FrontAccounting directory overwriting old files. If it is major release upgrade you can skip next step and go directly to cleanup.
+b. Configuration files update
+Compare new config.default.php -file with the old +file with the +old config.php and add all new settings (if any).
-[<FA -2.2beta]
-$show_users_online = 0;
-$def_print_destination -= 0;
-$dflt_date_fmt=0;
-$dflt_date_sep=0;
-$table_style,table_style2 -changed
-[<FA -2.3beta]
-$alternative_tax_include_on_doc=0;
-$suppress_tax_rates = 0;
-[<FA -2.3RC1] -
-Application version -information and a couple of other private FA variables are stored in -version.php -file. The -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 -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.
-This step can be skipped
+The following variables has been moved from config.default.php into sys_prefs table: 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
+FrontAccounting version 2.4 or later. Before database upgrade is
done on all company databases backup file is created automatically to
enable database restore after failure. After major version
@@ -117,39 +88,9 @@ restore databases from backup and retry normal installation. To run
upgrade in forced mode check box 'Force Upgrade', and press 'Upgrade
System' again. Remove or rename install folder in main FrontAccounting directory.
- After upgrade is installed you can remove files obsoleted by new
-FrontAccounting version. Also old, unused settings can
-be removed from config.php
-file. a.
-Source files cleanup [<FA
-2.2beta] /includes/reserved.inc
-– removed. [<FA
-2.1]
- /admin/db/v_banktrans.inc
-- removed b.
-Config.php cleanup
- [<FA
-2.2RC1]
- $security_headings,
-$security_groups arrays – moved to database (see Access Setup)
-
- $def_app – moved
-to user configuration in database. $version
-– moved to version.php
-file. Remove Remove or rename install folder in main FrontAccounting
+directory.
+ During upgrade process new features are initialized to default
status, and sometimes old settings are also changed to conform with
new security policy. This automatic process is designed to be as
@@ -157,8 +98,8 @@ 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_zero_lines_amount = 1;
+$show_po_item_codes = 0;
+$accounts_alpha = 0;
+$loc_notification = 0;
+$print_invoice_no = 0;
+$allow_negative_prices = 1;
+$print_item_images_on_quote = 0;
+
+These values can be maintained in Setup tab -> System and GL Setup.
+
+The following variables has been moved from config.default.php into sys_refs table:
+
+$alternative_tax_include_on_docs = 0;
+$suppress_tax_rates = 0;
+
+These values can be maintained in Setup tab -> Company Setup.
+
+The following variables has been moved from config.default.php into users table:
+
+$save_report_selections = 0;
+$use_date_picker = 1;
+$def_print_destination = 0;
+$def_print_orientation = 0;
+
+These values can be maintained in Setup tab -> Display Setup or Preferences.
+
+ Please also remove these variables from your existing config.php file
+2. Database upgrade
+3. Final cleanup
-4. New features configuration
+4. New features configuration
-
+
+
\ No newline at end of file