It's for 7.x-4.x-dev really.
The patch contains:
- some fixes (such as removing missing JS file reference)
- moving menu related settings in nodehierarchy_menu module
- a draggable form with entire hierarchy tree for any node in hierarchy (convenient replacement of draggable menu interface when nodehierarchy_menu module is not enabled)
Other changes I'd like to see:
- optimize hook_node_load() by checking if node can be in a hierarchy before performing DB queries
- add nodehierarchy_ancestors module which stores all ancestors (not just parents) of the node and provides views relations and filters for node ancestors
BTW, nodehierarchy and nodehierarchy_menu modules defines the same DB table. This should be solved in a smart way.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | nodeheirarchy-n2167269-8.patch | 12.38 KB | damienmckenna |
Comments
Comment #1
maximpodorov commentedComment #2
maximpodorov commentedThe updated patch includes the following modification:
- the items of irrelevant node type are deleted from the tree, not just marked as disabled
Comment #3
damienmckennaComment #4
damienmckennaThe patch doesn't apply anymore.
Comment #5
damienmckennaRerolled.
Comment #6
damienmckennaComment #7
damienmckennaAfter saving a node the following error shows:
Notice: Undefined variable: nodes in _nodehierarchy_save_node() (line 750 of nodehierarchy.admin.inc).Comment #8
damienmckennaSo _nodehierarchy_save_node() didn't need a return statement after all.
Comment #9
maximpodorov commentedI'm developing a new general framework for entity hierarchies, since this project can't satisfy all the requirements of complicated projects (like multiple hierarchies containing the same entities).