Installing FUEL CMS
FUEL CMS uses CodeIgniter. If you are familiar with installing CodeIgniter, then many of the following steps will seem familiar to you.
The following are steps to installing FUEL:
- Download the latest version from getfuelcms.com
- Place the downloaded folder onto your webserver. Note that the fuel/data_backup, fuel/install and fuel/scripts folders should be a folders inaccessible from the web if using .htaccess.
- Browse to the index page. You should see a page of similar instructions as below.
- Alter your Apache .htaccess file to the proper RewriteBase directory. The default is your web servers root directory. If you do not have mod_rewrite enabled you will need to change the $config['index_page'] from blank to 'index.php' in fuel/application/config/config.php
- Install the database by first creating the database in MySQL and then running the fuel/install/fuel_schema.sql file
- Configure the fuel/application/config/database.php file with the proper database connection settings (like with any other CodeIgniter database application)
- Change the $config['encryption_key'] found in the fuel/application/config/config.php file
- Make the following folders writable:
- fuel/application/cache/
- fuel/application/cache/dwoo/
- fuel/application/cache/dwoo/compiled/
- assets/images/
That's it!
Upgrading to 1.4
If you have a current installation of 1.3x or less and are wanting to upgrade, there are a few things to be aware of. FUEL 1.4 uses CodeIgniter 3.x which includes a number of changes, the most prominent being the capitalization of controller and model names. Additionally it is more strict on reporting errors.
Upgrading to 1.4 will be a bit of a manual process and different depending on how your projects were developed. In general, FUEL CMS gives developers the fuel/application folder as their coding playground. So one option would be to start with a fresh 1.4 installation and copy over the following files (mileage may vary depending on your project):
- fuel/application/controllers/*
- fuel/application/helpers/*
- fuel/application/libraries/ (that are specific to your project and not FUEL related overwrites)
- fuel/application/models/*
- fuel/application/views/*
- fuel/application/config/MY_fuel.php
- fuel/application/config/MY_fuel_modules.php
- fuel/application/config/MY_fuel_layouts.php
- fuel/modules/ (any module folders that aren't fuel... leave that one alone)
Another option would be to create a separate branch using Git and add the following as a remote repository in which to pull and merge from:
https://github.com/daylightstudio/FUEL-CMS.git
It will indicate potential merge conflicts and some of them you may need to fix if they are your own code changes in the fuel/application folder. However, most will just need to be accepted.
Additionally, FUEL 1.4 includes a script to help automate most (and maybe all) of the updates that may be required for your own actual code to address capitalization issues, method parameter errors and more in your own fuel/application and installed advanced module code. It is recommended you run the following command from the folder you installed FUEL CMS using a different Git branch to test out. Mac OSX or a Unix flavor operating system and Git are required to run the script:
php index.php fuel/installer/update
Lastly, there is a SQL update file at fuel/install/upgrades/fuel_1.4_schema_changes.sql that should be run and performs some minor updates to the schema.
Certain modules may require their own configuration and database SQL files to be run. Please reference their own documentation in the user guide for additional install information.