How to load models from another CakePHP application

CakePHP is great for administering database relations (tables), something like using PhpMyAdmin. But PhpMyAdmin lacks the ability to associate relations together. Admin interfaces to manage relations through associations are therefore better done using CakePHP 1.2.

However, to create an administrative application on top of your main CakePHP application is just messy and hard to maintain. One of CakePHP’s most powerful feature is scaffolding where you could declare:

[code lang=”php”][/code]

…and all controllers would have scaffolding. Unfortunately, we can’t do such magic on our deployed application. So that leaves us with only one way – make a CakePHP 1.2 Admin application that loads models from our Main application.

In summary, we did this:

  1. Create a new application called ‘admin’ to load the database and models from our existing application ‘main’.
  2. Load the models and do scaffolding.
  3. Create a simple page to link to all our scaffold views.

Ultimately, we want to maintain the admin interface as little as possible. The main application should not have changes in code.

0. Structure for this example

My models are Student, Classroom and Teacher since I like school. Here’s my rough folder structure:


  • /config
  • /controllers
  • /views
  • /webroot
  • app_controller.php
  • index.php


  • /config
  • /controllers
  • /models
    – classroom.php
    – student.php
    – teacher.php
  • /views
  • /webroot
  • app_controller.php
  • index.php

1. Bootstrapping in Admin

Edit the Admin ‘bootstrap.php’ in /trunk/admin/config/ to load models from Main application. I’m using Windows Vista, that’s why the C drive.

[code lang=”php”]modelPaths = array($main_app, $main_app_models);

// Models to be loaded, we will use this again
Configure::write(“ModelsToLoad”, array(
// import the models
App::import(“Model”, Configure::read(“ModelsToLoad”));

Previously in CakePHP 1.1, there is loadModel but that has been deprecated in favor of App::Import(‘Model’, $models);.

Also, make sure you have ‘app_model.php’ in your /trunk/main/, i.e. your Main application:

[code lang=”php”][/code]

2. Getting our database configuration

We wouldn’t want to maintain another database.php, so the Admin will use Main application’s database settings. Editing Admin’s database.php:

[code lang=”php”][/code]

Now we’ll have our models nicely loaded.

3. Setting up Admin’s controllers

We can create a file called ‘app_controller.php’ and place it on /trunk/admin/. We scaffold every controller:

[code lang=”php”][/code]

And we create our three controllers – classroom_controller.php, student_controller.php and teacher_controller.php. It looks like this inside classroom_controller.php:

[code lang=”php”][/code]

4. The Admin is done

Now, go to your Admin application to see your classrooms. Mine is at http://localhost:7171/classrooms/

If everything is done correctly, you should see your admin interface with the default CakePHP theme.

5. Setup the Admin homepage

There’s nothing at the homepage, let’s put links to our views. Remember that we write the configuration ‘ModelsToLoad’ earlier on? Now it’s time to use it.

Create a file called ‘home.ctp’ in /trunk/admin/views/pages/home.ctp. And throw in the following codes:

[code lang=”php”]

Listing all available models

  • link($model, “/”.low($model).”s”); ?>


The above reads from the array of models and make links for easy access from the homepage.



Although this looks complicated, but it’s quite easy to set up. When you have a new model, add it to ‘ModelsToLoad’ and create the corresponding controller for it. This post is originally titled “How to create a CakePHP admin inteface by loading models from an existing CakePHP application” but that is just too long. I couldn’t locate a guide on using App::import() and how models can be loaded from external applications so I had to look at Cake’s code. Due to limitations of my WordPress plugins, I had to use double quotes instead of single quotes in all my PHP codes.

Once again, CakePHP’s scaffolding is a wonderful feature. Take some time to play with it, the rewards are tremendous.

CakePHP’s built-in Pages Controller

CakePHP 1.2 comes with in built PagesController which helps you easily create static pages. It’s easy to set up, you just have to put your pages view in /views/pages/. All the codes are for routes.php.

[code lang=”php”] ‘pages’, ‘action’ => ‘display’, ‘home’));

The page title ($pageTitle) would be ‘Home’ for the above.

If you want your URL to be /about/my-company, you can do the following:

[code lang=”php”] ‘pages’,
‘action’ => ‘display’,

The page title would be ‘My Company’ this time since underscores are converted to spaces. Pretty useful.

Why some people contribute to open source

A month back, I talked to a friend I shall call Joel since his name is really Joel anyway. We had a short geek talk and he asked me if I have any knowledge on open-source projects.

“I only know how to use them, I don’t code for them,” I answered.

He continues, “but do you know of any open source project that is worth my time?”

“Well, it sort of depends on what you like…”

He interrupts, “It doesn’t matter, I want to join a project that is popular.”


And he elaborates to me, “If you want to join an open source project, should join one that is popular then can gain recognition.”

That was a sad moment for me. I shrugged and suggested “erm, maybe can try Firefox.”

On a side note, Uzyn is excited that CakePHP 1.2 Release Candidate 1 is out. I’ve been longing to consume the release candidate. Great work CakePHP team! I love your work.

Fruity birthday cake with kiwi mango and strawberry

