PHPainfree Test Drive

What is PHPainfree

PHPainfree is a relatively young PHP framework written by Eric Ryan Harrison.

The README for the project is in first person, so I'll let PHPainfree explain what it is:

I am an ultra-lightweight PHP framework. I am inspired by the MVC concept, but I'm too artsy to let myself be defined by labels like that. I basically do what I want.


To try the framework out I cloned the git repository. This should be roughly equivalent to version 0.6.3, in case you want to follow along at home.

My setup is a bit unique, as a trial usage in a sub-directory of my local machine, but you should be able to adjust your install to suit.

It essentially boiled down to these steps:

  1. Clone Repository
  2. Edit includes/PainfreeConfig.php
  3. Symlink includes/ and templates/ into htdocs/
  4. Tweak RewriteBase in htdocs/.htaccess

Shell Transcript

jmhobbs@katya:/var/www/localhost/PHPainfree$ ls  htdocs  includes  LICENSE  templates
jmhobbs@katya:/var/www/localhost/PHPainfree$ cd includes/
jmhobbs@katya:/var/www/localhost/PHPainfree/includes$ cp PainfreeConfig-GENERIC.php PainfreeConfig.php
jmhobbs@katya:/var/www/localhost/PHPainfree/includes$ vim PainfreeConfig.php
jmhobbs@katya:/var/www/localhost/PHPainfree/includes$ cd ..
jmhobbs@katya:/var/www/localhost/PHPainfree$ cd htdocs/
jmhobbs@katya:/var/www/localhost/PHPainfree/htdocs$ ln -s ../includes/ .
jmhobbs@katya:/var/www/localhost/PHPainfree/htdocs$ ln -s ../templates/ .
jmhobbs@katya:/var/www/localhost/PHPainfree/htdocs$ ls -a
.  ..  css  .htaccess  images  includes  index.php  js  templates
jmhobbs@katya:/var/www/localhost/PHPainfree/htdocs$ vim .htaccess

Listing: htdocs/.htaccess

RewriteEngine On
RewriteBase /PHPainfree/htdocs/

RewriteRule ^js/(.+)$ js/$1 [L]
RewriteRule ^css/(.+)$ css/$1 [L]
RewriteRule ^images/(.+)$ images/$1 [L]

RewriteCond %{SCRIPT_FILENAME} !-f
RewriteCond %{SCRIPT_FILENAME} !-d
RewriteRule ^(.+)$ index.php?route=$1&%{QUERY_STIRNG} [L]

After that is all done, it should happily serve up it's welcome page.

It Works!
It Works!

Framework Basics

When PHPainfree claim's to be ultra-lightweight, they mean it. Many of the bits and pieces you would expect on a framework just don't exist. Many.

But more on that later. For now, let's take apart the default files and build something out of them. What we'll attempt to assemble is that paragon of beginner programs, the todo list.

Looking at the provided example files it really seems to me that this is a very view driven framework. The "logic" part runs first, but really just sets up things for the "view" part. Model and controller seem smashed together into the "logic" files, but this is just my interpretation of the design.

This is how the provided example files flow:

Logic Setup => Template(s) Run => Calls Logic Methods

Getting Started


According to includes/PainfreeConfig.php the BaseView "is the name of your base template inside of the templates folder. This base view generally provides the overall framework of output for your application".

To feel out how the framework handles I created a very small stub BaseView in templates/layout.tpl

Listing: templates/layout.tpl

    <?php echo $Controller->title(); ?>

title(); ?>


According to includes/PainfreeConfig.php the ApplicationController is "...the primary controller for your application".

I created a new controller for my test, taken almost entirely from the provided includes/Generic.php.

Listing: includes/ToDoList.php


The last step for this first exploratory version is to change some variables in our configuration file.

Listing: includes/PainfreeConfig.php

