Views exposed taxonomy filter disappeared

@Belba,
This is expected as its already mentioned in views setting. Attaching the screenshot.

Check this note when you try to put exposed form in block.
If set, any exposed widgets will not appear with this view.

@shailja179

Thank you for the answer. I did add the block, with the exposed form to the header of my page. I updated this in the steps. I should have been more clear. The issue persist.

Yes, you can add that form in other part of view(header,footer) as a block. Thats why we need to expose filter in block otherwise it comes above view if we don't expose to block.

Sorry title changed by mistake.

Moving to active as there is no patch to review

Tried the steps to reproduce, my steps:
* Umami install on 11.x
* Create node View
* Add title filter, exposed
* Expose filters in block
* Add block to page header => Filter show on every page
* Add filter on 'Tags', dropdown, exposed, allow multiple
* Reload page with the filters => Filters still show

What critical step am I missing to reproduce this?

@Lendude

Thanks for the follow up.

The most important step is that there must be a filter of type entity reference(taxonomy) field in the exposed form.

To save work you can make views of articles and in the filter criteria make a filter on the 'field_tags'. Also create a filter for the titles, as you did in the previous section. The exposed filter is shown! The title of this topic has been edited by another user.

Then go to the TWIG template responsible for displaying the views exposed form : views-exposed-form.html.twig. Do a {{ dump() }} function to inspect the variables. The result is not displayed, the exposed form disappears.

Remove the filter from the type entity reference field of the views filter. Everything works as expected. The problem only arises with fields of type entity reference(taxonomy).

The problem is not there in version 10.0.9. It does in both versions 10.1.0 and 10.1.1.

Also experiencing this issue. I am surprised that this has not gained a lot of traction. Seems like a big issue for existing sites with lots of views with exposed filters.

For us the issue was from this particular patch from core: https://www.drupal.org/node/2898635 → . When this patch was removed, the filters were back.

A colleague was able to discover this issue for us.