FrontAccounting Update

X-Git-Url: https://delta.frontaccounting.com/gitweb/?a=blobdiff_plain;f=update.html;h=d88329d564854199c1a6f954c605a235be193d12;hb=161bba0a7475c63af6951cb1fc465747926f51bf;hp=5f43f50a9f7fdc212ca4b001eb9779cd68447b6d;hpb=f7ecb3bcb857eaedd049c6d0307c470fcf7d3f4d;p=fa-stable.git diff --git a/update.html b/update.html index 5f43f50a..d88329d5 100644 --- a/update.html +++ b/update.html @@ -1,60 +1,288 @@ - - - + + +FrontAccounting Update + + + +

***Front*Accounting +Update**

Important Notes for release 2.3.22.

New global flags in config.php (config-default.php):

+/* Show average costed values instead of fixed standard cost */ In Enventory Valuation Report.
+$use_costed_values = 0;
+
+/* Print Item Images on Sales Quotations. Set to 1 if so. */
+$print_item_images_on_quote = 0;
+

Important Notes for release 2.3.21.

- FrontAccounting Update - -

FrontAccounting Update

-
-
+

Crucial security patches:

Important Notes

+This version consists of crucial security patches and this applies especially to all publicly available servers,
+ f.i. installations which are run in not fully trusted environment like public demos, shared accounts or SAAS.
+

New global flags in config.php (config-default.php):

+/* Whether to allow sending new password by e-mail */
+$allow_password_reset = false

Important Notes for release 2.3.20.

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)
  5. installed_extensions.php (contains information about installed extensions to the menu system)
  6. if you have made changes to other files, like themes or so, backup -these files too.
  +
  Crucial security patches:
  +This version consists of crucial security patches and all guest FA +installations (I mean whenever FA is run in not fully trusted +environment) should be updtaed.
  +
  Important Notes for release 2.3.17.
  -
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).
-
When -updating release 2.0.X to release 2.1.X, you must immediately -login on company 0, the first company you created, as admin -(called the superadmin). If you use a theme other than the standard 3, -aqua, cool or default, switch to one of these before going further. You -can download a new one of the new themes on the download page. Go -to the 'Setup' tab and run 'Software -Upgrade'. -Mark the checkbox 'Install' and press 'Upgrade System'. This will -upgrade ALL your companies.
If something goes wrong during upgrade, you can enter here again and try 'Force Upgrade', and press 'Upgrade System' again.
There are no database changes during a major and minor release. Like from 2.1 to 2.1.1 - 2.1.5 .

New global flags in config.php (config-default.php):

$xr_providers = array("ECB", "YAHOO", "GOOGLE", "BLOOMBERG");
+$dflt_xr_provider = 0;
+
+

$xr_provider_authoritative = false;
+

Important Notes for release 2.3.16.

New global flags in config.php (config-default.php):

*/
$sort_sales_items = false;

/*

*/
$clear_trial_balance_opening = false;

Important Notes for release 2.3.14.

New global flags in config.php (config-default.php):

$def_print_orientation += 0;

Important Notes for release 2.3.13.

New global flags in config.php (config-default.php):

$no_check_edit_conflicts += 0;

Important Notes for release 2.3.12.

New global flags in config.php (config-default.php):

$text_company_selection

$hide_inaccessible_menu_items

$login_delay

$login_max_attempts

Important Notes for release +2.3.5.

Recurrent +Invoices

Now +the Last Sent day is stamped with the former Last Sent (or Begin date +the first time) + months + days. Before the Last Sent day was stamped +with tthe creation date (today). The Invoice date is still todays date. +
If you for some reason want to make a pause in the +recurrent +invoices, you can now edit the Last Sent day in the Management section +of Sales tab.
Before the days value, together with a month +value, decided which day in the month the invoice was due.. + This +does not work now. You can change the day in the +month you +want the recurrency to happen by setting the Last Sent day with the new +day in the Management section.
If you create a new Recurrent Invoice the Beginning date +can be set to the day in the month you want the recurrencies to be due.

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

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

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

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

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

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.

+
+

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

FrontAccounting +Update

Important Notes for release 2.3.22.

New global flags in config.php (config-default.php):

Important Notes for release 2.3.21.

Crucial security patches:

Important Notes

New global flags in config.php (config-default.php):

Important Notes for release 2.3.20.

Crucial security patches:

Important Notes for release 2.3.17.

New global flags in config.php (config-default.php):

Important Notes for release 2.3.16.

New global flags in config.php (config-default.php):

Important Notes for release 2.3.14.

New global flags in config.php (config-default.php):

Important Notes for release 2.3.13.

New global flags in config.php (config-default.php):

Important Notes for release 2.3.12.

New global flags in config.php (config-default.php):

Important Notes for release +2.3.5.

Important Notes

1. Application files update

2. Database upgrade

3. Final cleanup

4. New features configuration

***Front*Accounting +Update**