Kohana is a PHP 5 framework that uses the Model View Controller (MVC) architectural pattern. There are several reasons why you should choose Kohana but the main ones are security, weightlessness and simplicity. In this tutorial, I’ll introduce its main features, and, with a simple demonstration, I’ll show you how much time Kohana can potentially save you.

Kohana is a PHP5 framework that uses the Model View Controller architectural pattern. MVC keeps application logic
separate from the presentation. This allows us to create cleaner code and save time for bug searching.
In unfamiliar with this pattern:

  • Model represents data on which the application operates. Usually a database.
  • View contains presentation code such as HTML, CSS and JavaScript.
  • Controller interprets input from the user and sends to the model and/or view.

Kohana was originally a fork of CodeIgniter (CI), which is an open-source product from EllisLab. There are many similarities between CI and Kohana, but all of the code is either new or completely rewritten. As you can read on the official Kohana web site, the main features are:

  • Highly secure
  • Extremely lightweight
  • Short learning curve
  • Uses the MVC pattern
  • 100% UTF-8 compatible
  • Loosely coupled architecture
  • Extremely easy to extend

Let’s get started. Visit Kohana’s official web site http://kohanaphp.com and click on the green box in the right corner to download the latest version. All Kohana libraries, helpers, and views are included in the default download package, but you may select extra modules, vendor tools, and languages if you want. For the purpose of this tutorial, the default package can be enough. Click on “Download Kohana!” to begin the download.

Once you’ve finished downloading it:

    1. Unzip
    2. Rename the “Kohana_vx.x.x” folder to “kohana” and upload it to your web server document root
    3. Edit the global configuration file application/config/config.php as follows
  1. If you are using a unix-like system, the installation’s subdirs may have lost their permissions during zip extraction. Chmod them all to 755 by running find . -type d -exec chmod 755 {} \; from the root of your Kohana installation.
  2. Make sure the application/logs and application/cache directories are writeable. Chmod to 666.
  3. Now, point your browser to http://localhost/kohana/. Automatically, the framework will call the install.php script and check for your server requirements.

Kohana will run in nearly any environment with minimal configuration. There are a few minimum server requirements:

  • Server with Unicode support
  • PHP version >= 5.2.3
  • An HTTP server. I suggest you use XAMPP. XAMPP is an easy all-in-one tool to install MySQL, PHP and Perl.
  • Database (MsSQL, MySQL, MySQLi, PostgreSQL, PDOSqlite)

There are also some required extensions.

  • PCRE
  • iconv
  • mcrypt
  • SPL

If your installation completes successfully, you will be redirected to this test page:

If any of the tests fail, you must correct them before moving forward.

If all tests have passed, go to the Kohana directory and remove or rename the install.php script. Refresh, and you will see a welcome page like this:

Kohana is ready to go. No other configuration is needed. This framework is amazing. Isn’t it? Let’s review some code. Follow me.

Canonical programming tutorials start with the “Hello world” example. I think, instead, that a simple application can give you a clear idea how the framework works. So, we will build a CD collection manager — just for a fun demonstration. Before we start coding, a brief introduction to Kohana file system is required.

Our application will be placed in the application folder. In this folder there are several sub folders but we need the following for our project:

  • config folder hosts all the configuration files coded as simple static arrays.
  • controllers folder hosts our custom controllers class
  • models folder hosts our custom models class
  • views folder hosts our custom files written in HTML (or any markup language or script needed to display data and interface controls to the user)

The remaining sub folders are not required for this tutorial, so I invite you to learn more on the Kohana web site.

The system folder host the Kohana core and the Kohana tools like libraries, helpers and predefined configuration files. In this project we will use some libraries and some helpers – good tools to speed up your work.

The assets folder is not a predefined Kohana folder. I have created it for media files like CSS, JS, and images. I’ll show you how to include these files in the project.

The modules folder is the place to put reusable collections of related files that together add a particular functionality to an application. The authentication module, provided by the Kohana team, is an example of module.

This is a very brief introduction to the Kohana file system, but it’s enough for the purposes of this tutorial. I don’t want to bore you more with theory.

I have chosen MySQL as my DBMS, but remember that Kohana also supports MsSQL, MySQLi, PostgreSQL, PDOSqlite. Create a database called “cd_collection” or choose the name you prefer, and run the following SQL through phpMyAdmin or any tool to handle the administration of MySQL.

As you can see, the SQL creates two tables, albums and genres, and populates them with some data. The last SQL statement adds a constraint for the foreign key “genre_id”.

The database structure is very simple and doesn’t need much explanation.

Now, you have to tell Kohana where your database is located and how to access it. Edit the global configuration file system/config/database.php as follows

This code tells Kohana to connect to a MySQL database called “cd_collection” on localhost with the username “root” and the password “root”. You have to change these settings according to your database server configuration.

Let’s now create our first controller. Remember these conventions.

  • controller filename must be lowercase, e.g. album.php
  • controller class must map to filename and capitalized, and must be appended with _Controller, e.g. Album_Controller
  • must have the Controller class as (grand)parent

Also, remember how Kohana structures its URLs and how you can call a controller method; e.g http://hostname/kohana_directory/index.php/controller/function.

Let’s take a look at this simple controller.

PHP5 OOP is a prerequisite. So if you aren’t well-versed.

