- Issue created by @brian.barry@utexas.edu
- π©πͺGermany jurgenhaas Gottmadingen
The Views: Set filter value action works together with the Views: Pre Build event.
One use case, where we're using it, is a cron run that should send email notifications based on a view result. So, after the cron event, we execute a view with ECA and have that views pre-build event followed by the views set filter value action.
The only shortcoming is that the event can only subscribe to a specific view, but not to a specific display within that view. That's something we should probably add as an optional configuration to that and other events too.
- π©πͺGermany jurgenhaas Gottmadingen
As mentioned above, we've added the display ID as an optional argument to views related events, see π ECA Views: Events should allow to limit them by display ID Active
- πΊπΈUnited States brian.barry@utexas.edu
Thanks for your reply. It seems like what I'm trying to do is not possible (i.e., use "Views: Set filter value" within the process of form validation). I'll see if I can find a different approach.
- π©πͺGermany jurgenhaas Gottmadingen
I still think it's possible. When you use the action to query the view, Drupal will dispatch the event to prebuild that view. And that's where you can alter the filter value.
This is not sequential processing, it's so driven by events. That allows for different approaches.