I am having issue showing contextual filter on the editor page. Steps followed
1) I created a view with contextual filter
2) Enabled - Exposed Filters - editor view ( under extra settings )
3) Tried creating content by Exposed Filters - editor view is not showing up.
Am I missing something
UPDATE:
Fix is here: Trigger ajax refresh when display ID is changed
Comments
Comment #2
azinck commentedI am having the same problem. I believe it's because, when you're selecting a view, the display ID is typically not already selected, so the ajax call that ends up calling ViewsReferenceExposedFilters::alterFormField() doesn't provide a display ID, so it's unable to load the view and provide the filters. I'd have expected the selection of a display would have resulted in another ajax call to provide the necessary data, but such a call never happens. That's despite the comment on #2957177: Pass view name and display id to alterFormField() method in ViewsReferenceSetting plugin that claims "It also adds ajax refresh to the options field triggered by a change on the display_id field".
I'm testing with Views Reference Field 2.0-beta2 and Views Reference Field Filter 1.0.0-alpha1.
Comment #3
azinck commentedBtw, one workaround is to set a default value on the field where you select the view and the display. If you can live with that, then the filters do get added correctly because both bits of data are available when the widget is rendered.
Comment #4
azinck commentedI've posted a patch to fix this problem on #3166490: Trigger ajax refresh when display ID is changed.
Comment #5
roborew commentedAs this issue is fixed by Trigger ajax refresh when display ID is changed , I'll close this issue for now. I've bumped the other queue so hopefully the maintainer will get it in soon. Suggest to patch the viewsreference modules with this patch for now: viewsreference-ajax_after_display_selection-3166490-6.patch