ECA lazy element¶
Available since: 1.1.0
Provided tokens
| Token | Description |
|---|---|
[argument] |
An optional argument for rendering the element. |
[name] |
The name that identifies the lazy element for the event. |
[event] |
The event. |
[event:argument] |
An optional argument for rendering the element. |
[event:name] |
The name that identifies the lazy element for the event. |
[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. |
Fires when a lazy ECA render element is being resolved. Lazy elements bypass page caching and are rendered separately (e.g., via BigPipe).
Personalized content
Use lazy elements for user-specific content (e.g., 'Welcome back, [username]', shopping cart count) that must not be cached with the rest of the page.
The [name] and [argument] tokens identify the specific lazy element.
Fields¶
Element name-
The name of the element, as it was specified in the configured action Render: lazy element. In any successor of this event, you have access to following tokens:
- [name]: Contains the name of the element.
- [argument]: Contains the optional argument for the element.
The element name that identifies this lazy element. Must match the name used in the 'Render: lazy element' action.