-FrontAccounting ERP
+
===================
FrontAccounting ERP is open source, web-based accounting software for small and medium enterprises.
interface for everyday business activity with automatic GL postings generation. This is multicurrency,
multilanguage system with active worldwide users community:
-Project web site http://frontaccounting.com
+* [Project web site](http://frontaccounting.com)
+* [SourceForge project page](http://sourceforge.net/projects/frontaccounting/)
+* [Central users forum](http://frontaccounting.com/punbb/index.php)
+* [Main code repository](https://sourceforge.net/p/frontaccounting/git/ci/master/tree/)
+* [GitHub mirror](http://github.com/FrontAccountingERP/FA)
+* [Mantis bugtracker](http://mantis.frontaccounting.com)
+* [FrontAccounting Wiki](http://frontaccounting.com/fawiki/)
-SourceForge project page: http://sourceforge.net/projects/frontaccounting/
+This project is developed as cooperative effort by FrontAccounting team and available under [GPL v.3 license](./doc/license.txt)
-Central users forum: http://frontaccounting.com/punbb/index.php
+## Requirements
-Main code repository: https://sourceforge.net/p/frontaccounting/git/ci/master/tree/
+To use FrontAccounting application you should have already installed:
-GitHub mirror: http://github.com/FrontAccountingERP/FA
+* Any HTTP web server supporting php eg. _**Apache with mod_php**_ or _**IIS**_.
+* **_PHP_** >=5.0 (version 5.6 or 7.x is recommended)
+* **_MySQL_** >=4.1 server with **_Innodb_** tables enabled, or any version on **MariaDB** server
+* **_Adobe Acrobat Reader_** (or any another PDF reader like _**evince**_) is handy for viewing reports before printing them out.
-Mantis bugtracker: http://mantis.frontaccounting.com
+## Installation
+### 1. PHP configuration checks
-FrontAccounting is available under GPL v.3 license.
+* One critical aspect of the PHP installation is the setting of **_session.auto_start_** in the php.ini file. Some rpm distributions of PHP have the default setting of **_session.auto_start = 1_**. This starts a new session at the beginning of each script. However, this makes it impossible to instantiate any class objects that the system relies on. Classes are used extensively by this system. When sessions are required they are started by the system and this setting of **_session.auto_start_** can and should be set to 0.
+* For security reasons both Register Globals and Magic Quotes php settings should be set to Off. When FrontAccounting is used with www server running php as Apache module, respective flags are set in .htaccess file. When your server uses CGI interface to PHP you should set **_magic_quotes_gpc = 0_** and **_register_globals = 0_** in php.ini file.
+* **_Innodb_** tables must be enabled in the MySQL server. These tables allow database transactions which are a critical component of the software. This is enabled by default in the newer versions of MySQL. If you need to enable it yourself, consult the MySQL manual.
+### 2. Download application files
+
+* Download and unpack latest FrontAccounting tarball from SourceForge into folder created under web server document root, e.g. **/var/www/html/frontaccounting**
+
+* If you prefer easy upgrades when new minor versions are released, you can clone sources from SourceForge project page or Github mirror e.g.:
+> # cd /var/www/html
+> # git clone `https://git.code.sf.net/p/frontaccounting/git` frontaccounting
+
+Master branch contains all the latest bugfixes made atop the last stable release.
+
+### 3. Installation
+
+Use your browser to open page at URL related to chosen installation folder. As an example, if you plan to use application locally and in previous step you have put files on your Linux box in /var/www/html/frontaccounting subfolder, just select `http://localhost/frontaccounting` url in your browser, and you will see start page of installation wizard. Follow instructions displayed during the process.
+
+During installation you will need to provide data server credentials with permissions to create new database, or you will have to provide existing database name and credentials for user with valid usage permissions to access it. You will have to chose also a couple of other options including installation language, optimal encoding for database data etc. Keep in mind that some options (like additional translations and charts of accounts) presented during installation process could be installed also later, when FrontAccounting is already in use.
+
+ After successful installation please remove or rename your install directory for safety reasons. You won't need it any more.
+
+### 4. Logging In For the First Time
+
+ Open a browser and enter the URL for the web server directory where FrontAccounting is installed. Enter the user name **admin** and use password declared during install process to login as company administrator. Now you can proceed with configuration process setting up additional user accounts, creating fiscal years, defining additional currencies, GL accounts etc. All configuration options available in application are described in [FrontAccounting Wiki](http://frontaccounting.com/fawiki/) available directly from Help links on every application page under  icon.
+
+
+## Troubleshooting
+
+If you encountered any problems with FrontAccounting configuration or usage, please consult your case with other users on [Frontaccounting forum](http://frontaccounting.com/punbb/index.php). If you think you have encountered a bug in application and after consulting other community members you still are sure this is really a bug, please fill in a report in project [Mantis bugtracker](http://mantis.frontaccounting.com) with all details which allow development team reproduce the problem, and hopefully fix it. Keep in mind, that [GitHub](http://github.com/FrontAccountingERP/FA) page is mainly passive mirror for project based on SorceForge, so posting bug reports here is at least suboptimal.
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>FrontAccounting</title></head>
-<body>
-<div><strong><span style="font-size: 20pt;"><span style="color: rgb(204, 102, 0); font-style: italic;">Front</span>Accounting
-Installation</span></strong></div>
-<h2>Pre-requisites</h2>
-<ul style="margin-top: 0pt;" type="disc">
-<li>A working HTTP web server eg. <em><strong>Apache,
-IIS</strong></em>. </li>
-<li><strong><em>PHP</em></strong>
-installed on the web server. </li>
-<li>A working <strong><em>MySQL</em></strong>
-server - with <strong><em>innodb</em></strong>
-tables enabled (see notes below) </li>
-<li><strong><em>Adobe Acrobat Reader</em></strong>
-- or another PDF reader for viewing the PDF reports before printing them out. </li>
-</ul>
-<h2>Important Notes</h2>
-<ul>
-<li>One critical aspect of the PHP installation is the setting
-of <strong><em>session.auto_start</em></strong>
-in the php.ini file. Some rpm distributions of PHP have the default
-setting of <strong><em>session.auto_start = 1</em></strong>.
-This starts a new session at the beginning of each script. However,
-this makes it impossible to instantiate any class objects that the
-system relies on. Classes are used extensively by this system. When
-sessions are required they are started by the system and this setting
-of <strong><em>session.auto_start</em></strong>
-can and should be set to 0. </li>
-<li>
-For security reasons both Register Globals and Magic Quotes php settings
-should be set to Off. When FrontAccounting is used with www server running
-php as Apache module, respective flags are set in .htaccess file. When your
-server uses CGI interface to PHP you should set
-<strong><em>magic_quotes_gpc = 0</em></strong> and
-<strong><em>register_globals = 0</em></strong> in php.ini file.
-</li>
-<li><strong><em>Innodb</em></strong>
-tables must be enabled in the MySQL server. These tables allow database
-transactions which are a critical component of the software. This is
-enabled by default in the newer versions of MySQL. If you need to
-enable it yourself, consult the MySQL manual. </li>
-<li>FrontAccounting is implemented and tested with MySQL.
-Generally
-it should work with other databases, but this is not supported in any
-way at the moment. </li>
-</ul>
-<h2>Copying all the project files to the correct directory</h2>
-<ul>
-<li>You must obviously have downloaded the project archive to
-be reading this file. </li>
-<li>All the files inside this archive should be copied to a
-directory under the web server root directory. </li>
-<li>For example, create a folder called <strong>/account</strong>,
-and extract the archive into this folder. </li>
-</ul>
-<h2>Installation Steps</h2><ol><li>If you have the option to create multiple databases on your
-host, create one, fi. <strong>frontacc</strong>, otherwise
-write down the database name for your account. At the same time look up
-the username and password for the database. You will need these
-informations during the wizard install. </li>
-<li>Enter <strong><em>your_url/account</em></strong>
-(or whatever directory you entered). This will run the install wizard if this is the first time you run FrontAccounting,
-setup a drill company and optional populating with initial demo data. You can later
-on create your own real company. It is a good idea to get familiar with
-the system before starting your own company. </li>
-<li>After successfully install, remove or rename your install
-directory for safety reasons. You don't need it any more.</li>
-</ol><h2> Logging In For the First Time</h2>
-<ol>
-<li>Pleae ensure that the folder <strong>/company/0</strong>
-on the server is <strong>writable</strong>. </li>
-<li>Open a browser and enter the URL for the web server
-directory where FrontAccounting is installed. </li>
-<li>Enter the user name: '<strong>admin</strong>'
-</li>
-<li>Enter the password you created during install.
-</li>
-<li>(NB : enter without quotation marks). </li>
-<li>
-<div>You can set up additional user accounts from the System
-Setup
-tab. Be careful not to delete the demonstration user until a new user
-has been set up. If there are no users defined the next time you try to
-login you won't be able to. The only way then to create a user to login
-with is to manually edit the SQL table "users" to insert a user.</div>
-</li>
-</ol>
-<h2>Setting Up Company Specific Data</h2>
-<ol>
-<li>All the standing configuration data is defined from the
-Setup tab
-and each link should be reviewed to enter appropriate data for the
-business. </li></ol><h2>Troubleshooting</h2>
-<ol>
-<li>If FrontAccounting is installed locally, you may have the <strong><em>session
-save path</em></strong> not set correctly. Normally this is
-set in your php.ini (for Windows). The entry is called <strong><em>session.save_path</em></strong>.
-Make sure this is set to a directory that actually exists. The default
-is set to /tmp, which may not be valid. </li>
-<li>If you are installing FrontAccounting onto a shared server,
-you may have to set the session save path within FrontAccounting. At
-the top of
-/includes/session.inc you will find this line : </li>
-<li>Uncomment this line and set the path to a directory that
-exists
-on your server. Make sure that you have read/write privileges on this
-directory. </li>
-</ol>
-<p> </p>
-</body></html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><head>
-
-
-<meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1"><title>FrontAccounting Update</title>
-<meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">
-<meta name="CREATED" content="0;0">
-<meta name="CHANGED" content="20100902;19041400"></head><body style="direction: ltr;" lang="en-US">
-<h4><strong><font color="#cc6600"><font style="font-size: 20pt;" size="5"><i>Front</i></font></font></strong><strong><font style="font-size: 20pt;" size="5">Accounting
-Update</font></strong></h4>
-<h2>Important Notes for release 2.4.1.</h2>
-<h3>This is a preliminary FrontAccounting ERP 2.4.1 release. </h3>
-This version provides a couple of new important features (in addition to all the <br>
-features merged from latest 2.3.26 release), but main development effort was <br>
-focused on internal architecture changes and cleanups to make future FA development <br>
-easier. <br>
-<br>
-At the time of release most of optional extension modules available from central<br>
-extensions repo has been also ported to 2.4 and should be mostly usable. Most Themes are<br>
-updated and many new Themes are available.<br>
-<br>
-Due to deep changes made under the hood, we highly encourage all current FA 2.3 users<br>
-to make test upgrades on a copy of your working installation connected to separate database<br>
-filled with your real company data. This will allow us find and fix any possible<br>
-upgrade issues before final 2.4 release. Please report any bugs/problems found via our <br>
-Mantis Bugtracker at http://mantis.frontaccounting.com.<br>
-<h3>Download instructions</h3>
-In Sourceforge FrontAccounting (http://sourceforge.net/projects/frontaccounting), select <br>
-Files -> FrontAccounting 2.4 ->2.4.1.<br>
-<br>
-For Windows users select the zip file. For all other users select the tar.gz file.<br>
-<h3>Notice for certain Windows wamp servers.</h3>
-Due to experienced long upgrade time for release 2.3 databases to release 2.4 on certain wamp <br>
-servers, we just ask you to be patience. It might take a while, but should end successfully. <br>
-<h4>New global flags in config.php (config-default.php):</h4>
-/* Optional popup search enabled if this is true. $max_rows_in_search = 10 <br>
-
- is used for maximum rows in search */<br>
-
-<span style="font-weight: bold;">$use_popup_search = true;</span><br>
-
-<span style="font-weight: bold;">$max_rows_in_search = 10;</span><br>
-
-<h2>Important Notes for release 2.3.22.</h2>
-
-
-
-
-<h4>New global flags in config.php (config-default.php):</h4>
-/* Show average costed values instead of fixed standard cost */ In Enventory Valuation Report.<br>
-<span style="font-weight: bold;">$use_costed_values = 0;</span><br>
-<br>
-/* Print Item Images on Sales Quotations. Set to 1 if so. */<br>
-<span style="font-weight: bold;">$print_item_images_on_quote = 0;</span><br>
-<h2>Important Notes for release 2.3.21.</h2>
-
-<h4>Crucial security patches:</h4>
-
-This version consists of crucial security patches and this applies especially to all publicly available servers, <br>
- f.i. installations which are run in not fully trusted environment like public demos, shared accounts or SAAS.<br>
-<h4>New global flags in config.php (config-default.php):</h4>
-/* Whether to allow sending new password by e-mail */<br>
-<span style="font-weight: bold;">$allow_password_reset = false</span><h2>Important Notes for release 2.3.20.</h2>
-
-<h4>Crucial security patches:</h4>
-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.<br>
-<h2>Important Notes for release 2.3.17.</h2>
-
-<h4>New global flags in config.php (config-default.php):</h4>
-/*<br>
- Choose Exchange Rate Provider<br>
- Default is ECB for backwards compatibility<br>
-*/<br>
-<span style="font-weight: bold;">$xr_providers = array("ECB", "YAHOO", "GOOGLE", "BLOOMBERG");<br>
-$dflt_xr_provider = 0;<br>
-<br>
-</span>/*<br>
- Set to true when remote service is authoritative
-source of exchange rates, and can be stored automatically without<br>
- manual edition. Otherwise exrate is stored on first new currency transaction of the day.<br>
-*/<br>
-<span style="font-weight: bold;">$xr_provider_authoritative = false;<br>
-</span><h2>Important Notes for release 2.3.16.</h2>
-<h4>New global flags in config.php (config-default.php):</h4><span style="font-weight: bold;">/*<br> </span> Optional sorting new sales documents lines according to item code<span style="font-weight: bold;"><br>*/<br>$sort_sales_items = false;<br><br>/*<br> </span>Trial Balance opening balance presentation option.<br> When set to true past years part of opening balance is cleared.<span style="font-weight: bold;"><br>*/<br>$clear_trial_balance_opening = false;</span><h2>Important Notes for release 2.3.14.</h2>
-<h4>New global flags in config.php (config-default.php):</h4>
-/* default print orientation. 0 = Portrait, 1 = Landscape */<br>
- <span style="font-weight: bold;">$def_print_orientation
-= 0;</span><br>
-<h2>Important Notes for release 2.3.13.</h2>
-<h4>New global flags in config.php (config-default.php):</h4>
-/* No check on edit conflicts. Maybe needed to be set to 1 in certains
-Windows Servers */<br>
- <span style="font-weight: bold;">$no_check_edit_conflicts
-= 0;</span><br>
-<h2>Important Notes for release 2.3.12.</h2>
-<h4>New global flags in config.php (config-default.php):</h4>
-/* <br>
- Display a dropdown select box for
-choosing Company to login if false.<br>
- Show a blank editbox only if true where
-the Company NickName<br>
- will have to be manually entered. This
-is when privacy is needed.<br>
-*/<br>
- <span style="font-weight: bold;">$text_company_selection</span>
-= false;<br>
-<br>
-/* Should FA hide menu items (Applications, Modules, and
-Actions) from the user if they don't have access to them? <br>
- 0 for
-no 1 for yes<br>
-*/<br>
-<br>
- <span style="font-weight: bold;">$hide_inaccessible_menu_items</span>
-= 0;<br>
-<br>
-/*<br>
- Brute force prevention.<br>
- $login_delay seconds delay is required
-between login attempts after $login_max_attemps failed logins.<br>
- Set $login_delay to 0 to disable the
-feature (not recommended)<br>
-*/<br>
- <span style="font-weight: bold;">$login_delay</span>
-= 30;<br>
- <span style="font-weight: bold;">$login_max_attempts</span>
-= 10;
-<h2><strong></strong>Important Notes for release
-2.3.5.</h2>
-Change in the behaviour of <span style="font-weight: bold; font-style: italic;">Recurrent
-Invoices</span>.<br>
-<ul>
-<li>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.
-</li>
-<li>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.</li>
-<li>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. </li>
-<li>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.</li>
-</ul>
-<h2>Important Notes</h2>
-<p>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.</p>
-<p>In the following description sections related to older FA
-versions are
-prefixed with <span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[color
-tags]</span><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
-. Y</span>ou can skip tagged fragment safely if currently FA
-application is newer than the version in tag.</p>
-<p>Upgrade process consists of up to four stages, some of them
-are
-optional:</p>
-<ol>
-<li>
-<p>Application source files update </p>
-</li>
-<li>
-<p>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.</p>
-</li>
-<li>
-<p>Final cleanup – is needed when some old source files,
-obsoleted by new release should be removed.</p>
-</li>
-<li>
-<p>New features configuration – this is optional step needed
-for most major releases and some minor ones. </p>
-</li>
-</ol>
-<p style="margin-bottom: 0cm;">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).</p>
-<p>Log into admin account of first company.<strong> </strong><strong><span style="">If
-you use a theme other than the standard 3 (aqua, cool or default),
-switch to one of these before going further.</span></strong></p>
-<h2><strong><b>1. Application files update</b></strong></h2>
-<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4"><strong><span style="">a. Source
-files update</span></strong></font></font></p>
-<p><strong><span style="">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.</span></strong></p>
-<p style="margin-top: 0.42cm; page-break-after: avoid;"><strong><font face="Liberation Sans, sans-serif"><font size="4"><span style="">b. Configuration
-files update</span></font></font></strong></p>
-<p><strong><span style="">Compare new
-</span></strong><strong><i><b>config.default.php</b></i></strong><strong>
-</strong><strong><span style="">file with the
-old
-</span></strong><strong><i><b>config.php </b></i></strong><strong><span style="font-style: normal;"><span style="">and
-add all n</span></span></strong><strong><span style="">ew
-settings (if any). </span></strong>
-</p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.2beta]</span></span></strong></p>
-<p><strong> <span style="">$show_users_online
-= 0;</span></strong></p>
-<p><strong> <span style="">$def_print_destination
-= 0;</span></strong></p>
-<p><strong><span style="">$dflt_date_fmt=0;</span></strong></p>
-<p><strong><span style="">$dflt_date_sep=0;</span></strong></p>
-<p><strong><span style="">$table_style,table_style2
-changed</span></strong></p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.3beta]</span></span></strong></p>
-<p><strong> <span style="">$alternative_tax_include_on_doc=0;</span></strong></p>
-<p><strong><span style="">$suppress_tax_rates
-= 0;</span></strong></p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.3RC1]</span></span></strong><strong> </strong>
-</p>
-<p><strong><span style="">Application version
-information and a couple of other private FA variables are stored in
-</span></strong><strong><i><b>version.php</b></i></strong><strong>
-</strong><strong><span style="">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 </span></strong><strong><span style="font-style: normal;"><span style="">config.php</span></span></strong><strong><span style="">.</span></strong></p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.3RC2]</span></span></strong></p>
-<p><strong> <span style="">$save_report_selections
- = 0; // A value > 0 means days to save the
-report selections.</span></strong></p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.3]</span></span></strong></p>
-<p><strong> <span style="">$save_po_item_codes
- = 0; // show item codes on purchase
-order </span></strong></p>
-<p><strong><span style="">$def_print_destination
-= 0; // default print destination. 0 = PDF/Printer, 1 = Excel</span></strong></p>
-<p><strong><span style="">$alternative_tax_include_on_docs
-= 0; // 1 = print Subtotal tax excluded, tax and Total tax
-included</span></strong></p>
-<p><strong><span style="">$suppress_tax_rates
-= 0; // suppress tax rates on documents. 0 = no, 1 = yes.</span></strong></p>
-<strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"></span></span></strong><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"></span></span></strong>
-<h2><strong><b>2. Database upgrade</b></strong></h2>
-<p><strong><span style="">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.</span></strong></p>
-<p><strong><span style="">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'.</span></strong></p>
-<p style="">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.</p>
-<h2>3. Final cleanup</h2>
-<p>Remove or rename install folder in main FrontAccounting
-directory.
-</p>
-<p>After upgrade is installed you can remove files obsoleted by
-new
-FrontAccounting version. Also old, unused settings <span style="font-style: normal;"><span style="">can
-be removed from </span></span><i><b>config.php</b></i><span style="font-style: normal;"><span style="">
-file.</span></span></p>
-<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4">a.
-Source files cleanup</font></font></p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.2beta]</span></span></strong></p>
-<p><strong><span style=""><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">/includes/reserved.inc
-– removed.</span></span></strong></p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.1]</span></span></strong><strong> </strong>
-</p>
-<p><strong><span style="">/admin/db/v_banktrans.inc
-- removed</span></strong></p>
-<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4"><span style="font-style: normal;"><span style="">b.
-Config.php cleanup </span></span></font></font>
-</p>
-<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
-2.2RC1]</span></span></strong><strong> </strong>
-</p>
-<p><strong><span style="">$security_headings,
-$security_groups arrays – moved to database (see Access Setup) </span></strong>
-</p>
-<p><strong><span style="">$def_app – moved
-to user configuration in database.</span></strong></p>
-<p><strong><span style="font-style: normal;"><span style="">$version
-– moved to </span></span></strong><strong><i><b>version.php</b></i></strong><strong><span style="font-style: normal;"><span style="">
-file. Remove</span></span></strong></p>
-<h2>4. New features configuration</h2>
-<p>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.</p>
-<p><br>
-<br>
-</p>
-<p>----------------------</p>
-<ul>
-</ul>
-</body></html>
\ No newline at end of file
projects / fa-stable.git / commitdiff