Views: Access¶
Available since: 2.0.0
Provided tokens
| Token | Description |
|---|---|
[user] |
The current user. Alias: current_user |
[htmx] |
Information about the current HTMX request. |
[htmx:is_request] |
Whether the current request was sent by HTMX ("1" or "0"). |
[htmx:boosted] |
Whether the current request was boosted by HTMX ("1" or "0"). |
[htmx:history_restore] |
Whether the current request is for HTMX history restoration ("1" or "0"). |
[htmx:target] |
The value of the HX-Target request header. |
[htmx:trigger] |
The value of the HX-Trigger request header. |
[htmx:trigger_name] |
The value of the HX-Trigger-Name request header. |
[htmx:current_url] |
The value of the HX-Current-URL request header. |
[htmx:prompt] |
The value of the HX-Prompt request header. |
[event] |
The event. |
[event:args:?] |
The list of arguments given to the view. |
[event:display_id] |
The display_id of the view. |
[event] |
The event. |
[event:machine_name] |
The machine name of the ECA event. |
[session_user] |
The user account that dispatched the event, regardless if ECA is processing models under a different account. This is only available if ECA is configured to always run under a specific account. |
[account] |
The user account of the event. |
Fires during access checking for a View display. This only works when the View display's access plugin is set to ECA in the Views UI.
Access defaults to denied
If no ECA model grants access, the View will be inaccessible. You must explicitly set the access result using the Set access result action.
Performance
Views with ECA access are not cached (maxAge=0). This can have
significant performance implications on high-traffic sites.
Fields¶
View-
Select the view from the list.
Select the View this event should react to. Only enabled Views are listed.
Display-
Provide the view
display idto which to respond. Leave empty to respond on any display.The machine name of a specific display (e.g.,
page_1,block_1). Leave empty to react to all displays of the selected View.