Can't select display so I can't reference a view

Created on 12 March 2025, 26 days ago

I type in the view, the autocomplete shows me the views available and i select the one I want to reference.

I then have to click a display in a dropdown below it but it doesn't get filled, its always empty so i can't select a display for that view and that means i can't save the node and it doesn't work.

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

🇬🇧United Kingdom effortDee

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @effortDee
  • 🇬🇧United Kingdom scott_euser

    There are a couple issues in the queue around the autocomplete which could help but the easiest of you don't have 100s of views to choose from is to switch to the select widget in manage form display.

  • 🇬🇧United Kingdom effortDee

    I have no problem selecting the correct view using autocomplete, it populates the field but i then have to select a display in a drop down beneath that, usually stating Default, Block, like that.

    But nothing appears in that drop down for the display so it won't actually reference the view and i can't save the node.

    I have got around this by adding unlimited view reference fields on manage form and then i add a second, reference the view, select the display then remove the first empty views reference field and that gets around it.

  • 🇬🇧United Kingdom scott_euser

    What I mean is on the entity you added the field to, go to manage form display, and change to the select widget instead. Then both the view and display fields are selects rather than the view field being an autocomplete.

  • Im having the exact same issue.

    Changing the form display to be a select list instead of auto complete does fix the issue but its not great that the module field was being perceived as entirely broken in its default form state.

  • 🇬🇧United Kingdom effortDee

    Scott i have thousands of views, so yes this would fix that issue, but autocomplete is the default form state and it now takes me quite a while to find the views i want to reference.

  • 🇬🇧United Kingdom scott_euser

    Oh absolutely contributions very welcome to help sort. I am only saying valid workaround. For now I did this in default core install with this module enable and blocks load fine:

    1. Added 2 Blocks to the Admin > Content View at /admin/structure/views/view/content/edit
    2. Created a Views Reference field in Article and left as default autocomplete
    3. Attempted to create an Article and select a View, and I correctly get the two blocks

    So it seems default use case works fine. Needs more info to reproduce in a clean install, error details, console errors, etc as appropriate.

Production build 0.71.5 2024