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.I don't see any other open issues for this, but I'm sure it's been discussed before so feel free to mark this as duplicate if I'm in the wrong place. :)
I think "Contextual filters" is the wrong language to use for arguments. I agree it needs to be changed, but "context" means so many things elsewhere in Drupal that I don't think adding it into views *also* is the right thing to do.
What do people think about "Dynamic filters"?
I'd like to get some consensus on this language (maybe we're already there - and if so I'll have to accept that) before we start updating the panels UI to use the new name for arguments.
Comments
Comment #1
jenlamptonsee #1213080: terminology update: replace all instances of "Argument" with "Dynamic filter" in panels UI for terminology update in panels.
Comment #2
dawehnerDynamic filters seems to be perhaps somehow more related to "exposed filters" as they change as well.
Comment #3
jenlamptonI think that's a good thing. These things all have the same affect, but Filters and Exposed filters have to be defined before they filter, but arguments (or dynamic filters, or contextual filters) are variables and don't need to be defined at all. I don't really like the name "Variable filters" but that would work too, I suppose.
Comment #4
joachim CreditAttribution: joachim commentedI presume 8.x-3.x means 'views in core'?
See also #1668024: Provide a unified user interface for static filters, exposed filters, contextual filters (arguments) and facets -- I'd like to remove the concept of filtering from arguments entirely :)
Comment #5
tim.plunkettComment #6
xjmComment #7
yoroy CreditAttribution: yoroy commentedI've always found both 'arguments' and 'contextual filters' very frustrating because no matter how much UI, labeling and descriptioning are added, it comes down to something with %1 and %2 and it's just not made clear where those come from, what they represent and how they are used. I still don't get arguments, nor contextual filters :)
Comment #8
tim.plunkettI think at this point we'd have a mutiny if we revert back to arguments after making everyone relearn it in D7.
I'd like to close this soon, but leaving open for more discussion.
Comment #9
xjmRelated: #1668024: Provide a unified user interface for static filters, exposed filters, contextual filters (arguments) and facets
Comment #10
Bojhan CreditAttribution: Bojhan commentedDynamic filters does sound interesting, it was renamed but was it ever tested?
Comment #11
dawehnerWell, this has been backed up by the people which designed the UX, but i'm not sure whether this was tested directly.
Comment #12
xjmI think that "dynamic" filters is too easily confused with exposed filters. Contextual filters aren't exactly dynamic; in fact, on a given page load, they're static. They're taken from the context--a node, a term, a URL argument, a block. If some of the context stuff from WSCCI/SCOTCH is exposed to the user, then our terminology will be consistent with that.
Comment #13
joachim CreditAttribution: joachim commentedIf #1668024: Provide a unified user interface for static filters, exposed filters, contextual filters (arguments) and facets happens, then this issue probably goes away -- or is radically changed.
Things that come in from the URL argument should be called arguments, things that come from context should be called context. And they all can feed into filters.
Comment #14
tim.plunkettPostponing on #1668024: Provide a unified user interface for static filters, exposed filters, contextual filters (arguments) and facets, but this might just be obsolete.
Comment #15
Anonymous (not verified) CreditAttribution: Anonymous commentedIf I remember correctly the word "arguments" was used in D5/D6 version. I'm not sure though since I'm not using views for many years now.