I am very excited about this module. Here's what I want to do:
I want to be able to create non-linear documents where nodes can be linked to each other in a non-hierarchical way. I understand that this makes a hierarchical menu difficult - that not a problem for me. I am using the D7 port which is largely up and running with a few glitches. If I can indeed assign multiple parents to a node then I can achieve my objective. I may be doing something dumb but I can't find a way of assigning more than one parent in the D7 port. The normal drop down list only allows one item to be selected. The alternative widget seems to be an auto-complete field but still only allows one parent to be selected.
Any insights would be very welcome. Once again - great module and in my view a better alternative to book pages which has menu issues.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | cannot-assign-multiple-parents-1166894-9.patch | 915 bytes | keithm |
| #7 | cannot-assign-multiple-parents-1166894-7.patch | 1.63 KB | keithm |
Comments
Comment #1
alexbern commentedLooking for the same!
Can't figure out how to set a node to more than one parent. There's a checkbox in content type settings to allow multi parents. No changes when set.
I need this to have the same node in 2/3 different sections. In each, the node shall have the parent's breadrumb displayed.
Comment #2
r0bm1lls commentedHmm - so now I'm thinking either its not working in the D7 port yet or that multiple parents actually means assigning a child to parent of different content types. This is all guesswork at this point. I may try this on a test D6 installation to see if something is different there. Will report on findings.
Anyhow I think this is a really great module and am really looking forward to it growing.
edit:
I set up on a D6 install. The difference is that on the D6 version there are two parent fields in the node edit page one to assign a primary parent and another to assign another parent. The second field to assign another parent is missing in the D7 port. Not sure what the intention was here.
Comment #3
alexbern commentedwhat a good idea to compare it w D6version! Maybe they've just forgot this issue to port. I should have a look at the code.
Comment #4
keithm commentedComment #5
keithm commentedComment #6
keithm commentedThis problem is due to a bug in Drupal core. See #1015798: Fieldsets inside vertical tabs have no title and can't be collapsed. The patch in comment #7 fixed it for me. To use it, save the file to your Drupal root directory and type
patch -p0 < vertical-tabs_collapsed-fieldsets_1.patchin a terminal or shell window. Windows users see http://drupal.org/node/620014 for instructions.Comment #7
keithm commentedThere are some problems in nodehierarchy as well. Patch attached.
Just to be clear, the core patch in #6 is still required.
Comment #8
r0bm1lls commentedThanks guys for all this. Tried the patch in #7 did not seem to go completely:
patching file nodehierarchy.module
Hunk #1 succeeded at 535 (offset -27 lines).
Hunk #2 FAILED at 698.
Hunk #3 FAILED at 1530.
2 out of 3 hunks FAILED -- saving rejects to file nodehierarchy.module.rej
Sorry I'm no coder so would not know what went wrong.
Also would that patch in D7 core be implemented in D7.2?
Comment #9
r0bm1lls commentedOops sorry, my bad. Tried patching the wrong version. Applied patches to core and to module and it works!!! Thanks so much. Now lets see what fiendish constructs I can contrive with this module....
Comment #10
keithm commentedI pulled a piece of patch #7 into a separate patch in #1168348: Warnings produced when creating nodes and rerolled the patch for this issue.
To fix this problem and enable the ability to assign multiple parents:
Comment #11
lebachai commentedI had no trouble apply your attached patch, but the vertical-tabs.css patch looked like it was from the 8.x version, not 7.x. Am I mistaken?
Comment #12
graytoby commentedNo luck. I tried all patches, I'm still unable to select multiple parents. I only get selection list and I can only select one node. The same applies to autocomplete widget, only one node can be entered as a parent.
Comment #13
JayKayAu commentedI'm getting the same problem. This is true both with and without the experimental Node Hierarchy Widgets module enabled.
Comment #14
Anonymous (not verified) commentedI am experiencing the same issue, the following error is displayed on Node View and Node Edit pages when multiple parents is enabled:
Notice: Undefined property: stdClass::$nid in nodehierarchy_nodehierarchy_node_form() (line 543 of /var/www/otdomainaccess/sites/all/modules/nodehierarchy/nodehierarchy.module).
Applying the aforementioned patch to drupal core fixes the issue.
Comment #15
Ganzeiba commentedSame problem here, can't add more than one parent in the Node Hierarchy > Parent field even if the option "Allow multiple parents" is active.
Comment #16
alexh commentedThe patch in #10 with the mentioned core patch solves this issue for me. Thanks a lot!
Comment #17
Courtney.B commentedRan patch #10, able to select multiple node parents.
Comment #18
skaughtadd this CSS into your theme should help with the missing fieldset (which is the result of a vertical tabs css issue). however the actual 'add' button doesn't actually work.
Comment #19
Anonymous (not verified) commentedI didn't need the patch, just the CSS is enough.
But one issue remains. Maybe the patch will help me there, I'll try in a minute.
Men you make a node that needs multiple parent from scretch or edit one, you can allow multiple parents.
But when you assign a child node than that node only saves under that parent, you need to click on edit to apply it to multiple parents...
He, it's in the good direction !!!
I also still get errors when I wont the widget module is enabled.
But hé, as I just said, I didn't try the patches yet.
Love the module, good work, keep going.