Can't select a default bundle when using entity reference views

Can you edit your reference field and just select only one allowed bundle?
That will cause the bundle dropdown to disappear.

I have the same issue.

I have also the same need

I have the same case as #2. After some digging, it does seem to work when i filter per view and hard code something like this as a test in i_e_f.module file at line 334 +/- inside the inline_entity_form_settings() function inside the elseif ($field['type'] == 'entityreference') { ... } below everything else in that function.

    // Make sure that if we are rendering a view we fake
    // setting a bundle. It's not used, and only exists to suppress
    // the rendering of the bundle select on the node form.
    if (!empty($field['settings']['handler_settings']['view'])) {
      $settings['bundles'] = array(array());
    }

A bit below this line i read a foreach ($info['bundles'].....)... that 'bundles' isn't set if you use my attempt, so this should just work. At least, the select is gone, and the content displays just fine, filtering is done via Views anyway.

edit: after testing some with the cer module (Corresponding entity references), i notice that when i select a view for selecting entities, cer will stop working. So we do need a bundle and this is not enough.

@Rob C Sounds like a good idea to me although I think people may want to select which bundles can be created rather than hard coding.

A views is being used to filter what can be referenced, it should also be responsible for defining which bundles may be created.

I have applied the attached patch for my use case (Taxonomy Terms) (but should be easy to convert for all entity types) and this allows bundles to be selected from within views using the "Taxonomy term: Vocabulary" filter, the selection made here will be reflected in the node edit forms.

Once reviewed if people think the approach used is good then I can roll new patches for node content types etc.

I don't have a user case for Taxonomy, but if you produce a patch for node content type I will be happy to test and report.
I think this feature is important.
Thanks

Here's a patch that integrates with node views to limit the bundle selection field.

Revised patch #8 to be correct for bundle values.

This patch does not apply anymore against 7.x-1.5 and this feature has not been implement yet.
That means there is no way to make sure that if using a view for the entity selection, only the bundles which are returned by the view are available to create.
Anyone able to port this patch against latest dev version or point to another working patch?
Thanks

Update patch to work with 7.x-1.5

The previously attached patches did not work for me because I was referencing entity types other than node. This patch simply tests if the handler is a Entity Reference Selection Handler, and clears the $settings['create_bundles'] array.

I haven't found any ill affects in this approach. EntityReference doesn't require a bundle.

This logic should probably be in inline_entity_form_settings. But I could not decipher the impact of that change. If agreed, I can refactor.

Patch #12 works a treat :)

Corrected patch file - changed paths to files to be from module folder instead of from drupal root folder.

#16 is works well!

#16 works for me too - thanks for the update

#16 works for me as well.

Patch works a charm, and while it's a bit of a pain in the butt to have to load and execute a view just to get the bundle filter values, it is a seamless user experience and fixes the issue nicely.

I can't commit a patch that works only for nodes.
Get the entity keys, search for the bundle key, make it generic.

Attached is a patch, that uses the same approach as #16, but should work for any entity. I also added a check of contextual filters, if no filter on the bundle is present.

Patch by FeyP Worked like a charm for me.

Please ignore, posted to the wrong thread.

Works for me as of the IEF 7.x-1.6 release (dev) as well. Any chance of getting this committed?

The recent update to 1.6 caused the issue for me again and I had to calm the masses, find and reapply the patch.

Thanks all!

Patch in #1872316-22: Can't select a default bundle when using entity reference views works great for me as well. Will this be committed sometime in the future?

#1872316-22: Can't select a default bundle when using entity reference views Tested and works well! :)

Worked for me too, i'd love to see this commited :)

revised patch at #22 Works for me too - would be great to see this patch moved to dev. THANKS!

#22 worked nicely. Thanks! I'd also like to see it committed to dev

#22 is working. May it be commited?

#22 is working. Thanks!

Same in D8 - https://www.drupal.org/node/2729333

#22 solved my problem. Will it be committed?

Confirming also that this works and should be committed

#22 also worked for me.. thanks alo @FeyP

#22 also works for me. Thanks.

#22 tested and works on 7.x-1.8

The patch on #22 works for me as well.

#22 works like a charm. Thanks!

Applies to 7.x-1.9 cleanly and still relevant

#22 works!