Closed (fixed)
Project:
Node Reference Create
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Jul 2009 at 12:01 UTC
Updated:
21 Nov 2009 at 07:50 UTC
It's possible that this module is a duplicate of http://drupal.org/project/nodereference_autocreate
Comments
Comment #1
mitchell commentedThey are different. This module combines the autocomplete functionality with the ability to create nodes that don't exist. Nodereference_autocreate can create new nodes, but it cannot reference existing ones.
Comment #2
mitchell commentedI feel like this module will get a lot of similar questions, so I'm dedicating this one to nodereference_autocreate.
Comment #4
elfur commentedI'm sorry, but that quote begs the question: Doesn't Node reference itself refer to existing nodes, meaning that you don't need an addon for that?
The normal workflow with a 'create-node-on-the-fly' module available:
1. Content type A has a node reference field associated with Content type B.
2. I create a new node of type A, add relevant data and reach the node reference field. Either of two things can happen.
a) the node I need to refer to is already existing, I select it and move on (this happens either via 'select list' option or 'autocomplete' option of the normal node reference field).
b) the node I need to refer to does not exist, I create the node of Content type B on the fly using either of the two modules in question.
3. I finish creating the original node of type A.
This leads to me repeating the question: What is the difference between the two modules.
(note: I'm not biased towards either of them, I'm really and truly wondering which one of them to use for my own project).
thanks
Elfur
Comment #5
elfur commentedTo follow up on my own comment. There's a thread over at Autocreate Node Reference that gives an idea of what the difference is.
As I understand it, the other one deals with automatic creation of template-clones based on given criteria setup by the admin, while this module deals with automatic creation of a node (with a reference to the original one, setup by the user) that would be in a select list of a "normal" node reference field, had it been created earlier.
Is this a correct understanding?
If so, I suggest that the authors of both modules coordinate their comments and explanations and redirect users between them accordingly - because, then there's quite a difference between the two.
Comment #6
mitchell commented@elfur: Your understanding seems fine. Thank you for investigating the similarities and noting them here.
The differences of these two modules is also discussed in another issue for nodereference_autocreate: #494556: choose to create a new node or a created one.