Getting Started
From batavi
Contents |
Installation
Before you install
Before installing Batavi, you need to check that the following requirements are fulfilled by your web-hoster:
Apache 2.x PHP 5.x < 5.3 MySQL 5.x with InnoDB enabled
Please note, that here are listed only basic requirements. To see full list of requirements please visit page: System Requirements.
For Apache 2.x, it's advised to run php in CGI mode, as this makes sure that Apache can read and write the files needed. If this is not possible, please see the USER RIGHTS section.
On a side note, please make sure that you've got enough coffee in your coffee-machine to continue with installation.
Download and transfer to server
Download Batavi version 1.0 from http://www.batavi.org (the download button will redirect you to SourceForge.net) to your desktop. Make sure it's not unpacking the tarbal automatically. Use your preferred way to transfer the tarbal to your server.
Unpack
Unpack the tarbal on your preferred location:
$tar xvjpf batavi-1.0.tar.bz2
This will give you a directory batavi, to which you can point your web-server via a virtual host.
MySQL
Once again, please make sure that MySQL is using InnoDB.
Create a new user and database for your Batavi installation, make sure that the character set is utf8:
$mysql -u root -p mysql mysql> CREATE DATABASE batavi /*!40100 DEFAULT CHARACTER SET utf8 */; mysql>CREATE USER 'batavi'@'localhost' IDENTIFIED BY 'some_pass'; mysql> GRANT ALL PRIVILEGES ON batavi.* TO 'batavi'@'localhost' mysql> CREATE USER 'batavi'@'%' IDENTIFIED BY 'some_pass'; mysql> GRANT ALL PRIVILEGES ON batavi.* TO 'batavi'@'%' mysql> FLUSH PRIVILEGES;
Installation
As you're done with all the pre-installation tasks, please point your browser to the location of your new web-shop and follow the steps there. Use the database user you created in the steps above.
User rights
If Apache is not running PHP as CGI, please make sure that you change the owner of the following files to your Apache user (in the below example apache, but can also be www-data or something else), or set the file permissions correct:
$chown apache includes/work $chown apache admin/ext/tiny_mce/plugins/ajaxfilemanager $chown apache templates/default/images/uploaded $chown apache templates/default/images/icons $chown apache images/default/dynamic/banners $chown apache images/default/dynamic/banners/graphs $chown apache images/default/dynamic/banners/uploaded $chown apache images/default/dynamic/brands $chown apache images/default/dynamic/brands/uploaded $chown apache images/default/dynamic/brands/originals $chown apache images/default/dynamic/categories $chown apache images/default/dynamic/categories/large $chown apache images/default/dynamic/categories/thumbnails $chown apache images/default/dynamic/categories/mini $chown apache images/default/dynamic/categories/uploaded $chown apache images/default/dynamic/categories/originals $chown apache images/default/dynamic/categories/product_info $chown apache images/default/dynamic/menu $chown apache images/default/dynamic/menu/default $chown apache images/default/dynamic/menu/originals $chown apache images/default/dynamic/products $chown apache images/default/dynamic/products/uploaded $chown apache images/default/dynamic/products/originals $chown apache templates/default/images $chown apache includes $chown apache install $chown apache data $chown apache robots.txt
or
$chmod 777 includes/work $chmod 777 admin/ext/tiny_mce/plugins/ajaxfilemanager $chmod 777 templates/default/images/uploaded $chmod 777 templates/default/images/icons $chmod 777 images/default/dynamic/banners $chmod 777 images/default/dynamic/banners/graphs $chmod 777 images/default/dynamic/banners/uploaded $chmod 777 images/default/dynamic/brands $chmod 777 images/default/dynamic/brands/uploaded $chmod 777 images/default/dynamic/brands/originals $chmod 777 images/default/dynamic/categories $chmod 777 images/default/dynamic/categories/large $chmod 777 images/default/dynamic/categories/thumbnails $chmod 777 images/default/dynamic/categories/mini $chmod 777 images/default/dynamic/categories/uploaded $chmod 777 images/default/dynamic/categories/originals $chmod 777 images/default/dynamic/categories/product_info $chmod 777 images/default/dynamic/menu $chmod 777 images/default/dynamic/menu/default $chmod 777 images/default/dynamic/menu/originals $chmod 777 images/default/dynamic/products $chmod 777 images/default/dynamic/products/uploaded $chmod 777 images/default/dynamic/products/originals $chmod 777 templates/default/images $chmod 777 includes $chmod 777 install $chmod 777 data $chmod 777 robots.txt
Finalization
If you followed the web installation, everything should be okay after the last page and you can login to your Batavi admin through http://www.yourhost.com/admin with the admin user you created.
Known Issues
Batavi 1.0
Due to the Smarty bug, if you install Batavi on PHP 5.3 you will get following message:
Warning: strftime(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /var/www/html/batavi/ext/smarty/libs/Smarty_Compiler.class.php on line 403
Solution for problem is to upgrade Smarty or return to previous version of PHP.
Batavi 1.1 will have this issue solved.
SELinux
For those of you who are using SELinux on their server, please be aware that apart from changing file permissions or file owner on the 'old fashioned' unix way, you also need to change the following for SELinux:
chcon -t httpd_sys_script_rw_t <filename>
