Based on

Maybe adding a select list would be the first one I can think of. Add ability to select multiple variants, if selected.


Views or VBO widget would be ultracool.

The existing entityreference integration should allow the "Reference existing" autocomplete to pull results from a view.

That's as far as IEF 1.x will be able to go.
After #1881616: Move the inline forms (add, edit, remove, reference existing) to modals is implemented, we might be able to go further, but in general using a View as a selection widget requires huge hacks and the resulting bugs are usually not worth it.

Hi, coming from

Would love to be able to filter on producttype, because I have different producttypes which needs to be handled by different product displays (nodes).
Right now all products are shown on "existing variants" and they are only possible to select using autocomplete widget. These are much to much products sometimes for a producttype which sometimes only has 20 relevant productvariants.

Thanks a lot in advance for considering getting this in.
greetings, Martijn


For your remark on which you are referring to "which for entityreference fields should allow fetching from the results of a view as well, but I haven't tested that yet"; made a new issue:


Priority:Minor» Normal

I was assuming there was a way to configure this to just enhance the existing entity_reference widget (whatever it might be) to inject a "add new" next to what's there. In my case, the content creators aren't already going to know if they can reference existing or need to add new. In some cases, they just want the dropdown of existing values. In others, they need to see and try the autocomplete first. Only if they don't see what they're adding would they want to click a button and wait for the ajax reload to replace the form element.

Also, if you set the widget to a IEF - single value it *always* embeds the inline add form and doesn't let you select an existing at all, making the 'Allow users to add existing nodes.' widget setting checkbox (and the related settings that are revealed if you check it) meaningless. ;)

#1881616: Move the inline forms (add, edit, remove, reference existing) to modals won't really help this (and in some ways would make it worse). I just want to see the selection widget I've already got when the form first load, and if I need to add a new entity, click a button for a modal or ajax inline rebuild. I haven't dove into the code yet to understand why this would be so hard. But, I might be willing to spend some effort making it happen since my itch is itchy these days. ;) Any advice or pointers would be appreciated.

Based on a quick search of the IEF issue queue, this seems like the right issue to be discussing this in, but if not, please point me to a better one.


I agree with Derek's assumption that most Content creators will not know whether their Term already exists. They should be able to begin typing the term (if using something like Chosen jQuery) for the select list; when it comes up blank, they would continue typing the complete name which would open the new Add form fields with the typed name in the Title field.

Is this on the drawing board? I don't think I can implement IEF until it is, as nice as it is.

No, I have no time for work of that scale at the moment. Patches welcome.

Issue summary:View changes

added "Add ability to select multiple variants, if selected."