The constructor function, called __construct, initializes the class and calls the parent constructor.
The index function is the default function, so it will be called if we call the controller without
specifying any function (e.g. http://localhost/index.php/kohana/album. After the name controller
there isn’t any function, the default index function will be called.)

Given these basic rules, let’s focus on our application. The album controller implements all the actions for
the albums collection management. This controller allows us to create a new album, to show the albums stored in our database,
to update an album, and to delete an album.

So, let’s change the class as follows.

Create a file called album.php in application/controllers/ and paste the following.

Let me explain what this code does.

Five members variables are declared at the top of the class:

These members are private because I want to limit visibility only to this class.

In the construct method the model and view objects are created using the five members:

To create a model object use this syntax:

To create a view object, use this syntax:

Now there are two objects to access the album and genre model, and three objects to access the views needed to render the presentation.

The index method call the show_albums_list method that lists all albums stored in the database.

In this method you can see how the model and view object are used to access relative methods. “get_list” is a model method (we will see it later) that returns all the albums stored in the database. The result is saved in the “$album_list” array. To pass the result array from the controller to the view, the “set” method is called on the view object. This method requires two parameters: a new empty variable (album_list) to contain data of an existing variable ($album_list). Now the new variable “album_list” contains the $album_list array (we will see later how to show the content in the view). The method “render”, with the TRUE parameter, is necessary to output data to the browser.

The show_create_editor method shows the user interface to insert a new album.

The list of the genres is passed to the view.

The show_update_editor method shows the user interface to update an existing album.

“read” is a model method (we will see it later) that returns data ($album_data) of the album with an id equal to $id. Then, every single element of the returned data album is passed to the view.

The create method receives data, for a new album, from the view and data are stored in the database.

$album_data is an array that contains the POST data from the view. To save the album, the array is passed to the create model method. The last line is a call to a helper method. Helpers are simply functions that assist you with development. The helper classes are automatically loaded by the framework. Helpers are declared as static methods of a class, so there is no need to instantiate the class. In this case the method “redirect” of the helper “url” is called and tells Kohana to redirect the browser to the album controller. This avoids a new insert (for example pressing F5).

“Helpers are simply functions that assist you with development.”

The update and delete methods work in the same manner as the create method above.

The last method get_genres_list gets the genres list from the model ($db_genres_list) and builds a new array ($genres_list) for the select box in the views.

Let’s now create models for our web application. Remember these conventions.

  • model filename must be lowercase, e.g. album.php
  • model class must map to filename and be capitalized, and must be appended with _Model, e.g. Album_Model
  • must have the Model class as (grand)parent

Here is the album model code. Create a file called album.php in application/models/ and paste the code below on it.

All the methods in the models make use of the Query builder syntax. This Kohana tool speeds up database development times and simplify the queries creation.

Two members variables are declared at the top of the class:

These members are private because I want to limit the visibility only to this class. They are the containers for the database tables names.

The first line in the constructor method loads the Kohana database library into $this->db. In the second and third lines the two class members are initialized.

The query in the read method retrieves album records that have a certain identifier (“$id”).

The query in the delete method deletes the albums table row that have a certain identifier (“$id”).

The query in the update method updates the albums table row that has a certain identifier (“$id”) with new values from the “$data” array.

The “$data” array must contain record names as keys of the array, and value as values of the array. The “$data” array must have this form:

The query in the create method inserts a new record with values of the “$data” array.

The “$data” array must have this form:

The query in the get_list method retrieves all the albums rows.

Now, the genre model. Create a file called genre.php in application/models/ and paste the code below it:

This model is very simple so I’ll waste no further time to comment upon it. The Models and the controller are ready to go. Let’s now work on the Views.

Views are files that contain the presentation layer for your application. The purpose is to keep this information separate from your application logic for easy reusability and cleaner code. For this project, three views are required: a view to list the album collection, a view to create a new album, and a view to edit an existing album.

Create a file called list.php in application/views/ and paste the following code in:

This view shows an html page containing a list of all albums. This list has been created using foreach loop that prints the information in an html table. For each album row, there are two images: a “red cross” and a “pocketbook”. They link respectively the controller delete method and the update method. Both pass the album id to the album controller using a get request. Above the list there is a button to create new albums. In this code we also make use of an html helper provided by Kohana that speeds up operations to write html pages.

Let’s now create a file called create.php in application/views/.

The last but not the least is the update view. Let’s create a file called update.php in application/views/.

The first one is a simple editor that enables the user to insert information about a new album.
The fields like author and name will be inserted using an html input and genre using a
combo box. Once the user clicks on the create button, all information is passed,
as a POST request, to the create/update method in the album controller. When the controller receives these posted
variables, it calls the model that inserts a new album into the database. The forms, in both views, makes use of Kohana form helper.

To give a bit of style to our application, create the assets folder in the Kohana root at the same level of the application folder. Now, open it and create two new folders: css and images.

In the css folder create a new file called style.css and paste this:

Now copy the following images to the images folder:  

That’s all. Point your browser to http://localhost/kohana/index.php/album and you should see something similar to this:

If you try to create a new album or to edit an existing one you should see something similar to this:

Of course, some improvements are required for this application but with a small amount of code, you’ve created a little web application.
Now, you know how to use the MVC pattern with Kohana, and how to use database libraries and helpers. To learn more, read the official documentation.

Leave a Reply