I am using Advanced Insert View to embed a view with arguments that are dates and terms. In the Add or select view UI, the date fields show with machine names (e.g. media.field_document_date) whereas the term entity reference field gets a human readable label.
Create a view that has contextual filters using a date field (e.g. "Date in the form of YYYY.") and term reference field. Note that when inserting the view via Advanced Insert View the date field has machine name whereas term reference field gets a human-readable label.
Ensure all core fields, including Date, get a human-readable label in Advanced Insert View UI.
Comments
Comment #2
jonathan_hunt commentedComment #3
a.dmitriiev commentedAs far as I remember the human readable label is added to the fields that are only in 1 bundle. The reason why this is like this is the following: the field instance exists per bundle and the label per bundle can be different. The filter in the view doesn't really know (and doesn't really care) for which bundle it is, so it has no information about the bundle the field belongs to. As there might be different labels per bundle, which one would you like to see in this case?
I guess in case the label is the same for each bundle the field is attached to, the label can be still show, this can be fixed. What are your suggestions for the case the field has different labels? show the bundle label in brackets? Or list them all? Not sure which one would be good UX
Comment #4
a.dmitriiev commentedThe fix is part of the MR for #3628746: Support arguments with multiple values
Comment #5
a.dmitriiev commentedFixed in the same MR as #3628746: Support arguments with multiple values