Logical Operators for Widget Args

Feature Requests
1

Example use case:
A widget that shows all events from the Alumni group AND events from any other group with the Alumni tag.

If we add these args…

<arg id="group">Alumni</arg>
<arg id="tag">Alumni</arg>

Events will only be included if both conditions are met. That means that events in the Alumni group must be tagged “Alumni”, which seems unnecessary.

I think the official way to do this is to create a Stream widget, but that also seems unnecessarily complex.

I honestly have no idea if this is even feasible or how it could be implemented into the UI. Perhaps similar to the “If no results, substitute args” option. Just a spot to include additional args that would add results to the widget.

Anyway, I just wanted to throw this out there because it seems to come up frequently around here.

2

Hi Jon,

Does this setting help at all? Setting: tag_mode - LiveWhale Support? It sounds like maybe it would do the trick:

This setting allows you to change the default behavior for matching “all” tags (the logical AND) to “any” (the logical OR).

You could try that and see if that gets you the result you’re expecting. Hope that helps!
Rachael

3

No, that would not work in this case. That only works with tags. I am envisioning something similar but for different args, like events that “have tag A” OR “from group B”.

4

Here is a real world example:

Our Computer Science Department has a News widget on it. That widget mostly just shows stories from the News group that are tagged “computer science”. But occasionally Computer Science writes their own story in their own group, and it should be included in the widget too. So the widget is set to show stories from two groups. But since the widget already includes a tag arg, that means that stories that are in the CS group must also be tagged “computer science”.

That just kind of seems redundant to tag stories in the “computer science” group with “computer science”. It’s not hard, it just feels a little unnecessary.

5

Another possibility to mitigate this issue might be to have the option to set default tags for content in group settings. Like how you can set default event categories for specific groups. Or how you can set default tags on events from linked calendars.

Using the above example, I could then just set a default tag of “computer science” on all stories in the computer science group, and forget about it.