hi, i'm quite new at drupal and recently comed up with the need to add hierarchycal relations between nodes, in my search i found three modules that provide this feature: "node family", "node hierarchy" and, of course, "relativity". can anyone who tried the three of them mension the pros and cons of each?

[Edit to remove all caps in title: Nevets]

Comments

KMNL’s picture

KMNL commented

Tracking...

I'd like to know from the perspective of the dev as well.

So far:

Node family has an API, built to work with views and nodeprofile/userprofile (complex user profiles, grouping many content types under the "profile" umbrella) updated OCT-04-07.

Hierarchy seems built for locations, less supported updated AUG-24-07.

Relativity provides easy "add relative node below this one" and "what this node is under" style links updated NOV-09-07.

What I'm really looking for is a module that provides hierarchy, easy add/attach buttons, outputs correctly to sitemap, and makes a taxonomy term for each entry. Any ideas?

Jkello’s picture

Jkello commented
Title: WHAT ARE THE DIFERENCES WITH "NODE FAMILY" AND "NODE HIERARCHY" MODULES? » What Are The Diferences With "Node Family" And "Node Hierarchy" Modules?

Any suggestions? I am currently deciding one of the 3

jalbro’s picture

jalbro commented

I'm dealing with this issue as well. I've currently testing "node hierarchy" and find that it does the job (with path auto as well), but I'm wondering about the other two.

I specifically want to use it to give edit rights to different parts of the site to different people.

I'm also wondering how taxonomy based menus interact with it. Can you have two different ways to get to the same node?

-Jeff

pkej’s picture

pkej commented

I think the NAT module, Node Auto Term, URLify, global redirect, node breadcrumb and pathauto modules might be of help.

I suspect the relativity module is eating memory. But it is an nifty module, I've used it to streamline the creation of travelogues. The user creates a travelogue and writes the info inside it. After submitting the user can attach points of interest to the node, which are location enabled nodes. Then a cck-view field shows a view which takes the travelogue's node id and maps all its children.

Pretty good workflow.

But, when I had an repeatable event with a reference to the travelogue, a cck-view field that took the travelogues node id to show a gmap_view, my front page ran out of memory. Ah, I also used taxonomy field module to attach fields to taxonomy fields, it might be that one which eats memory, as relativity hasn't failed me before.

At least I now know my hosting providers memory limit for PHP.