"Expose this filter to visitors, to allow them to change it." is not updated in view editor and is not updated on view configuration after edit it.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

merlinofchaos’s picture

Status: Active » Postponed (maintainer needs more info)

Interesting. I just tried this and it's working fine for me. Perhaps there is something interefering, such as a javascript crash. Can you look in your javascript console and see if there are any errors when you click that checkbox?

pluca’s picture

I'm sorry but the failure is related to "Order Criteria" not to "Filter Criteria" : the new UI make me a little bit confusing.
I don't have any error on javascript console when i click the checkbox.
I describe better the situation :
I have a view created with beta1 with "Order" on 3 fields all exposed. When i open the pop-up to change the "Exposed" flag, it is unchecked (in the pop-up the "Expose" flag doesn't reflect the real view status).
So I created a new "Order" with a new field and it was (normally) unexposed. I changed the flag in the pop-up but after "Apply" the changes to the filter wasn't exposed.
This situation doesn't happen for "sort order" in the same pop-up : this work.

dawehner’s picture

Status: Postponed (maintainer needs more info) » Fixed

Okay commited a fix to 7.x-3.x and pushed.

* The checkbox value itself
* The description of the checkbox

This will we part of beta3.

Waldknoblauch’s picture

Still the same problem (Expose this filter to visitors) in beta3 version ...

dawehner’s picture

Status: Fixed » Postponed (maintainer needs more info)

@4

Can you provide some more context, a screenshot etc.

Waldknoblauch’s picture

Waldknoblauch’s picture

... the problem was the module http://drupal.org/project/entitycache. now it works!

bojanz’s picture

What does entitycache have to do with views sorts? That's odd

dawehner’s picture

Status: Postponed (maintainer needs more info) » Fixed

Anyway, it's fixed now :)

pluca’s picture

Component: Views Data » exposed filters

The problem was still there... but in my configuration the problem was the "AT Admin 7.x-1.0" theme. Problem solved after switching to Seven.

Anonymous’s picture

I'm having the same problem, using dev version. when clicking on the "expose this filter to visitors" and then "apply" (and then saving), the filter remains un-exposed. re-editing the filter reveals that it did not save the "expose to visitors" preference. sorry for my ignorance, and please let me know what more information i can provide you with. i really appreciate any help or advice!!

update - for whatever reason, disabling panels and location modules fixed this. thanx.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

shawnxiong’s picture

Version: 7.x-3.0-beta2 » 7.x-3.0-beta3
Status: Closed (fixed) » Active

I'm having the same problem with 7.x-3.0-beta3 version. I clicked on the "expose this filter to visitors" and then "apply" and "save", but this flag didn't save at all. I really appreciate any help or advice!!

Thanks very much!

dawehner’s picture

Status: Active » Fixed

Please checkout the current dev version it's fixed there already.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Walter Johnson’s picture

I have the current dev version and the flag doesn't save. The filter is never exposed.

spenoir’s picture

Version: 7.x-3.0-beta3 » 7.x-3.x-dev

This is still an issue in Drupal 7. Not sure what version of 7 I've got but it was downloaded recently

namdq’s picture

Try to disable Devel module first then expose the filter, I got problem too and this solution works well.

spenoir’s picture

Thanks namdq it does work well, actually it seems to speed up the admin too

jensen9090’s picture

reason:Exposed filters on View pages use URL querystring variables to pass the filter variables back to the server, but when your view is displayed in a block, this isn't possible.

how to make it work:Simply set the "Use AJAX" option to "Yes" in your view's "Basic settings" and your exposed filters will magically appear in your View blocks.

I find this solution at [http://drupaleasy.com/quicktips/exposed-filters-block-views]

Vote_Sizing_Steve’s picture

I'm having the same problem in my view, which only has one page (no block views). I've attached a screenshot of the firefox/bug output after I 'disable' the errors generated.

I am running on a Acquia Dev local server; and encountered this problem yesterday on an old build with my Artisteer theme. I also have artisteer themes enabled in today's build, but am no longer using them with this view.

kupide’s picture

Status: Fixed » Closed (fixed)

I'm having the same problem

Liliplanet’s picture

Status: Closed (fixed) » Active

subscribe thx! 'expose this filter to visitors' does not save ..

dawehner’s picture

Status: Active » Fixed

Please disable the button_style module, it causes the problem.

sstacks’s picture

As with others, disabling the Devel module (actually, some of the Devel sub companion modules that come bundled with Devel) corrected this issue for me.

I have seen several recommendations on this thread for disabling moules, some of which I don't have installed. There is obviously something that interferes with saving the exposed filter option that is not related to any one module but several.

MeDAN’s picture

AT Admin theme was also the problem in my project. Thanks pluca ;)

Automatically closed -- issue fixed for 2 weeks with no activity.

jrbeeman’s picture

Just a note -- we ran into this issue today during a training. If you have the Theme Developer on, it can interfere with various aspects of the Views UI (among a vast host of other things), so if you run into the issue of not being able to fully expose a filter in Views, make sure Theme Developer isn't enabled and look for other modules that may be interfering with jQuery- and AJAX-related operations.

Charles wang’s picture

I also ran into this problem as jrbeeman said, thanks to jrbeeman for your advice.

sunsetco’s picture

Likewise for me.
Setting the flag for "Expose", Save, then check the setting and the Flag is unset.

All the other controls on the settings stay, but not "Expose".

dmegatool’s picture

Disabling the Devel module worked for me. Was having the issue described but now it works.

hgneng’s picture

Disabling the Devel module worked for me (7.x-3.1) Thanks a lot!

garrettfisher’s picture

Me too. Disable Devel mod makes this problem go away.

eltioseba’s picture

I was having the same problem. Disabling Theme Developer (not all Devel) solved the issue.

Anonymous’s picture

Same problem here. I have a clean minimal Drupal 7 installation, with ctools and views enabled. Looks like this issue is theme related (artisteer 3.1 theme), cause exposed filter state not saving only when that theme enabled. Any ideas where to dig in theme files?

marcel.jtf’s picture

Thanks @jensen9090. The AJAX option did the trick for me.

Amir Simantov’s picture

#24 - this helped me! button_style module was the problem.

Dimm’s picture

Problem: Zircon Theme ( Base on Nucleus base theme)
Garland - Ok