Ah sorry… I had validation in my model on lft / rgt / lvl… But the behavior runs after validation.
And I notice the root needst left = 1 / rgt = 2 else it will move the root to child
Any reason why there is not a addRoot method ?
Also it be nice to have some convience method to have the tree return in an multi dimensional associative array… As far as I can see now descendants()->findAll() just returns all records in a flat array.
Also how to get the the path? Like I select a category but want to get the entire path all the way up, usefull for breadcrumbs and filtering in categories.
like…
SELECT parent.name
FROM nested_category AS node,
nested_category AS parent
WHERE node.lft BETWEEN parent.lft AND parent.rgt
AND node.name = 'FLASH'
ORDER BY parent.lft;
Also I see now that my first error was because validation is called before the makeRoot function… maybe better to call this after the makeRoot so the model can still have validation rules. And not have to call validate = false
One more thing how to use the delete function? If just get the model instance and delete it will not be called… and will not remove the descendants. Shouldnt it use the beforeDelete event?
Because if i change it too:
/**
* Deletes node and it's descendants.
* @return boolean whether the deletion is successful.
*/
public function beforeDelete($event) {
parent::beforeDelete($event);
$owner=$this->getOwner();
if($owner->getIsNewRecord())
throw new CDbException(Yii::t('yiiext','The node cannot be deleted because it is new.'));
$transaction=$owner->getDbConnection()->beginTransaction();
try
{
$root=$this->hasManyRoots ? $owner->{$this->root} : null;
if($owner->isLeaf())
$result=$owner->delete();
else
{
$condition=$this->left.'>='.$owner->{$this->left}.' AND '.
$this->right.'<='.$owner->{$this->right};
if($root!==null)
$condition.=' AND '.$this->root.'='.$root;
$result=$owner->deleteAll($condition)>0;
}
if($result)
{
$first=$owner->{$this->right}+1;
$delta=$owner->{$this->left}-$owner->{$this->right}-1;
$this->shiftLeftRight($first,$delta,$root);
$transaction->commit();
return true;
}
}
catch(Exception $e)
{
$transaction->rollBack();
}
return false;
}
Both with the commented attributes set and unset. I feel this implementation detail should be hidden, I didn’t even know if the counters start at zero or one until I read some comments in this thread, and maybe it is hidden and I don’t have to care about it. Just still didn’t find out.
In the end, this always throws an exception “Many roots mode is off”. And since it’s a new record and since I can’t save the AR using CActiveRecord::save, I’m feeling kind of lost here.
In the end, I created the root node directly in the DB (lft:1, rgt:2, level: 1, root: null) and managed to insert a node using the following snippet of code:
Is there a chance to get some small code snippets for each of the provided API methods? For example it seems to me as if the saveNode method is useless in single root mode, but maybe I’m using it the wrong way.
I’m trying to understand what values are stored in the ‘root’ field and the ‘level’ field. I wouldn’t need to know this except that I’m building a backoffice administration app that we’ll most likely use to configure our categories. I want to make sure I use the correct logic so that this extension will work if and when I want to use it.
First of all, Thank you for implementing nested tree!
I’m facing a problem atm. The situation:
I’m making a webshop with nested categories, using the nested tree. When someone deletes a category, the program seeks for products assigned to that category and its subcategories, if found, the category must be not deleted. So I run the event beforeDelete. This works like a charm when the category is a leaf, but when it has subcategories the event doesn’t get raised because of deleteAll() used in nestedtree’s delete() method.
I think I will manually raise the event in the controller before deleting (if the category is not a leaf) and lean on the event’s return. What do you think? Anyone had a similar case?
The thing is done, tho I had to modify the extension.
I had to implement a new method into it:
public function setIgnoreEvent($ignoreEvent)
{
$this->_ignoreEvent=$ignoreEvent;
}
I did this because in the behavior beforeDelete() method checks for _ignoreEvent and if it is false, the event raising stops. What do you think? I think you should include this into the class.
So the code looks like:
$toDelete = true;
$category->tree->setIgnoreEvent(true);
if (!$category->beforeDelete()) {
$toDelete = false;
}
$category->tree->setIgnoreEvent(false);
if ($toDelete && $category->tree->deleteNode()) {
$this->messages[] = 'Sikeresen letöröltem a kategóriát.';
} else {
$this->messages['hasError'] = 1;
$this->messages[] = 'Nem tudtam letörölni a kategóriát!';
foreach ($category->getErrors() as $field => $error) {
$this->messages[] = $error[0];
}
}
Could you please add some documentation how to actually add / modify / delete nodes 
the naming confused me… i though this method id only to move and existing child to the first position