Exposed Filter is not showing in a block view

By roh846 on 11 Aug 2009 at 03:30 UTC

I have a block view with an exposed filter. The filter is not showing up in the block view. I have no clue what to do.

Some of the posts say that we need a page view with a path to have the exposed filter.............didn't work.

Comments

Just to clarify

dddave commented 11 August 2009 at 08:11

The exposed filter is by itself a new block. Have you enabled and configured this new block on the blocks admin page?

Yes, I know that is one way

roh846 commented 11 August 2009 at 13:25

Yes, I know that is one way of putting the exposed filter. What I'm trying to do is to include the exposed filter with the block view itself...............

Same here.

tpainton commented 14 August 2009 at 21:40

Same here. I have a block with a view.. It has an exposed filter. I would like that included in the original block with it's view.. is this possible?

Exposed form in block

dambrisco commented 14 August 2009 at 22:02

If you want a separate block for the exposed filter, this should be set to Yes. If you want the filter to be in the View's Block display, make sure that the Block display's "Exposed form in block" option is set to No.

Depening on the configuration you're attempting to achieve, you might want to override your default settings.

I know this is a very old

hockey2112 commented 3 January 2014 at 23:31

I know this is a very old post, but I just wanted to say "thank you"... your method/settings worked great for me!

It worked!!!

pena007 commented 21 November 2019 at 21:43

New filter criteria were not displaying, I adjusted the Exposed form style and Use AJAX with no avail.

The only option that worked for me was "Exposed form in block: Yes"

I was then able to apply the block to the correct region/page.

Same here

echoz commented 27 August 2009 at 07:52

I'll join this group of now 3 people who have this happening. I also have a page view (yes, with path) where the exposed filter is working. My block's behavior with the filter enabled might shed some light. The filter selects options that might be in one of the fields. When it's enabled for the block view, the filter form does not show, but it filters to only show the rows of my view that have the a term of the filter, in other words, it doesn't default to "Any", even though the filter is set to "Optional". The block view also has an argument, but it's a different hidden field and seems unrelated. I've tested a huge amount of configurations. Hope this adds info leading to an answer!

Solved, use AJAX

echoz commented 27 August 2009 at 09:04

http://drupal.org/node/288101

AJAX

PaulMagrath commented 9 September 2009 at 19:25

AJAX solution linked to above effectively closes this issue. The AJAX based work-around is extremely slick. It would improve usability though if Views generated a warning if filters are exposed and AJAX is set to off though.

AJAX Solves

jillpadams commented 8 March 2012 at 20:57

Enabling Ajax gave me exactly what I needed! Thanks all.

Thanks Ajax solved the

dekiche commented 5 April 2018 at 06:12

Thanks Ajax solved the problem

Thanks, turning on AJAX fixed

OldAccount commented 6 January 2010 at 14:33

Thanks, turning on AJAX fixed the problem for me too! I agree that it should be a little more clear that this is required, the whole "exposed form in block" setting confused me as well.

Thanks

svh commented 1 July 2010 at 10:57

Turning on Ajax helped....

Use AJAX

Farnoosh commented 2 February 2018 at 15:52

Thanks, turning on AJAX helped here too.

Drupal 7 :

Exposed form style: Basic

Use AJAX: Yes

Funny, this worked fine for me w/o Ajax, until views-6.x-3.0

anonymous07 commented 28 September 2010 at 14:13

All the exposed filters disappeared and enabling Ajax brought them back.

Thanks for the info!

Error in IE8

juice1492 commented 1 October 2010 at 12:29

The Ajax fix works great for Chrome/Firefox. But in IE8 I get a js error: Invalid Argument - ajax_view.js line 28. Has anyone else run across this or have a solution?

Thanks

Found my problem

juice1492 commented 1 October 2010 at 13:34

Another post mentioned IE8's "pickiness" when validating the DOM; I discovered that I had a missing closing tag that was invalidating the DOM and causing IE8 to choke

works

qqboy commented 26 April 2016 at 03:10

works @anonymous07

https://www.drupal.org/project/image_captcha_indicator
https://www.drupal.org/project/ext_js

Issues finding the block?

nick0989 commented 19 June 2017 at 15:22

I had an issue finding the name of the block when it was created in the advanced menu tab. What I had to do was load my browser with old data, go in and change the view on another browser and then compare the list to one another. It ended up being there as an "exposed form: [name]." I was looking for something along the lines of "view: [view name]:"