Here is a thought, if we use node reference then only two levels would show. The node and its linked node. How would it be built if we wanted multiple levels?

Parent, Child, Grand Child, Grate-Grand Child, ext....

I haven't tested this but I imagine that works with terms in the same vocabulary. Any way to do it with node reference though? One linked after another?

Comments

joachim’s picture

joachim commented

Multiple levels work fine. I don't really understand your question...

timefor’s picture

timefor commented

Maybe I'm doing something wrong then. Here is what I've done,

1. I have a content type called Teacher. Teacher is linked to a content type called Class through a node reference. I can see a list of Teachers and their Classes. That part works.

2. The content type called Class is linked using a node reference to content type called Assignment. I can see a list of Classes & Assignments.

3. But when I include everything in the same view I see a list of Teachers linked to Classes and a List of Classes linked to Assignments. I'm not seeing a multiple level list including Teachers linked to Classes and linked to Assignments.

Example - This is what I'm seeing,

Teacher1
- Class1
Teacher2
- Clas 2
Class1
- Assignment1
Class2
- Assignment2

This is what I want to see,

Teacher1
- Class1
- Assignment1
Teacher 2
- Class2
- Assignment2

So maybe its another documentation issue. Could someone explain how this would be setup?

joachim’s picture

joachim commented
Status: Active » Closed (fixed)

Oh right. Yeah, it won't work with that.

If teachers linked to other teachers -- say is showed who was a teacher's manager -- then you could have a multi-level tree. But there is only one field you can take parent data from.

maxplus’s picture

maxplus commented

Hi,
I'm also looking for a solution for this.
Maybe it can be solved in D7 using the Relation module?