It looks like this module used to support Node Reference, but that this was dropped in 7.x-2.x. I can understand that, since Node Reference/References isn't so well-maintained.
But now Entity Reference exists, and it *is* maintained. I move for Entity Reference support in this module.
I envision a "Field API" option being added for the Hierarchy handler. This would ask for the field that contains the Entity Reference to the parent. It would respect said Entity Reference's configuration and set up the tabledrag only to allow putting children under a node that is of the right type or (optionally - this isn't a v1 necessity for me) - one that is returned in the view that the Entity Reference runs.
If anyone has solved this or has some code to help...please speak up. I'm debating whether I should take a stab at this or not. I think for now I can handle it with user training ("don't put lessons under lessons...it doesn't make any sense")...provided that I can now get the Rules set up alright to update the menus based on the hierarchy.
(Trying to avoid using Node Hierarchy and writing much code.)
Comments
Comment #1
wizonesolutionsNote that this is not a duplicate of #1777646: How to work with Entity References. That one is about using Draggableviews for content pulled in via an Entity Reference relationship. This one is about using Entity Reference fields to store and determine the hierarchical order in the view.
Comment #2
drupalok commentedme too would LOVE to see this feature coming back with ENTITY REFERENCE!
Comment #3
klonos...coming from #1777646: How to work with Entity References
Comment #4
damien tournoud commentedNote that this is precisely what the Tree module is for.
Comment #5
dobe commentedPlease check out my patch at https://drupal.org/node/1879408 I am currently using it in production for entity reference parent's
Comment #6
istryker commented