Let me start by saying: excellent work!
it would be nice if (either from the admin/content/node or a dedicated node hierarchy admin interface) the module could provide a way of choosing a parent for existing nodes.
It would be very easy to assign and change hierarchy and file paths for all those sites with 100+ nodes. This would definitely turn out in huge improvements for sites structure with no effort at all for all the administrators.

Comments

scriptaimago’s picture

scriptaimago commented

Hi all, again me

I'm using node hierarchy and it's awesome; problem is... it's quite frustrating to implement it on already existing site with plenty of nodes;
it would be perfect if from the edit node form, it could be possible, alongside with the create "Create new child", to add a "add existing nodes as child" button. The button would open a select box (with multiple options) listing all nodes available for nodehierarchy addition.

It's just an idea, if I had any serious PHP skills, I'd dig myself in making this addition; wretched me, I don't!
I hope at list to have given you a good suggestion (a starting point?)

Thanks, hope to hear from you, Lorenzo

jbylsma’s picture

jbylsma commented
Priority: Major » Normal

One of the nice parts of NH that I didn't really know about was the integration with the menu systems; you could easily move around items using "admin/build/menu-customize". Would that help you at all?

ironbuilt’s picture

ironbuilt commented

subscribing. this would be awesome...

scriptaimago’s picture

scriptaimago commented

Hi jbylsma,
You can certainly move menu items in "admin/build/menu-customize", but aliases remain just the same even if you "bulk update" in "admin/build/path" (even if you have set [fullnodehierarchy path] as the main and only pattern).

It would be perfect if the menu panel ("admin/build/menu-customize") could update aliases and establish new child relationships in nodehierarachy.
I don't think that is possible. That's why I proposed a nodehierarchy feature to control child assignment and consequent alias update from "bulk update" in "admin/build/path"

I'm not a php coder otherwise I woud have proposed a patch or integration myself.
Thank you all for your replies.

jbylsma’s picture

jbylsma commented

I'm trying to get back into the issue queue here. I don't think your suggestion is a bad idea, but I realized that you were talking about integration with Pathauto in your last post. If you have Node Hierarchy properly setup for the parent/child relationship, you should be able to use the Nodehierarchy Recursive Pathauto module I had written. It's a lesser priority to get it integrated in with Node Hierarchy, but it should help get your site updated easier.

webdrips’s picture

webdrips commented

Hi @jbylsma. Does your module automatically update child paths if the parent path is changed (say via re-saving the parent node with a new alias)? If not, is there some code in it I could borrow to implement this?

jbylsma’s picture

jbylsma commented

Yup, it should, using Pathauto. It should also work with rearranging items through Drupal's menu system.