Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
"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.
Comment | File | Size | Author |
---|---|---|---|
#21 | Expose this filter to visitors flag does't work (Breakpoints set by disabling errors).PNG | 294.94 KB | Vote_Sizing_Steve |
#6 | Bildschirmfoto 2011-03-28 um 12.44.36.png | 113.85 KB | Waldknoblauch |
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedInteresting. 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?
Comment #2
pluca CreditAttribution: pluca commentedI'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.
Comment #3
dawehnerOkay 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.
Comment #4
Waldknoblauch CreditAttribution: Waldknoblauch commentedStill the same problem (Expose this filter to visitors) in beta3 version ...
Comment #5
dawehner@4
Can you provide some more context, a screenshot etc.
Comment #6
Waldknoblauch CreditAttribution: Waldknoblauch commentedComment #7
Waldknoblauch CreditAttribution: Waldknoblauch commented... the problem was the module http://drupal.org/project/entitycache. now it works!
Comment #8
bojanz CreditAttribution: bojanz commentedWhat does entitycache have to do with views sorts? That's odd
Comment #9
dawehnerAnyway, it's fixed now :)
Comment #10
pluca CreditAttribution: pluca commentedThe 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.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedI'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.
Comment #13
shawnxiong CreditAttribution: shawnxiong commentedI'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!
Comment #14
dawehnerPlease checkout the current dev version it's fixed there already.
Comment #16
Walter Johnson CreditAttribution: Walter Johnson commentedI have the current dev version and the flag doesn't save. The filter is never exposed.
Comment #17
spenoir CreditAttribution: spenoir commentedThis is still an issue in Drupal 7. Not sure what version of 7 I've got but it was downloaded recently
Comment #18
namdq CreditAttribution: namdq commentedTry to disable Devel module first then expose the filter, I got problem too and this solution works well.
Comment #19
spenoir CreditAttribution: spenoir commentedThanks namdq it does work well, actually it seems to speed up the admin too
Comment #20
jensen9090 CreditAttribution: jensen9090 commentedreason: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]
Comment #21
Vote_Sizing_Steve CreditAttribution: Vote_Sizing_Steve commentedI'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.
Comment #22
kupide CreditAttribution: kupide commentedI'm having the same problem
Comment #23
Liliplanet CreditAttribution: Liliplanet commentedsubscribe thx! 'expose this filter to visitors' does not save ..
Comment #24
dawehnerPlease disable the button_style module, it causes the problem.
Comment #25
sstacks CreditAttribution: sstacks commentedAs 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.
Comment #26
MeDAN CreditAttribution: MeDAN commentedAT Admin theme was also the problem in my project. Thanks pluca ;)
Comment #28
jrbeemanJust 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.
Comment #29
Charles wang CreditAttribution: Charles wang commentedI also ran into this problem as jrbeeman said, thanks to jrbeeman for your advice.
Comment #30
sunsetco CreditAttribution: sunsetco commentedLikewise 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".
Comment #31
dmegatool CreditAttribution: dmegatool commentedDisabling the Devel module worked for me. Was having the issue described but now it works.
Comment #32
hgneng CreditAttribution: hgneng commentedDisabling the Devel module worked for me (7.x-3.1) Thanks a lot!
Comment #33
garrettfisher CreditAttribution: garrettfisher commentedMe too. Disable Devel mod makes this problem go away.
Comment #34
eltioseba CreditAttribution: eltioseba commentedI was having the same problem. Disabling Theme Developer (not all Devel) solved the issue.
Comment #35
Anonymous (not verified) CreditAttribution: Anonymous commentedSame 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?
Comment #36
marcel.jtf CreditAttribution: marcel.jtf commentedThanks @jensen9090. The AJAX option did the trick for me.
Comment #37
Amir Simantov CreditAttribution: Amir Simantov commented#24 - this helped me! button_style module was the problem.
Comment #38
Dimm CreditAttribution: Dimm commentedProblem: Zircon Theme ( Base on Nucleus base theme)
Garland - Ok