Trying to filter content by two field values (either/or)

Question

I'm trying to filter published content by the values set inside of two fields (one or the other). Right now, I'm successfully filtering my content by one field:

Contextual Filter

If field_targetuser = logged in uid, than display content.

However, I also want to show content in which field_universal = YES , regardless of the logged in uid.

Naturally, implementing the first Contextual Filter and than a second only further filters the intial filter. What I'm trying to accomplish:

Show all content of this type if targetuser matches logged in user id, but ALSO show all content where field_universal = YES, regardless of what appears in the targetuser id.

Views setup:

Answer 1

It appears that you are trying to do and OR filter in contextual filters, and as @jreynolds mentions, OR conditional are not available in contextual filters out of the box. @jreynolds' solution is to move the arguments into the filters, which is a solution I like very much, but I also hesitate to use a sandbox module if I can avoid it. Instead I'm using Views Contextual Filters OR. Which has a dev version available. With this module installed you need to go into the query settings in the advanced section of your view and check a box next to "Contextual filters OR". The disadvantage of this, of course, is that you can't do more advanced logic like and'ing two filters and or'ing a third.

Another solution is to access the views api in a custom module and change the contextual filter query to be an OR query as explained in This answer.

UPDATE I think you should be able to accomplish this by putting both of your filters in contextual filters and using the module I recommended above. You currently search for your user field matching the currently logged in user in contextual filters. Now add a second contextual filter that matches for field_universal and provides a fixed default value of yes or whatever it is that needs to match in that field. That in combination with the Views Contextual Filters OR module should query for the message is meant for the current user OR the message is a universal one.

Answer 2

You can solve this without any additional modules or coding, just with pure Views + Entity Reference. Here is how:

1. You need to add 1 more relationship to your current View (looking at your screenshot):
   • Entity Reference: Targeted User => This is the Entity Reference field that points to a User, what you call "targetuser"
2. You need to add a "User: Current" filter to your view. Once you click on that, you should see the following: This filter will allow you to select only the nodes where the targeteduser is the same as the logged-in (current) user.
3. You need to place the universalswap in an OR relationship to the new filter inside a FILTER GROUP. Then place that group in an AND relationship to the rest of your filters, i.e. Type = Messages.

That should do it without any additional modules. Here is a screenshot of my final View configuration: I am logged in as admin (uid:1) and you can see in the results that I am getting all messages that are either "Universal" or targeted at me.

Good luck!

Answer 3

The most straightforward way to do this in my view would be to add field_targetuser and field_universal to your fields and exclude them from display then create a views Global: PHP filter with the following filter code in

global $user;

if($user->uid == $data->field_targetuser || $data->field_universal == "yes")          
{
    return false;
} else {
    return true;
}

The code here basically checks to see if the current uid matches the targetuser field or the field_universal equals yes. If either of these conditions are met the filter returns false which displays the result, otherwise return true which excludes the result.

Hope this is what you were looking for :-)

Answer 4

What you need is a way to move the contextual filters down into the normal filter section of Views where you can apply conditional logic on them (in your case an OR condition)

There is a module for that: Views arguments in filters

There are at least two problems with arguments as they are currently used in Views:

• Many people find it difficult to wrap their head around how arguments work.
• It is not possible to use operators on arguments, for example to show all nodes created after the timestamp value you provide in an argument, or display all the nodes that in their title contain the word/phrase in the argument. There is just "equals" or "not equals". (Unless you more or less code your own argument handlers, which would end up a special case that few others can make use of.)

Answer 5

It appears as though the below view settings fixed the issue. This setup displays Messages for the current user, OR messages in which field_universalswap = Yes...

Because the field_targetuser is always the logged in user, it displays current user's messages. If the field_targetuser does not match the current user, it still displays those messages if field_universalswap = Yes.

My only tick about this route: It also displays messages I've sent - not sure that's a bad thing yet though...