Simple Blog – The Index

Simple Blog is a multi-part series about developing data-driven application with PHP and MySql. Check out the intro for details about this unique approach.


Simple Blog – Example 8: CodeIgniter

Simple Blog is a multi-part series. Check out The Index

In example 4, we implemented the MVC pattern for our Simple Blog app. We physically separated our data, presentation, and application logic into models, views, and controllers. In example 6, we rewrote our data logic using PDO which enabled parameterized statements and database portability. In example 7, we implemented the Smarty Template Engine to cleanup our views with a more readable syntax.

So, we’ve developed a web application written in PHP5 that follows MVC, supports multiple databases, provides object-record mapping, has a built-in template engine, and built-in caching. Many of the features we’ve implemented for Simple Blog are precisely the features offered by PHP Frameworks. So, the next logical step was to rewrite the app using a PHP Framework such as CakePHP, CodeIgniter, Symfony, Yii, or Zend which promise to deliver all of the features we’ve implemented so far and more.

In the process of researching these frameworks, I ran across CodeIgniter’s User Guide which was so well written and so well organized that I decided to start with CodeIgniter. A quick glance at and we get to the promises: small footprint, exceptional performance, nearly zero configuration, and clear documentation. Well, let’s dive in and see what CodeIgniter is all about.

Continue reading

Simple Blog – Example 4: MVC

Simple Blog is a multi-part series. Check out The Index

In example 1, we started out by writing some PHP scripts that executed pretty much top to bottom. In example 2, we re-factored our code and markup into reusable function and templates to minimize repetition in the development process. In example 3, we identified a couple candidate objects which we rolled into classes to enhance code maintainability. Throughout this process, we’ve extracted our data logic from our base pages, however, application logic and presentation layer are still mixed.

In this example, we’ll decouple application logic and presentation logic by moving all of our presentation logic into new files we’ll call views. Once we’ve performed this decoupling, our code will be nicely separated into three distinct types: models, views, and controllers.


Our model is just the Post class we created in Example 3. I’ve renamed the file to ‘post.model.php’ and moved it into a directory called models, but other than these two administrative changes, the Post class is unchanged.


Simple Blog has three views: List View, Read View, and Upsert View. The List View displays a list of posts. The Read View displays a single post. The Upsert View displays an HTML form for either creating a new post or editing an existing post. So, let’s take a look at our three views. Note, there is zero new code here, the only thing we’re changing is how the code is organized.

List View

<?php require_once(VIEW_PATH.''); ?>

	<?php foreach($posts as $post): ?>

			<a href="read.php?id=<?php 
				echo $post->id;?>"><?php 
				echo $post->title;?>

			<?php echo $post->content;?>
			<?php echo $post->created;?>

	<?php endforeach; ?>

<?php require_once(VIEW_PATH.''); ?>

Continue reading