As seen on this production site (http://frimaerkehandleren.dk), I have a number of different exposed filters which the user can play with. This is AFTER I've changed back from 7.x-3-12
'Cause installing 7.x-3-12 caused it to look like this:
The Leave blank for all. Otherwise, the first selected term will be the default instead of "Any". is displayed under the Dropdown with Terms.
In the backend the View looks like this:
Again we see the Leave blank for all. Otherwise, the first selected term will be the default instead of "Any". under the list of terms.
I don't see any ways to turn this text off and I shouldn't have to, the way I see it. The text is refering to backend configuration, so it appears to me that it's a bug.
If there's an easy way to remove the text, that I've overlooked please let me know.
Comment | File | Size | Author |
---|---|---|---|
#5 | viewsissue4.png | 29.04 KB | William H. Olesen |
#4 | viewsissue3.png | 84.94 KB | William H. Olesen |
#2 | viewsissue2png.png | 136.58 KB | William H. Olesen |
#2 | viewsissue1.png | 275.27 KB | William H. Olesen |
Comments
Comment #2
William H. Olesen CreditAttribution: William H. Olesen as a volunteer commentedComment #3
William H. Olesen CreditAttribution: William H. Olesen as a volunteer commentedComment #4
William H. Olesen CreditAttribution: William H. Olesen as a volunteer commentedComment #5
William H. Olesen CreditAttribution: William H. Olesen as a volunteer commentedIt might be important to note, that this behaviour does not occure below drowndowns using Grouped filters containing date-filtering like at another of my sites here:
Comment #6
tdurocher CreditAttribution: tdurocher commentedYes, for me too. Besides being confusing, messed up formatting for my inline filters.
Comment #7
tdurocher CreditAttribution: tdurocher commentedI now see this is a duplicate of https://www.drupal.org/node/339384. My workaround is to add the following css:
.view-my-view .views-exposed-widgets .description {
display:none;
}
Note that this may hide descriptions that you DO which to display so may not work for everybody. Could probably get a more specific selector in that case.
Comment #8
pandroid CreditAttribution: pandroid commented+1
Issue for us too.
Comment #9
donaldp CreditAttribution: donaldp as a volunteer commentedI see this as well, but also note that 3.12 is officially broken and I've reverted to 3.11. I've not tried 3.13 yet to see if this issue persists...
Comment #10
William H. Olesen CreditAttribution: William H. Olesen as a volunteer commentedThe issue persists with 3.13 - at it again :(
EDIT: When reverting to 7.x-3.11 I find that the mentioned backend helptext (Leave blank for all. Otherwise, the first selected term will be the default instead of "Any".) which appears in the frontend, does not appear in the backend in 7.x-3.11 as it does in the later versions.
So from 3.12 a helptext was inserted for the backend which also appears in the front end - at least for me and a few others.
As stated in #7 one can of course CSS ones way out of it, but making it disappear all together seems like the best long term solution to me.
Comment #11
nerida CreditAttribution: nerida commentedIssue for me too
Comment #12
dhalbert CreditAttribution: dhalbert as a volunteer commentedClosing as a duplicate of #339384: Default option <Any> not set in exposed filters when terms are selected. But I'll mention one way to get rid of this for now is to use String Overrides to replace the text with nothing.
Comment #13
capogeannis CreditAttribution: capogeannis as a volunteer commented+1... using CSS band-aid to hide it. No bueno.
Comment #14
Niek_Kloots CreditAttribution: Niek_Kloots commentedI solved it by removing line 198
#description' => t('Leave blank for all. Otherwise, the first selected term will be the default instead of "Any".'),
from modules/views/modules/taxonomy/views_handler_filter_term_node_tid.inc
Comment #15
sustainablesolutionsnz CreditAttribution: sustainablesolutionsnz commentedThanks Niek_Kloots
Comment #16
Schroeffu CreditAttribution: Schroeffu commentedSame happen to me.
Will try #14
Comment #17
stephesk8s CreditAttribution: stephesk8s commentedThis still exists in 3.13. Removing the line worked for me. Thank you @Niek_Kloots. Hopefully this will be fixed in 3.14 so I don't have to try to remember to remove it again.
Comment #18
jrz CreditAttribution: jrz commented#14 works for me
Comment #19
ron_s CreditAttribution: ron_s commentedThere's no need to hack the module, use String Overrides, or write a hook function.
A patch has already been committed to the -dev branch and is available here:
https://www.drupal.org/node/339384#comment-10587426
Comment #20
tyners CreditAttribution: tyners commented#14 works for me. Thanks, Niek_Kloots!
Comment #21
Cisse CreditAttribution: Cisse commentedI'm using the String Override module to replace Leave blank for all. Otherwise, the first selected term will be the default instead of "Any". to blank. Easy and fast. Also handy to replace other original strings in Drupal.
Comment #22
Happy Scientist CreditAttribution: Happy Scientist as a volunteer commentedThanks Niek_Kloots! You solved my problem.
Comment #23
alanom CreditAttribution: alanom commentedThis appears to be fixed in the latest Views 7.x-3.x-dev release but still not in any Views stable release.
Comment #24
ron_s CreditAttribution: ron_s commented@alanom, just apply the patch I linked to in #19.
Comment #25
creact CreditAttribution: creact commented#14 worked for me too. Thanks a million.
Comment #26
jmart CreditAttribution: jmart commentedI use Views in a multisite environment. I'm not going to install String Override on all the sites. So I hacked Views. Thanks #14.
Comment #27
jaesperanza CreditAttribution: jaesperanza commentedI fixed this by "hiding" the helptext message from being displayed using CSS.
.description {
display: none;}
I am not sure though if this poses any security risk. I think this is better than hacking Views or at least until patch is included to the current version.