Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Admin can set plugin ids for a field in the field settings. Currently views are made available to select that do not have the particular plugin id(s) selected in the settings.
Create a further filter in the Views code that removes any views that do not have the included plugin types.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | _Issue__2895108__Field_form_plugin_Id_display_selection_refinements___plugin_id_not_presen.patch | 2.46 KB | NewZeal |
Comments
Comment #3
NewZeal commentedAdding a patch for this so that it can be added to 2.x.
Note that the patch also includes a fix for when attempts are made to save a View name without a display id.
Comment #5
seanbCommitted to 2.x with minor changes. I believe the UX can be improved a bit more by filtering the view names that lead to the error (why show the view in the first field if selecting it will lead to an error right?). If we fix that we can remove the JS that shows the error again.
Comment #6
NewZeal commentedI agree, limiting the Views before they are presented would be ideal.
I had a brief look at this but attempting to filter the items available to the entity autocomplete requires deep Drupal penetration and I currently don't have the time. It may be easier to do it for the select field I don't know I haven't looked.
Comment #8
NewZeal commentedThis problem may be solved in the same way that entity reference views can be used to filter a reference field. That would be the first place to look. Anyway we should probably leave this ticket open for potential contributions.
Comment #9
NewZeal commentedNo followup occurred. Closing issue.