Comments should follow templates and recurrent invoices.

[fa-stable.git] / update.html

diff --git a/update.html b/update.html
index 2c0702043f4f659774f407a79e3ba919a8874690..b14ec82fde45709448207806c6b6c138400e7b8f 100644 (file)
--- a/update.html
+++ b/update.html
@@ -28,8 +28,7 @@ backup this file if you have done manually changes to it.
 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>
@@ -38,23 +37,27 @@ these files too. </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
+        <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. &nbsp;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>
+  </li><li><strong>When
+updating release&nbsp;2.0.X to release 2.1.X, you must immediately
+login on company 0, the first company you created, as&nbsp;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.&nbsp; Go
+to the 'Setup' tab and run 'Software
+Upgrade'.
+Mark the checkbox 'Install' and press 'Upgrade System'. &nbsp;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>
 </ul>
 
-<p>&nbsp;</p>
+<p style="font-weight: bold;">&nbsp;</p>
 </body></html>
\ No newline at end of file