Skip Navigation

[Resuelto] Custom field filters default to AND – no option to set OR

This support ticket is created hace 1 año, 4 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 3 respuestas, has 2 mensajes.

Last updated by Simon hace 1 año, 4 meses.

Assigned support staff: Shane.

Screenshot 2021-09-29 17.33.40.png
Screenshot 2021-09-29 17.33.38.png

I am trying to: add a View with custom field filters saying that one of two conditions must be true in order for the post to be included

I expected to see:
- A dropdown below the custom field filters where I can choose AND / OR

Instead, I got:
- No dropdown! Where's it gone?

UPDATE: I installed Views 3.2.1 and the Dropdown reappeared. I set my View to use OR logic. I then updated Views to the latest version and it disappeared again, although the query is still set to OR.


UPDATE: I deactivated Blocks and installed an older version of Views (3.2.1). The dropdown then appeared. I set it to OR.

I updated Views to the latest version and it disappeared again (although my View still works!). So the question is, have you deliberately removed this or is it a bug?



Languages: Inglés (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Simon,

Thank you for getting in touch.

This is an issue that is still open and we are actually aware. Hopefully this one gets fixed soon.

For now your workaround should work.

Secondly the only other workaround is to specify the filter relationship using the views query filter as depicted in our errata page below.



The errata is actually wrong - it says the OR param is ignored, in reality that choice has disappeared!

I actually think my workaround of switching back to an older version of Views is better. This seems like a pretty big bug so hoping it gets fixed in next release.