-
-
- A working HTTP web server eg. Apache, IIS. +
- A working HTTP web server eg. Apache, IIS. -
- PHP installed on the web server. +
- PHP installed on the web server. -
- A working MySQL server - with innodb tables enabled (see notes below) +
- A working MySQL server - with innodb tables + enabled (see notes below)
- Adobe Acrobat Reader - for viewing the PDF reports before printing them out. @@ -39,19 +40,19 @@
- 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. +
- 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. +of session.auto_start + can and should be set to 0. -
- 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. +
- 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.
- FrontAccounting is implemented and tested with MySQL. Generally @@ -68,10 +69,12 @@ way at the moment.
- You must obviously have downloaded the project archive to be reading this file. +
- You must obviously have downloaded the project + archive to be reading this file. -
- All the files inside this archive should be copied to a directory under the web server root directory. +
- All the files inside this archive should be copied to + a directory under the web server root directory.
- For example, create a folder called /account, and extract the archive into this folder. @@ -86,17 +89,17 @@ way at the moment.
- If you have the option to create multiple databases on your host, create one, fi. frontacc, -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. +
- If you have the option to create multiple databases on your host, create one, fi. frontacc, + 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. -
- Enter your_url/account/install (or -whatever directory you entered). This will run the install wizard, -setup a drill company and populating with initial 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. +
- Enter your_url/account/install (or whatever + directory you entered). This will run the install wizard, setup a drill + company and populating with initial 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.
- After successfully install, remove or rename your install directory for safety reasons. You don't need it any more. @@ -106,7 +109,7 @@ the system before starting your own company.
-
-
-
Creating the Database
+ +Creating the Database
+ -
-
-
- NOTE : As FrontAccounting is still heavily under development, -the database structure will ALWAYS change between releases, so if you -have a database that you created for a previous release of -FrontAccounting, it WILL NOT WORK after installing a new release. -Please delete any old databases before proceeding. +
- NOTE : As FrontAccounting is still heavily under + development, the database structure will ALWAYS change between releases, so + if you have a database that you created for a previous release of + FrontAccounting, it WILL NOT WORK after installing a new release. You may + run the script, update_db.php and select the appropriate script, f.i. + alter.sql (from release 1.XX to release 2.0). -
- We strongly suggest using a GUI to manage your database(s) and database users. If you don’t have any, download phpMyAdmin. +
- We strongly suggest using a GUI to manage your database(s) and database users. If you dont have any, download phpMyAdmin. -
- Create a database with a name of your choice. The default in config_db.php is ‘frontacc’, but of course you can select whatever name you desire. +
- Create a database with a name of your choice. The default in config_db.php is frontacc, but of course you can select + whatever name you desire.
- Populate the database you have created. There are two scripts
are provided to populate the database (both inside the folder /sql) :
-
+
-
-
- en_US-demo.sql. This has a minimal amount of demonstration data set up so that transactions can be tried to see how the system works. +
- en_US-demo.sql. This has a minimal + amount of demonstration data set up so that transactions can be tried to + see how the system works.
- en_US-new.sql. This script has @@ -152,76 +160,75 @@ wish to set up your company on FrontAccounting then this is the script to use. - -
+
- Now that the database is created you will need to set up a -database user to access this database. DO NOT USE THE USER -‘ROOT’. Set up a new user and give that user full -privileges over the database ‘frontacc’. +
- Now that the database is created you will need to + set up a database user to access this database. DO NOT USE THE USER ROOT. + Set up a new user and give that user full privileges over the database + frontacc.
- After successfully install, remove or rename your install directory your_url/account/install (or whatever directory you entered) for safety reasons. You don't need it any more. - -
-
-
+
Editing config_db.php
- +-
-
- config_db.php contains connection -information for the database. These must be set to your local settings -or you will not be able to access FrontAccounting. +
- config_db.php contains connection + information for the database. These must be set to your local settings or + you will not be able to access FrontAccounting. -
- FrontAccounting allows multiple connections, you can enter as -many connections as you have separate entities (most people will use -only one). +
- FrontAccounting allows multiple connections, you + can enter as many connections as you have separate entities (most people + will use only one). -
- $db_connections is an array of connections – for each connection : +
- $db_connections is an array of connections + for each connection : -
- “name” is the name of the connection, this is the name that will be displayed to the user +
- name is the + name of the connection, this is the name that will be displayed to the user -
- “host” is the computer IP -address or name where the database is. The default is localhost -assuming that the web server is also the sql server. +
- host is the + computer IP address or name where the database is. The default is localhost + assuming that the web server is also the sql server. -
- “dbuser” is the user name under -which the database should be accessed. NB, again, do not use the user -ROOT. A user with appropriate privileges must be set up. +
- dbuser is + the user name under which the database should be accessed. NB, again, do not + use the user ROOT. A user with appropriate privileges must be set up. -
- “dbpassword” is the password for “dbuser”. You would have entered this when you created “dbuser”. +
- dbpassword + is the password for dbuser. You would have entered this when you created + dbuser. -
- “dbname” is the name of the database. The provided scripts use the name OpenAccounting. +
- dbname is + the name of the database. The provided scripts use the name OpenAccounting. -
- “tbpref” is the table prefix for +
- tbpref is the table prefix for the tables. If you only have access to one database, you must use table prefix to separate the companies. Table prefix is set by a table prefix counter inside config_db.php, fi. 0_ for the first company. - +
- Open a browser and enter the URL for the web server directory where FrontAccounting is installed. +
- Pleae ensure that the folder /company/0 on the server is writable. + +
- Open a browser and enter the URL for the web server + directory where FrontAccounting is installed. -
- Enter the user name: 'admin' +
- Enter the user name: 'admin' -
- Enter the password: 'password' +
- Enter the password: 'password' -
- (NB : enter without quotation marks). + +
- (NB : enter without quotation marks).
-
-
+
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 @@ -285,12 +296,15 @@ implemented and we strongly recommend you to use this approach, see
-
-
- If FrontAccounting is installed locally, you may have the session save path not set correctly. Normally this is set in your php.ini (for Windows). The entry is called session.save_path. Make sure this is set to a directory that actually exists. The default is set to /tmp, which may not be valid. +
- If FrontAccounting is installed locally, you may have the session save path not set correctly. Normally this is set in your php.ini (for Windows). The entry is called session.save_path. Make sure this is set to + a directory that actually exists. The default is set to /tmp, which may not be + valid. -
- If you are installing FrontAccounting onto a shared server, you -may have to set the session save path within FrontAccounting. At the -top of config.php you will find this line : +
- If you are installing FrontAccounting onto a shared + server, you may have to set the session save path within FrontAccounting. At + the top of config.php (in release 2.0 this has moved to /includes/session.inc) + you will find this line :
- Uncomment this line and set the path to a directory that exists
-
-
-
-
-
-
Installation Steps (manuel, for advanced users, not recommended)
-
+
-
-