Before running the installation script all necessary software must be installed and properly configured. The developement of host providers has accelerated recently, from simply hosting server space through web domains and we will be requiring a WWW, SQL, FTP servers and PHP. All the data necessary for the installation process we are obtaining from our chosen host provider.
Then all the installation files need to be moved to the target server – for example by using an FTP client (installed FTP server required). When all files are transferred, it is necessary to change the access rights to the “compile” directory to full access: read/write/run (777). It can be done directly from FTP client by selecting a proper option, or using a system command (for example, for Linux-based systems it would be “chmod -x 777 /var/www/compile”, where -x parameter is responsible for setting access rights on files and directories located in the target directory, while “/var/www/compile” is simply the target directory).
Next step is running the web browser and typing in our WWW address
(ie. http://www.mydomain.net/index.php) in the location bar.
If entered correctly, your browser should display the installation page of the system ('Configuration.php' file contains the variable [INSTALLED] which is responsible for running the installation executable).
When the installation script appears on the screen, pay attention to any messages that may appear (marked red). They inform about any errors in access rights to specific files or directories. To fix them, you can use an automated script via FTP or give access rights to files or directories manually, for example using the “chmod” command.
WARNING!!! You should never give read/write/run rights to the entire installation directory, because it may cause serious security-related consequences.
In order to proceed, access rights need to be given appropriately.
To make use of the automatic privileges setup option, proper basic FTP client data must be provided (server address (host) + optionally a port number in case we are not using the standard one, ie. if "ftp.mydomain.net:5021”/login/password/source catalog which contains the installation script. If our WWW site is installed in the root directory of the FTP user and the installation files are placed in 'public_html', the patch will be /public_html/.
Importantly, the script needs to be logged in to a user which has appropriate rights to modify (in this case, “root” rights).
When the installation script is provided with the required data, you can proceed to the phase of setting up write permissions (“set up” button).
After the installation files are prepared, you can provide the database server data (it is important that you remember to create a database – tables will be automatically created by the installer). Here you also need to provide the address to the database server, login and password (REMEMBER!!! Login and password to the server need to be different than the “root” password), name of the database, table prefix (so that the installer can create tables staring with a given series of characters) and the access path.
After these data are provided you can test the connection with database server – the script will display information determining whether the connection was successful or not (data was incorrect or there was an access problem).
When you have confirmation that the connection is okay and you have appropriate access rights to files/directories, you may begin to enter the data for the administrator's account – login/password/correct e-mail address.
The last thing you need to do before starting the installer it to choose the modules that will be used:
Then all the installation files need to be moved to the target server – for example by using an FTP client (installed FTP server required). When all files are transferred, it is necessary to change the access rights to the “compile” directory to full access: read/write/run (777). It can be done directly from FTP client by selecting a proper option, or using a system command (for example, for Linux-based systems it would be “chmod -x 777 /var/www/compile”, where -x parameter is responsible for setting access rights on files and directories located in the target directory, while “/var/www/compile” is simply the target directory).
Next step is running the web browser and typing in our WWW address
(ie. http://www.mydomain.net/index.php) in the location bar.
If entered correctly, your browser should display the installation page of the system ('Configuration.php' file contains the variable [INSTALLED] which is responsible for running the installation executable).
When the installation script appears on the screen, pay attention to any messages that may appear (marked red). They inform about any errors in access rights to specific files or directories. To fix them, you can use an automated script via FTP or give access rights to files or directories manually, for example using the “chmod” command.
WARNING!!! You should never give read/write/run rights to the entire installation directory, because it may cause serious security-related consequences.
In order to proceed, access rights need to be given appropriately.
To make use of the automatic privileges setup option, proper basic FTP client data must be provided (server address (host) + optionally a port number in case we are not using the standard one, ie. if "ftp.mydomain.net:5021”/login/password/source catalog which contains the installation script. If our WWW site is installed in the root directory of the FTP user and the installation files are placed in 'public_html', the patch will be /public_html/.
Importantly, the script needs to be logged in to a user which has appropriate rights to modify (in this case, “root” rights).
When the installation script is provided with the required data, you can proceed to the phase of setting up write permissions (“set up” button).
After the installation files are prepared, you can provide the database server data (it is important that you remember to create a database – tables will be automatically created by the installer). Here you also need to provide the address to the database server, login and password (REMEMBER!!! Login and password to the server need to be different than the “root” password), name of the database, table prefix (so that the installer can create tables staring with a given series of characters) and the access path.
After these data are provided you can test the connection with database server – the script will display information determining whether the connection was successful or not (data was incorrect or there was an access problem).
When you have confirmation that the connection is okay and you have appropriate access rights to files/directories, you may begin to enter the data for the administrator's account – login/password/correct e-mail address.
The last thing you need to do before starting the installer it to choose the modules that will be used:
1) Administrator:
a) admin_prvmsg.php – module responsible for the configuration of private messages,
b) admin_shoutbox.php – module responsible for the configuration of administrator notes (shoutbox),
c) admin_portal.php – module responsible for the configuration of the portal section,
d) admin_download.php – module responsible for the configuration of the download section,
e) admin_gallery.php – module responsible for the configuration of the gallery section,
f) admin_portal_doc.php – module responsible for the configuration of the documentation of the portal,
g) admin_forms.php – module responsible for the configuration of forms,
h) admin_forum.php – module responsible for the configuration of the forum section.
2) #privatemsg – private message module.
3) Download – download section module.
4) Forum – forum module.
5) Gallery – gallery module.
6) Portal – portal module, with options available:
a) portal_stats.php – statistics,
b) portal_doc.php – works similarly to the Articles but it has the option to add attachment files,
c) portal_forms.php – portal forms.
After modules are chosen, you can start the installation script, using the “Install” button.
