First try to find the leaves:

Then for each do

Then check if the lineage is correct, I don’t know a way to handle all you want in one query. This will select all visible parents. I usually store the parent_id in a column with mptt so I can derive whether a parent is missing. The other way would be to get the entire lineage of a leaf and then see with a loop in php whether all parents are visible.

I’m not sure it can be done any faster, maybe the more sql proficient know.

This looks great. Thanks for the contribution!

I wonder, is there some way of making the tree2array work nicely with CodeIgniters ol() or ul() HTML-helper?

Ok, been busy and now I’ve noticed your question when checking all suggestions (be patient, I’ll implement some of them), so here comes the answer:

No, I’m afraid not.

You have to either convert this:

To

Or you could use something like this:

Hey, I just understood the whole “MPTree” concept. I actually started implementing the same thing for the CodeExtinguisher site ( http://71.65.20.84:81/codexsite/index.php/docs/setup )

I remember you were interested in implementing this feature into CodeExtinguisher. If you still are, I’m willing to work through it with you. I haven’t actually tried MPTree yet, but it seems perfect for my use.

I think it would be a very nice addition, both to CodeExtinguisher and MPTtree, to have a good admin interface for storing tree data in a database.

I’m going to make some other additions to MPTtree and it would be nice to make a release “with” a full admin interface, so I’ll gladly work with you.

Cool, I can include this as a “view mode”. Take a look at the preview (in my signature), and see how there is the ability to use different view_modes? If you want more info on view_modes in the context of CodeExtinguisher, take a look at the temporary docs also linked to in my signature.

Ummm, the view_modes page in your wiki is empty.
But I think it’s not a bad idea. It could be useful with also a “flat” table manipulation option.

The things needed are a few buttons/drag-drop, etc.
Can view modes handle this in a nice way?

oh yeah, i thought I had written that page. In any case, yeah, each file in CodeExtinguisher can load its own assets.

That sounds fine.
Maybe we should continue this discussion via MSN or skype.

(While this is increasing our post count , I don’t feel like filling a whole thread with a conversation)

haha yes I don’t want to steal your thread, could you PM me your email? gmail, msn or skype work for me

I’ve now started to code on MPTtree version 0.2

Some things I’ll add/edit:
- The Fusion feature, the addition of parent_id (an optional option, a fusion between Nested Sets and Adjacency list)
- Remake the locking system (not so much, but it will hopefully make it easier for me)
- A few new methods for the ORM (will be added in ignitedRecord as well)
- Renaming of a few ORM methods, to not confuse the user when using MPTtree and IgnitedRecord

So I ask:

Are there any specific features/changes you want to see in MPTtree 0.2?



PS. Wondering about if I should drop the ORM feature of MPTtree and concentrate my ORM work on IgnitedRecord, what do you think?

Hi there,

thank you for sharing this nice work ...

Is it possible to have multiple trees in one db-table?

Greets,
yami

No, but you can use a common root node for all the trees in that table:

BTW. A lot of my time is currently spent on coding IgnitedRecord, but I’ll soon resume with the development of MPTtree

MPTree @version 0.1.6-fix

The mpttree->move_node_append($move_lft,$to_lft); cast an error..
However, the function does what it’s supposed to!

Great model!

I have some suggestions to it.

1. I would like to get a branch of the tree from $lft up to the root.

2. Argh, just slipped my mind. ^^

Again N I C E work! =)

That error is fixed in 0.1.6-fix2, which you can find here

If you want a branch from lft to root, use get_parents(lft, rgt).

EDITED just after post: I added the answer to the branch question.