$PainfreeConfig = array(

// ApplicationController is the primary controller for your
// application. Generic.php is provided, but doesn't do anything
// except look for the view in the templates/ folder
'ApplicationController' => 'ToDoList.php',

// BaseView is the name of your base template inside of the templates
// folder. This base view generally provides the overall framework
// of output for your application
'BaseView' => 'layout.tpl',

Once that is done, it should now be serving my new files.


Building The Application

That's great and all, and we learned about the processing pipeline and stuff, but really, we didn't do anything.

So let's get down to it. I like a nice MVC pattern, with convention over configuration, so here is how I'm laying out my application. Note that you do not have to do it this way, PHPainfree is written to encourage you to do it, well, just about any way you want.

+-- includes
|   +-- Autoload
|   |   `-- BaseController.php
|   +-- controllers
|   |   +-- list.php
|   |   `-- todo.php
|   +-- main.php
|   `-- PainfreeConfig.php
`-- templates
    +-- layout.tpl
    +-- list
    |   `-- index.tpl
    `-- todo
        `-- index.tpl

Routing Requests

To make my structure work, I had to create my own routing system. I couldn't find anything built into PHPainfree that would do this for me, but that's okay because it's pretty simple. I set my ApplicationController option to "main.php" and placed this in there.

Listing: includes/main.php

route );

  if( 1 <= count( $path ) )
    $controller = preg_replace( '/[^a-z0-9_-]/', '', strtolower( $path[0] ) );

  if( 2 <= count( $path ) )
    $method = preg_replace( '/[^a-z0-9_-]/', '', strtolower( $path[1] ) );

  if( 3 <= count( $path ) )
    $arguments = array_slice( $path, 2 );

  $Controller = new Base_Controller(); // Will be replaced by a real controller
  require_once( 'controllers/' . $controller . '.php' );


Note that on line 18 I instantiate a class called BaseController. This is a stub class that I created for all of my controllers to inherit from, that way I have a consistent interface to call in my templates.

My BaseController.php file will be placed into includes/Autoload to take advantage of the loading feature of PHPainfree. Any file placed into the includes/Autoload folder will be automatically included at runtime, just after the configuration file is loaded and just before the logic file is ran. This is useful for loading libraries, or to do some request pre-processing.

Listing: includes/Autoload/BaseController.php

      // Make the controller available to the view
      $Controller =& $this;
        $PainfreeConfig['TemplateFolder'] . '/' .
        // My controller classes all end in "_controller", so I cut that off here
        strtolower( substr( get_called_class(), 0, -11 ) ) .
        '/' . $method . '.tpl'


The Database

Up to this point I haven't touched a database, which PHPainfree has some support for. Real quick I'll set up a MySQL database for our ToDo application.

MySQL Transcript

mysql> create database todolist;
Query OK, 1 row affected (0.02 sec)

mysql> grant all on todolist.* to painfree@localhost identified by 'password';
Query OK, 0 rows affected (0.05 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.03 sec)

mysql> use todolist;
Database changed
Query OK, 0 rows affected (0.01 sec)

mysql> CREATE TABLE todos ( id INT(6) UNSIGNED AUTO_INCREMENT, list_id INT(6) UNSIGNED, title VARCHAR(255), created DATETIME, completed DATETIME, PRIMARY KEY(id) );
Query OK, 0 rows affected (0.01 sec)

mysql> INSERT INTO lists ( name ) VALUES ( 'Yard Work' );
Query OK, 1 row affected (0.00 sec)

mysql> INSERT INTO todos ( list_id, title, created ) VALUES ( 1, 'Mow Grass', NOW() ), ( 1, 'Weed Garden', NOW() );
Query OK, 2 rows affected (0.00 sec)
Records: 2  Duplicates: 0  Warnings: 0


Configuring The Database

Configuring the database connection in PHPainfree is relatively straightforward. Just open up includes/PainfreeConfig.php and find the Database key. This is an array of MySQL connections, which cascade if they fail.

For instance, if you have a development environment and a production environment, you could place your dev configuration after the production configuration.

In development, the production connection would fail and then load the development configuration. Nothing to change, no environment variables to set, it just works.

Listing: includes/PainfreeConfig.php

  'Database' => array(
    'Primary' => array(
      'type'   => 'mysql',
      'host'   => 'localhost',
      'user'   => 'painfree',
      'pass'   => 'password',
      'schema' => 'todolist',
      'port'   => 3306

Using The Database

Using the database is easy too. The $Painfree global variable has a member called db which provides access to our configured database. But what is $Painfree->db? Well, a little bit of digging into the PHPainfree core and we find out it is just a normal MySQLi link object. Nothing fancy, no database abstractions.

Listing: includes/core/DBD/mysql.php

Bringing It Together

Applying all this knowledge and configuration, let's start our first controller, the List_Controller. This first version will simply fetch all the active lists from the database and get them ready for the template.

Listing: includes/controllers/list.php

db->prepare( "SELECT id, name FROM lists" );
      $stmt->bind_result( $id, $name );
      while( $stmt->fetch() )
        $lists[] = array( 'id' => $id, 'name' => $name );

      return $lists;


  $Controller = new List_Controller();

Now we need to make our template to use this controller. Again, very basic.

Listing: templates/list/index.tpl

ToDo Lists

    lists() as $list ): ?>

At this point, we should be able to render this view:

A List of Lists
A List of Lists

Finishing Up

From here it is a short work to finish the application with another controller and a few more actions. Rather than post a bunch of reptitive code snippets I'll provide my completed source, here.

A List of ToDo's
A List of ToDo's


So, there is my first PHPainfree application. As with any new tool, my usage is probably flawed until I learn more about it. So take this review with a grain of salt.


PHPainfree is a young framework, and it's a thin one. Coming from a heavier framework background, it feels too thin to me. I missed having an ORM, and built in helpers (think Form, Link, Validation). Also, there is no real exception stack that I could find, just $Painfree->debug() for you to use.

MySQL is the only option right now, though it is easily extended. For example, I wrote this in just a few seconds to add SQLite3 support.

Listing: includes/core/DBD/sqlite.php

However, having multiple drivers is shallow when there is no abstraction element. Since it uses native driver objects, I can't just switch from MySQL to SQLite3, because I would then have to switch all of my method calls. Using PDO would be a good option for PHPainfree, IMHO.

My other qualm is the rendering stream. I'm used to the standard MVC pattern, where the controller fetches data with models and publishes it via views. There may be a way to work like that in PHPainfree, but it's not readily apparent.


It's light, at the cost of including minimal features. And it's fairly easy to understand. According to SLOCCount there are only 101 lines of source (after removing the config file and default controller). You can read the whole framework in a few minutes.

Really, I think this is a framework to build your own framework. The core idea of PHPainfree is to stay out of your way. If I intended to use PHPainfree on a regular basis, I would set it up the way I like it, dumping libraries into includes/Autoload and then keep a tracking version in git with all my addons.


I think that where you can draw the most value from this framework is building something you love on top of this common core code. So give it a try at