Saturday, September 1, 2012

Using CTreeView with NestedSetBehavior in Yii

Getting this whole thing to work took me a few days of experimenting. Finally I've got it working. Posting it here hoping that it would save others some time and if I need it back in the future.

The Yii nested set behavior extension can be found at

Download the zip file and then extract it into the "app root"/protected/extensions/NestedSetBehavior folder. Make sure that the NestedSetBehavior.php can be found at "app root"/protected/extensions/NestedSetBehavior/NestedSetBehavior.php.

Then modify the model file which you want to use the behavior with. For example, I have a model Areas and the file "app root"/protected/models/Areas.php. Add to the mentioned file the following lines:
 public function behaviors()
  return array(

The table for the model has to have the lft, rgt, level, and root_area field. All the field of type integer. The hasManyRoots determine whether the behavior should support more than 1 root per table, and so if it is true, the root_area will contain the root node id.

Then you need to modify the actionCreate and the actionUpdate method of the controller to use $model->saveNode(); rather than $model->save();

And that should be it to get nested behavior working. But.... how would you display it using the CTreeView widget? And how would you update it using that?

To display the tree, in the view, it is as simple as:
$this->widget('CTreeView', array(

But to get the $treedata? I've added the following 2 function into the model file.
public function treechild($id)
  $curnode = Areas::model()->findByPk($id);
   $childrens = $curnode->children()->findAll();
    $out = array();
    foreach($childrens as $children){
    return $out;
    return null;
  return null;

 public function treedata()
  $roots = Areas::model()->roots()->findAll();
  $out = array();
  foreach($roots as $root){
  return $out;

The treedata function would iterate over all the root nodes in the table and the treechild function would iterate over all the child nodes so that the data would be put into a properly formatted data structure. The CTreeView require an array with at least the id field for id, and text field to be displayed in the tree.

And so the controller is as simple as:

But that's only good for displaying the tree, to fully modify the tree (add new nodes and updating existing nodes), I need to add the following javascript to the view:
$('#treelink li').on('click', function(event) {

And the following menu (do note that I'm currently using the default layout which displays the menu widget):
 array('linkOptions'=>array('id'=>'create'),'label'=>'Create Areas', 'url'=>array('create')),
 array('linkOptions'=>array('id'=>'edit'),'label'=>'Edit Area', 'url'=>array('update')),
 array('label'=>'Manage Areas', 'url'=>array('admin')),

And in the create view:
echo $this->renderPartial('_form', array('model'=>$model,'parent_id'=>$parent_id)); 

And in the _form view:
 echo CHtml::hiddenField('parent_id',$parent_id);

And in the actionCreate method in the controller, added after the "$model->attributes=$_POST['Areas'];" line:
    $parent = Areas::model()->findByPk($_POST['parent_id']);

And the render line would be changed to:

So what the whole thing actually did, was to bind the li items in the node tree to change the create and edit link when clicked. The create link will be changed so that the currently selected node id set as parent_id and the edit link is changed so that id is the currently selected node id. Once the create method received the parent_id variable, it would be passed on all the way into the form. And once saved, if the parent_id actually exists and points to a real node, the new node would be set to append to the aforementioned node. There isn't much change for the update method.

And that folks, is how you would use the CTreeView with the NestedSetBehavior.


Anonymous said...

That extension is SOOOO poorly documented. The methods are all named to do things other than what they actually do. It's a shame because it's clearly a lot of hard work, but half-ass documentation makes it a real pig to work with.

Anonymous said...

Poorly documented?
You mean NestedSetBehaviour?

Actually it is pretty well documented.
ROFL - stop complain, start to read.

Thanks for your article.

Haiya ala Solah