Busy with a new project where I want to allow the user to make a selection of my content using dropdown fields.

Created a new content type with fields.
I configured the fields on which I want the visitor to narrow down the list of content as list (text) and list (integer) depending on the content (text or figures).
I did not indicate a default value per field.

In Views I create a new view/page with a bunch of filters.
I select "expose filter" --> Single filter --> "is one of" --> "select all" (see screenshot)
I doe this for every field on which I want the visitor to make a selection on

As I don't want to see the APPLY button I select "auto-apply" in the exposed form setting (Advanced)

when I save and test the view I get the above error message (for each filter) and no overview of any of the published pages.
If now I make a selection on at least 1 field, I get a an oveview of all the content meeting my filter selection (as I expect it to be).
If I reset all filters to "Any" I get the complete list of pages for the configured content type - this is what I expect - but without the error message.

This prooves that my view is working, but only upon refresh and never upon initial (re)load.

Anyone haveing an idea what I do wrong ?
Don't count too much on the correctness of the content ... is is n initial test and I've copied/pasted the info from a site but not necessarily in the corroct order ;)

Thanks for helping me out here ...
Herman

CommentFileSizeAuthor
expected result.png99.82 KBheleba-1
views_config.png101.52 KBheleba-1
fields.png74.69 KBheleba-1
errocode.png48.71 KBheleba-1
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

adelka’s picture

subscribe

dawehner’s picture

Maybe another issue related with hybrid filters :(

odegard’s picture

Might not be related, but I bumped into this exact error when I had two exposed forms on the same page. Changing filters in one form triggered errors in the other form. The solution for me was to remove the forms so they were never on the same page. Cumbersome, but it works (for me!).

rogical’s picture

Same issue with address field

Georgique’s picture

Georgique’s picture

Post author should just unselect all of the options (even "Select all") - this solved problem for me. But I still think it is Views bug.

BarwonHack’s picture

I experienced this issue with Terms exposed as IDs but not with Terms as Name.

BarwonHack’s picture

Further info: Had better success with multiple taxonomy terms as exposed filters with Taxonomy view as opposed to Content view. No errors and much better performance. Content fields available after necessary relationships added.

neha.gangwar’s picture

Assigned: Unassigned » neha.gangwar
Status: Active » Closed (fixed)

In views filtration instead of select "select all". If you can select rest all the options than it works. because how can it filter results on the basis of select all options.

donquixote’s picture

MustangGB’s picture

Status: Active » Closed (outdated)

Closing this as outdated to tidy up a bit around here. If you're still having problems with the latest release please create a new issue.