<!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>
+<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>
-
+ <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 />
installed languages)
</li>
<li><strong>/modules/installed_modules.php</strong> (contains information about
-installed modules, <strong>only vers. 1.1</strong>)
- </li>
+installed modules<strong></strong>)</li><li><span style="font-weight: bold;">installed_extensions.php</span> (contains information about installed extensions to the menu system)</li>
<li>if you have made <em>changes to other files</em>, like themes or so, backup
these files too. </li>
</ol>
<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
+ <strong>config.php</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. <br>You must also manuelly ensure that you have write permission to the new folder /company/0.</strong></li>
+ </li><li><strong>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.</strong></li><li style="font-weight: bold;">If something goes wrong during upgrade, you can enter here again and try 'Force Upgrade', and press 'Upgrade System' again.</li><li><strong style="font-weight: bold;"></strong><strong>There are no database changes during a major and minor release. Like from 2.1 to 2.1.1 - 2.1.5 .</strong></li><li style="font-weight: bold;">When
+updating from release 2.1.2 to 2.1.3, please go into Bank and General
+Ledger tab. Enter Account Classes. Change the Class Types to a proper
+value for all classes.</li><li style="font-weight: bold;">When updating from release 2.1.4 to 2.1.5, please go into Bank and General Ledger tab. Enter Quick Entries. <br />The Tax now uses Tax Types instead of Item Tax Types. The reason for changing this is for the complex rules inside the EU.<br />Change
+to correct Tax Type. If you need more Tax Type lines in the same Quick
+Entry, please group them together and use the same action type.</li>
</ul>
-<p> </p>
-</body>
-
-</html>
+<p style="font-weight: bold;"> </p>
+</body></html>
\ No newline at end of file
projects / fa-stable.git / blobdiff