Hi all and thanks for the great work on this module.
I'd like the ability to select existing nodes and assign them as childnodes in the "children" tab, using the same autocomplete feature of parent selection.
This would be a great feature, because multiple parents means lots of existing childs as candidates when creating a new node, and going throw all those childs to select a parent is not the best workflow !
And btw, the autocomplete for parents selection doesn't seem to work when multiple parents is disabled for a content type. Still investigating before flagging it as a bug.
++
Comments
Comment #1
nvakenSeeing this issue is stemming from 2010 for 6.x, is there any progress in this feature request? Would love to have this too. I've got a project running which absolutely needs this kind of functionality, currently only possible - from the parent out - to create new child nodes.
Comment #2
roderikThis patch adds an autocomplete with which you can add child nodes. In order to do this, I moved a lot of code from nodehierarchy_widgets.module into the main nodehierarchy.module, and extended all that code to work for selecting children as well as parents.
The original module uses a select element for the parents, and only after enabling nodehierarchy_widgets you get an autocomplete. What this patch still needs is:
...but I'm not going to do that now.
This patch will only apply after applying #2335219-2: Reduce database queries by caching data and #1955860-5: node can be made a parent to itself first; I don't want to juggle too many patches in a module that isn't maintained anwyay.
Comment #3
roderikAnd here's related functionality which you will want (though it arguably could be a separate issue): in the list of child nodes, add a 'remove' link to each child.
Since these things probably won't be committed for some time, for people's convenience I'm adding one big patch which includes