-<!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>
- <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type" />
-
-
- <title>FrontAccounting Update</title></head>
-<body>
-<div><strong><span style="font-size: 20pt;"><span style="color: rgb(204, 102, 0); font-style: italic;">Front</span>Accounting Update</span></strong></div>
-<br />
-<br />
-
-<h2>Important Notes</h2>
-
-<ul>
- <li>You can easily upload all the files to your installation folder on the
-server overwriting the existing files, <strong><em>if you take these important
-steps</em></strong>:
- <ol>
- <li>Backup (download) the following files to another folder:
- <ol>
- <li><strong>config_db.php</strong> (contains information about the companies and
-connection info).
- </li>
- <li><strong>config.php</strong> (contains various settings. You only need to
-backup this file if you have done manually changes to it.
- </li>
- <li><strong>/lang/installed_languages.inc</strong> (contains information about the
-installed languages)
- </li>
- <li><strong>/modules/installed_modules.php</strong> (contains information about
-installed modules, <strong>only vers. 1.1</strong>)
- </li>
- <li>if you have made <em>changes to other files</em>, like themes or so, backup
-these files too. </li>
- </ol>
-
- </li>
- <li>Upload all the new files.
- </li>
- <li>Restore the files mentioned in #1. Be <strong>careful</strong> with
- <strong>config.db</strong>. Look into variances. There might be new variables in
-the new version. It might be easier to <em>manually change your former values in
-the new file</em>.
- </li>
- <li>Rename or remove the /install folder (you have already performed the install
-process earlier). </li>
- </ol>
- </li>
- <li>If there are changes to the database structure, please run the script <strong><em>update_db.php</em></strong>
-from FrontAccounting root installation, Enter the database user and the
-password and choose the update script from the local harddisk.</li>
- <li><strong>When updating release 1.XX to release 2.0, you must run the update_db.php script and select the file <em>- alter.sql -</em> that are located in the sql folder. You <em>must</em>
-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.<br />You must also manuelly ensure that you have write permission to the new folder /company/0.</strong></li>
-</ul>
-
-<p> </p>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html><head>\r
+\r
+\r
+\r
+\r
+\r
+\r
+\r
+<meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1"><title>FrontAccounting Update</title>\r
+\r
+<meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">\r
+<meta name="CREATED" content="0;0">\r
+<meta name="CHANGED" content="20100902;19041400"></head><body style="direction: ltr;" lang="en-US">\r
+<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\r
+Update</font></strong></h4>\r
+<h2><strong><b>1. Application files update</b></strong></h2>\r
+\r
+<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4"><strong><span style="">a. Source\r
+files update</span></strong></font></font></p>\r
+\r
+<p><strong><span style="">Extract distribution\r
+zip/tar.gz file in empty directory, and copy all the files to your\r
+FrontAccounting directory overwriting old files. If it is major\r
+release upgrade you can skip next step and go directly to cleanup.</span></strong></p>\r
+\r
+<p style="margin-top: 0.42cm; page-break-after: avoid;"><strong><font face="Liberation Sans, sans-serif"><font size="4"><span style="">b. Configuration\r
+files update</span></font></font></strong></p>\r
+\r
+<p><strong><span style="">Compare new\r
+</span></strong><strong><i><b>config.default.php</b></i></strong><strong>\r
+</strong><strong><span style="">file with the\r
+old\r
+</span></strong><strong><i><b>config.php </b></i></strong><strong><span style="font-style: normal;"><span style="">and\r
+add all n</span></span></strong><strong><span style="">ew\r
+settings (if any). </span></strong>\r
+</p>\r
+\r
+<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 style="background-color: white;">The following variables has been moved from config.default.php into sys_prefs table:<br>\r
+<br>\r
+$no_zero_lines_amount = 1;<br>\r
+$show_po_item_codes = 0;<br>\r
+$accounts_alpha = 0;<br>\r
+$loc_notification = 0;<br>\r
+$print_invoice_no = 0;<br>\r
+$allow_negative_prices = 1;<br>\r
+$print_item_images_on_quote = 0;<br>\r
+<br>\r
+These values can be maintained in Setup tab -> System and GL Setup.<br>\r
+<br>\r
+The following variables has been moved from config.default.php into sys_refs table:<br>\r
+<br>\r
+$alternative_tax_include_on_docs = 0;<br>\r
+$suppress_tax_rates = 0;<br>\r
+<br>\r
+These values can be maintained in Setup tab -> Company Setup.<br>\r
+<br>\r
+The following variables has been moved from config.default.php into users table:<br>\r
+<br>\r
+$save_report_selections = 0;<br>\r
+$use_date_picker = 1;<br>\r
+$def_print_destination = 0;<br>\r
+$def_print_orientation = 0;<br>\r
+<br>\r
+These values can be maintained in Setup tab -> Display Setup or Preferences.<br>\r
+<br>\r
+ Please also remove these variables from your existing config.php file</span><br>\r
+</span></span></strong><h2><strong><b>2. Database upgrade</b></strong></h2>\r
+<p><strong><span style="">This step can be\r
+skipped\r
+for small version updates i.e. when you have already installed\r
+FrontAccounting version 2.4 or later. Before database upgrade is\r
+done on all company databases backup file is created automatically to\r
+enable database restore after failure.</span></strong></p>\r
+<p><strong><span style="">After major version\r
+upgrade overwriting files in first step makes the system unaccessible\r
+for all users but site admin, who have to run upgrade procedures to\r
+update all company databases to the new version provided with the\r
+release. After logging to administrator account of first installed\r
+company go directly to Setup/Software Upgrade screen, mark all\r
+subsequent 'Install' checkboxes and press 'Upgrade System'.</span></strong></p>\r
+<p style="">If something goes wrong during\r
+upgrade, you can eventually try forced upgrade option. Forced upgrade\r
+ignores some smaller errors which can arise during upgrade due to\r
+some exotic database configuration. This is depreciated option, so\r
+first read error messages if any, try to fix signalized problems,\r
+restore databases from backup and retry normal installation. To run\r
+upgrade in forced mode check box 'Force Upgrade', and press 'Upgrade\r
+System' again.</p>\r
+<h2>3. Final cleanup</h2>\r
+<p>Remove or rename install folder in main FrontAccounting\r
+directory.\r
+</p><h2>4. New features configuration</h2>\r
+<p>During upgrade process new features are initialized to default\r
+status, and sometimes old settings are also changed to conform with\r
+new security policy. This automatic process is designed to be as\r
+neutral for end users as possible, however sometimes site or company\r
+admin intervention can be necessary to set thing after changes to\r
+their best state. Below you will find description of new settings\r
+available after upgrade.</p>\r
+\r
+<p>----------------------</p>\r
+<ul>\r
+</ul>\r
</body></html>
\ No newline at end of file
projects / fa-stable.git / blobdiff