recursive in CakePHP

The recursive property defines how deep CakePHP should go to fetch associated model data via find(), and read() methods.

Imagine your application features Groups which belong to a domain and have many Users which in turn have many Articles. You can set $recursive to different values based on the amount of data you want back from a $this->Group->find() call:

  • -1 CakePHP fetches Group data only, no joins.
  • 0 CakePHP fetches Group data and its domain
  • 1 CakePHP fetches a Group, its domain and its associated Users
  • 2 CakePHP fetches a Group, its domain, its associated Users, and the Users’ associated Articles

Ajax request in cakephp 2.x


<?php echo $this->Html->script('jquery', FALSE); ?>


echo $this->Form->create('Count', array('action'=>'ajaxShow'));
echo $this->Form->input('field', array('id'=>'field'));
echo $this->Js->submit('Send', array(


<div id='sending' style="display:none"> Counz[dot]gif will be displayed </div>
<div id='success'></div>


var $name = 'count';

    public $helpers = array('Js' => array('Jquery'));
    //var $helpers = array('Ajax', 'Javascript');
    var $components = array('RequestHandler');
public function ajaxShow(){
         $this->layout = 'ajax'; 
            $this->render('success', 'ajax');
            $this->set('for_map', $this->count->find('all'));



<p>It's working</p>

Controller Attributes in CakePHP

property Controller::$name

The $name attribute should be set to the name of the controller. Usually this is just the plural form
of the primary model the controller uses.

$components, $helpers and $uses

The next most often used controller attributes tell CakePHP what $helpers, $components, and
models you’ll be using in conjunction with the current controller. Using these attributes make
MVC classes given by $components and $uses available to the controller as class variables
($this->ModelName, for example) and those given by $helpers to the view as an object reference
variable ($this->{$helpername}).

property Controller::$uses
Controllers have access to their primary model available by default. Our RecipesController will have
the Recipe model class available at $this->Recipe, and our ProductsController also features the
Product model at $this->Product. However, when allowing a controller to access additional
models through the $uses variable, the name of the current controller’s model must also be included.
This is illustrated in the example below.
If you do not wish to use a Model in your controller, set public $uses = array(). This will
allow you to use a controller without a need for a corresponding Model file. However, the models
defined in the AppController will still be loaded. You can also use false to not load any
models at all. Even those defined in the AppController.

property Controller::$helpers
The HtmlHelper, FormHelper, and SessionHelper are available by default, as is the SessionComponent. But if you choose to define your own $helpers array in AppController, make sure to include HtmlHelper and FormHelper if you want them still
available by default in your Controllers. To learn more about these classes, be sure to check out their
respective sections later in this manual.

property Controller::$components
The components array allows you to set which Components a controller will use. Like $helpers
and $uses components in your controllers are merged with those in AppController. As with
$helpers you can pass settings into $components. See Configuring Components for more infor-

Other Attributes
While you can check out the details for all controller attributes in the API3 , there are other controller at-
tributes that merit their own sections in the manual.
property Controller::$cacheAction
The cacheAction attribute is used to define the duration and other information about full page caching.
You can read more about full page caching in the CacheHelper documentation.
property Controller::$paginate
The paginate attribute is a deprecated compatibility property. Using it loads and configures the
PaginatorComponent. It is recommended that you update your code to use normal component

Request Life-cycle callbacks in CakePHP

CakePHP controllers come fitted with callbacks you can use to insert logic around the request life-cycle:
This function is executed before every action in the controller. It’s a handy place to check for an active
session or inspect user permissions.
Note: The beforeFilter() method will be called for missing actions, and scaffolded actions.
Called after controller action logic, but before the view is rendered. This callback is not used often,
but may be needed if you are calling render() manually before the end of a given action.
Called after every controller action, and after rendering is complete. This is the last controller method
to run.
In addition to controller life-cycle callbacks, Components also provide a similar set of callbacks.

common tasks people learning CakePHP

These are common tasks people learning CakePHP usually want to study :
1. Layouts: Customizing your website layout
2. Elements: Including and reusing view snippets
3. Scaffolding: Prototyping before creating code
4. Code Generation with Bake: Generating basic CRUD code
5. Simple Authentication and Authorization Application: User authentication and authorization tutorial



Data Validation in cakePHP

alidation rules are defined in the model.

class Post extends AppModel {
public $validate = array(
‘title’ => array(
‘rule’ => ‘notEmpty’
‘body’ => array(

‘rule’ => ‘notEmpty’


The $validate array tells CakePHP how to validate your data when the save() method is called.