Jotlab

Now that we have our basic layout looking awesome, let’s go ahead and start building our site up to accept urls to smash and shorten! Within the app directory and go into the controller folder. Controllers are the logic, the brains and the masterminds behind the site operations. Once an action is requested the controller jumps into action, pulling data from the database, sending it to the views and then to the browser. Think of the controller as a middleman, a middleman with a heap of power! We’ll create a blank middleman, or task for our middleman, called an action. Create a blank file within the controllers folder and call it shorten_controller.php. Next dump this basic code into it:

1
2
3
4
5
6
7

<?php
	class ShortenController extends AppController {
 
		function index(){
 
		}
?>

This is the barebones of a controller with an action. Firstly we have extended the base class of a controller object of which the geniuses behind CakePHP have created for us. Then we setup a function, called index, which just so happens to be our action! We will build upon this action now, to be our index page, of which will accept a url from a user, validate it, then crunch it, store it in the database and then redirect to another page/action to display the lucky user’s new shortened url.

Let’s get rid of this pesky CakePHP code shall we? In order to do this, we need to tell CakePHP that we have a new default action that we’d like to use for our index/default page. To do this, we’re going to have to route, and route all night long. Open up the routes.php file within the config folder. You will notice this line:

Router::connect('/', array('controller' => 'pages', 'action' => 'display', 'home'));

Awesome. We need to change this to connect our default or ‘/’ root url to the root action we created, which was Shorten::index. To do that, change the previous line to:

Router::connect('/', array('controller' => 'shorten', 'action' => 'index'));

Now check your page again! It should come out a little different. We still get a complaint, but we’re going to handle that now!

Let’s take care of this missing table error message now and sort our database out to start accepting and storing urls!

Postscript: Leave A Comment // Subscribe (RSS Feed)