Ahh, just some random picture of a cake I took.

How to perform routing in CakePHP 1.2

CakePHP introduces a new way of writing your routes, you can now restrict your URLs at parameter level, meaning that we can now specify URLS like /date/:year/:month instead of /date/*. This post compares CakePHP 1.1 and 1.2 routing differences. I’ll start with showing the old way first:

CakePHP 1.1 way

In CakePHP 1.1, routings looks like this in /app/config/routes.php:

[code lang=”php”]Router->connect(‘/date/*’, array(‘controller’ => ‘posts’, ‘action’ => ‘p_date’));[/code]

And the corresponding method in the controller would look something like this:

[code lang=”php”]
function p_date($year, $month) {
$posts = $this->Post->findAll(
“MONTH(pub_date)=$month AND YEAR(pub_date)=$year”
$this->set(‘posts’, $posts);

CakePHP 1.2 way

There isn’t much changes in CakePHP 1.2’s routing handling statement except that now it uses 2 colons.

[code lang=”php”]Router::connect(‘/date/*’, array(‘controller’ => ‘posts’, ‘action’ => ‘p_date’));[/code]

No change in the controller’s method. Continue reading “How to perform routing in CakePHP 1.2”

How to select data with month and year in MySQL

One of the easier ways to retrieve data from MySQL by month and year is to use one of MySQL’s built-in functions – MONTH() and YEAR(). The following is a piece of CakePHP code.

[code lang=”php”]function p_month($year, $month) {
$posts = $this->paginate(
“status=’approved’ AND MONTH(pub_date)=$month AND YEAR(pub_date)=$year”

If you don’t use CakePHP, a SELECT statement in MySQL would be:

[code lang=”sql”]
SELECT * FROM Post WHERE Post.status=’approved’ AND MONTH(Post.pub_date)=2 AND YEAR(Post.pub_date)=2008;[/code]

The above extracts February 2008 data. Pretty neat.

Previous I wrote crap like:

[code lang=”sql”]
SELECT * FROM Post WHERE Post.status=’approved’ AND Post.pub_date>=’2008-02-01′ AND Post.pub_date<‘2008-03-01’;[/code]

It’s just messy and ugly. And lots of calculation have to be done before hand.


Hope it helps. I haven’t really tested the SQL statements by the way. But it should work correctly. Only tested the CakePHP code. I use CakePHP 1.2’s paginate function.

What I did yesterday

I meant this as a what-did-i-do-today post but it seems like by the time I actually gather myself to type this things… Well, it’s passed 12 already. So this is a what-i-did-yesterday post.

Coding with CakePHP (PHP)

My work involves writing PHP codes. I don’t really like the syntax now that I see Python. I still don’t like the braces all over. But well… I kinda have more confidence in that. I did some work with Ruby and honestly, I think I really should stick with PHP.


Coding with Django (Python)

Oh I did a bit of learning today. Learning Django has been fun. I looked at their documentation, the developers are just amazing. So much thought has been given to the DRY principle and Django sort of enforces you to do that to a certain extend to.

My next project will be in Python/Django. It’s more of a personal project actually. But it would be interesting to see how it can work with my current company’s product. Erm… Yeah, after the examinations.

I like Django’s design philosophy

I was just looking at Django’s design philosophies and I agree on many of their points. It made me start to rethink the many mistakes that I made in coding. I often build things that are not loosely-coupled enough and when it comes to extending, things are a total mess. And I got used to working alone and I tend to get lazy and start to use the IF ternary operator (the question mark and colon) which is really messy.

  • Loose coupling
  • Less code – less code usually means less bugs for me.
  • Explicit is better than implicit – I don’t mind writing more code if it makes things clearer. The hardest thing about CakePHP is that it does quite a lot of behind the scenes things and I don’t really know what’s going on. CakePHP actually does a lot of automation for you and it’s harder for beginners to start understanding them.
  • Don’t repeat yourself (DRY) – Of course, of course.
  • Encourage best practices – Python forces you to indent things a particular way. Indentation is part of their code syntax. It would seem restrictive to begin with but it turns out to be some sort of bonus feature for me.

Continue reading “I like Django’s design philosophy”

How to get the controller’s action name from the view

You know sometimes, in CakePHP’s views, it is useful to check what is the controller’s action. It is quite useful when it comes to implementing selected tabs.

You can use the following expression to get the action name from your view:

[code lang=”php”]$this->controller->action[/code]

The following is a usage example:

[code lang=”php”]< ?php /* This is a view element file - nav_messages.thtml */ ?>
< ?php $s = $this->controller->action; ?>

  • Inbox
  • Sentbox



“messages_inbox” and “messages_sentbox” is the name of the action (function) in my controller. Continue reading “How to get the controller’s action name from the view”

How to do logging in CakePHP

Okay, I realized this long ago but it annoys me that every time I just forget this. Sometime, when debugging CakePHP, the most direct method is to simply log an error. It’s like ‘trace’ in Actionscript or just a println() in Java. Anyway, here it is:

[code lang=”php”]$this->log(“Log anything here.”);[/code]

This can be called from the controller. Continue reading “How to do logging in CakePHP”