Closed (won't fix)
Project:
Inline Entity Form
Version:
7.x-1.1
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Feb 2013 at 04:39 UTC
Updated:
1 Jul 2013 at 10:44 UTC
Jump to comment: Most recent file
Comments
Comment #1
bojanz commentedYes, this is by design. THe single value widget is add / edit only.
We should document this better. Any suggestions?
Comment #2
bsandor commentedHi,
I don't have technical suggestions as I just met this module. Also I'd like to thank you all the effort you put inthere. I love it.
My theoretical idea is the following:
- i'm ephasizing that we are talking about a single value widget here
- you can set up with a flag if you want to use an inline node add/edit form or the style that is used on 'multiple' widget
- once you choose inline add/edit: the current way is going to happen & once you choose the other way (what to call it here???) than the multi widget works without saying 'X left from Y'.
This scenario helps adding existing nodes/entities, also doesn't overwhelm users.
In case code stays the same I'm going to use multiple widget as i really need add/remove/browse functions.
Thanks
Comment #3
robin.prieschl commentedHi
First of all, love this module, it is extremely useful and makes it much easier for the end user.
Wanted to find out what yours and others thoughts are. I think there is merit to having a lookup for single value widget as well. Something to similar to the image below.
The user would be able to search for existing nodes, or clicking on the "Add a new {Content Type}..." link brings up the form below.
One could also dispense with the link and perhaps disable the add new node form when a user types a value into the lookup form as one cannot have values in both.
What are your thoughts?
Comment #4
robin.prieschl commentedHi
First of all, love this module, it is extremely useful and makes it much easier for the end user.
Wanted to find out what yours and others thoughts are. I think there is merit to having a lookup for single value widget as well. Something to similar to the image below.
The user would be able to search for existing nodes, or clicking on the "Add a new {Content Type}..." link brings up the form below.
One could also dispense with the link and perhaps disable the add new node form when a user types a value into the lookup form as one cannot have values in both.
What are your thoughts?
Comment #5
bsandor commentedlook at this http://drupal.org/node/1917838 post. That's my idea about it.
Comment #6
bojanz commentedYou're free to use the "Inline Entity Form: Multiple values" widget with "Allowed number of values: 1" for this.
The "Single value" widget is intended to stay simple and is used widely in our contribs because of that.
Comment #7
anton-staroverov commentedI'm working for the years as usability experience designer and can confirm that it's a really critical issue from the usability point of view.
The behavior of "Multiple values widget" is very inconvenience - because it forces end user to select between "Add new" and "Add existing" buttons - which means one additional and unnecessary step!
There is only one correct solution for that (like described in #3):
We should provide autocomplete input field by default (for selecting existing entities).
And display "Add new entity" button - like core "Field" module do.
Comment #8
anton-staroverov commentedComment #9
bojanz commentedLet's keep this issue closed.
There's a feature request for what is described in #7 and I just replied there: #2025457: Combine "Add New" and "Add Existing" workflows.