Validate content entity

Available since: 2.1.0

When an entity is undergoing validation.

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: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.
[entity]	The entity of the event.
[ENTITY_TYPE]	The entity of the event under the name of its entity type.

Fires when a content entity undergoes validation (e.g., during form submission or REST API operations). Allows adding custom validation rules without writing PHP code.

Use conditions and the appropriate validation actions to add violation messages that will prevent the entity from being saved.

Fields

Type (and bundle)

This field provides a list with all created content entities and its bundles. You can also select -any-, if you want to react to all types or bundles.