Active
Project:
Node Connect
Version:
7.x-1.0-alpha1
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Reporter:
Created:
15 Feb 2012 at 17:14 UTC
Updated:
11 Sep 2013 at 18:15 UTC
From a user experience perspective, it would be very nice if when the node-reference autocomplete field is populated, and the green plus button is clicked, instead of getting an error that the node does not exist, validation passes, sends you to the node/add form and pre-populates the title of the new node with what the user had entered into the node reference field. This is especially handy when the user has the ability to add multiple node-references to the parent node form.
| Comment | File | Size | Author |
|---|---|---|---|
| Screen shot 2012-02-15 at 11.14.12 AM.png | 62.69 KB | dgoldenbaum |
Comments
Comment #1
wbobeirne commentedIt looks like that error message ("found no valid post with that title.") is handled in the References module. I don't think this can be done from Node Connect without changing the way References handles itself.
Comment #2
MChall commentedIt seems that moving off to the referenced node calls the validation on the primary node, i.e if you also have any mandatory fields set then will also not let you add a reference node. Can the call to create the reference node be made before the primary node validation, as this is going to get run when the primary node is saved.
Another way would be to null the entry in the field on selecting the functionality.
Can help with this in anyway apart from coding :(
Comment #3
baby.hack commentedI would also like to see this functionality in both entityconnect & Node Connect.
I like that the parent node is validated before creating the child node. I ultimately think that if there is text in the reference field, and the user clicks the add button, the text should be checked against node titles to see if a node of that title already exists. If a node already exists with that title, the user should be presented with options to use the matching node that already exists, to continue to node creation, or to cancel.
If there is no matching node, or if the user chooses to continue to node creation, the content of the field should be stored, the field should be set to null, and the content that was stored should then be passed to the node creation form to be used as the title.
Comment #4
shaunlaws commentedI'd love to see this feature, as described in #3.