Hello,

I use Node Hierarchy module for Drupal 6.x. When I create new node, I can choose Parent node from the list. The problem is my website will be huge with very big hierarchy (2-5 levels), so it will be unrealistic to find Parent node from the list, because there will be millions of available parents.

Also, name of some nodes will be the same (for example "A", "B", "C" etc will repeat like 10 times on my website).

I'd really really like to see some grouping and hierarchy view when I create new node. AJAX is not necessary here, simple list will be fine, but in future, I'd also like to see some Taxonomy-like editable hierarchy.

If you have some devel version with this feature (or something similar), could you post it here please?

I'm not a pro PHP programmer, but I'm writing scripts for 1 year. I don't know how to write modules, but If I can help in any way, for example write some piece of code, I'd like to help.

Comments

AppleAp’s picture

AppleAp commented

Sorry, didn't think about it, users will not need groups as A, B, C, D etc, for example, always have same parent.

So, hierarchy view of nodes when creating/editing new node will fix this part of issue.

dgorton’s picture

dgorton commented

The simplest way to handle this is actually to reverse the process - go to the parent node, click the children tab and create a new child of the appropriate type. That will create a new child with the appropriate parent already chosen.
We've got oodles of sites with significant content, and that's how we do it. That's a change to your process, but you can use it to get the job done right now.

AppleAp’s picture

AppleAp commented

Thanks for an idea, actually now I add new nodes same way you described.

But now I have just few nodes. When I will transfer my websites to Drupal, the "parents" list will contain millions of pages. I guess any browser will freeze when it will try to load such list. :)

Another problem is if I will need to change parent for a node. I will need to go to MySQL and change parent manually.

ronan’s picture

ronan commented

I don't think node-hierarchy has been tested with millions of potential parents, and am not sure how it will hold up under that kind of load.

Often on larger sites, I create a 'section' type which can be parents and a 'page' type which cannot. This reduces the number of potential parents to only those that make sense.

My longer term plans include improving the way parent's are stored to improve scalability and to have other options for choosing parents that can handle a large number of nodes.

AppleAp’s picture

AppleAp commented

Often on larger sites, I create a 'section' type which can be parents and a 'page' type which cannot. This reduces the number of potential parents to only those that make sense.
Yes, but sometimes websites really need 3-4 level hierarchy. For example, my website needs up to 5 levels (I'm not counting the main page).

My longer term plans include improving the way parent's are stored to improve scalability and to have other options for choosing parents that can handle a large number of nodes.
Ronan, do you plan to add feature I described in my first post? It doesn't need to add something big into the code, it's just the way how available parents nodes list displayed on the "edit node" or "create new node" pages.

If you plan to add such feature, can you tell me when do you plan to add it please?

AppleAp’s picture

AppleAp commented

I guess you do not plan to do this, Ronan?

Can someone tell me what module's function displays list of available parent and child nodes? I'd like to try to modify it.

HansBKK’s picture

HansBKK commented

AppleAp - see #317786: multiparent capability? and #335324: Integration with Node Auto Term [NAT] and Glossary

heatherann’s picture

heatherann commented

I would also be very interested in this as I am in the same situation as AppleAp. Once we start adding all our publications, this list is going to get unwieldy really quickly. Expand/collapse capability would make this much more user-friendly.