- Issue created by @tkasecker
-
jurgenhaas →
committed ce015aa8 on 3.0.x
Issue #3539222 by tkasecker, jurgenhaas: Event "Views Access" doesn't...
-
jurgenhaas →
committed ce015aa8 on 3.0.x
-
jurgenhaas →
committed 7ea32213 on 2.1.x
Issue #3539222 by tkasecker, jurgenhaas: Event "Views Access" doesn't...
-
jurgenhaas →
committed 7ea32213 on 2.1.x
- 🇩🇪Germany jurgenhaas Gottmadingen
Thank you @tkasecker for reporting this. As stated on Slack before, the "Set access result" action is the correct one. I've now fixed the access control as well, please give the dev release (either 2.1.x or 3.0.x) a try.
@jurgenhaas Thank you for your quick fix. I tested on dev release 2.1.x and the action now correctly sets the access result for the views access.
Since the Event "View access" is part of the submodule Views, but requires an action from the submodule Access so it can be properly used, maybe it makes sense to move the Event to the Access module? So everything that has to do with manipulating access can be found in one submodule. I think that would make more sense logically if you're looking for Events/Actions to manipulate access via ECA, but that's for you to decide.