FrontAccounting Update

X-Git-Url: https://delta.frontaccounting.com/gitweb/?a=blobdiff_plain;f=update.html;h=51dd4709eb4041397a4cfbc11560f0a4ada26020;hb=3b06c6c4718610a408cae2e9b76c3134ca30b84c;hp=5a87aafd2b4da3c9d7e8c162163a5e47c1740291;hpb=388b76390023fb33ed063682cb2ddb3b14a9ce15;p=fa-stable.git diff --git a/update.html b/update.html index 5a87aafd..51dd4709 100644 --- a/update.html +++ b/update.html @@ -1,60 +1,105 @@ - - - - - - FrontAccounting Update - -

FrontAccounting Update

-
-
- -

Important Notes

- -

You can easily upload all the files to your installation folder on the -server overwriting the existing files, if you take these important -steps: -
1. Backup (download) the following files to another folder: -
  1. config_db.php (contains information about the companies and -connection info). -
  2. config.php (contains various settings. You only need to -backup this file if you have done manually changes to it. -
  3. /lang/installed_languages.inc (contains information about the -installed languages) -
  4. /modules/installed_modules.php (contains information about -installed modules, only vers. 1.1) -
  5. if you have made changes to other files, like themes or so, backup -these files too.
  - -
2. Upload all the new files. -
3. Restore the files mentioned in #1. Be careful with - config.php. Look into variances. There might be new variables in -the new version. It might be easier to manually change your former values in -the new file. -
4. Rename or remove the /install folder (you have already performed the install -process earlier).
-
If there are changes to the database structure, please run the script update_db.php -from FrontAccounting root installation, Enter the database user and the -password and choose the update script from the local harddisk.
When updating release 1.XX to release 2.0, you must run the update_db.php script and select the file - alter.sql - that are located in the sql folder. You must -do this, before entering FrontAccounting! -Enter the database user and the password and choose the alter.sql -script. Do the same for the alter2.sql script. If you have -already updated release 2.0 Beta, you can just run the alter2.sql script.
You must also manuelly ensure that you have write permission to the new folder /company .
There are no database changes during a major and minor release. Like from 2.0 to 2.0.1 - 2.0.5 .

- -

+ + + + + + + + + +FrontAccounting Update + + + + +

***Front*Accounting +Update**

1. Application files update

+ +

a. 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 +config.php and +add all new +settings (if any). +

+ +The following variables has been moved from config.default.php into sys_prefs table:
+
+$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

This step can be +skipped +for small version updates i.e. when you have already installed +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 +upgrade overwriting files in first step makes the system unaccessible +for all users but site admin, who have to run upgrade procedures to +update all company databases to the new version provided with the +release. After logging to administrator account of first installed +company go directly to Setup/Software Upgrade screen, mark all +subsequent 'Install' checkboxes and press 'Upgrade System'.

If something goes wrong during +upgrade, you can eventually try forced upgrade option. Forced upgrade +ignores some smaller errors which can arise during upgrade due to +some exotic database configuration. This is depreciated option, so +first read error messages if any, try to fix signalized problems, +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. +

4. New features configuration

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 +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.

+ +

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