By jurgenhaas on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
2.0.x
Introduced in version:
2.0.0
Issue links:
Description:
Token names can be derived from alphanumerical characters and can also contain underscores and hyphens. In ECA, most token names are only using alphabetic characters together with underscores. Very few token names contain hyphens instead.
In order to make token names easier to remember, ECA no longer uses hyphens in token names. Only underscores are used moving forward.
This affects the following token names, that have been changed:
[event:content-type]renamed to[event:content_type][event:entity-bundle]renamed to[event:entity_bundle][event:entity-id]renamed to[event:entity_id][event:entity-type]renamed to[event:entity_type][event:extra-field-name]renamed to[event:extra_field_name][event:field-name]renamed to[event:field_name][event:machine-name]renamed to[event:machine_name][event:parent-bundle]renamed to[event:parent_bundle][event:parent-id]renamed to[event:parent_id][event:parent-type]renamed to[event:parent_type][event:path-arguments]renamed to[event:path_arguments][event:route-parameters]renamed to[event:route_parameters][event:view-display]renamed to[event:view_display][event:view-id]renamed to[event:view_id][form:base-id]renamed to[form:base_id][form:num-errors]renamed to[form:num_errors]
An update hook is available which updates existing ECA models.
Developers should consider doing a similar change for existing tokens in ECA event plugins and, more importantly, only use underscores for token names introduced in the future.
Impacts:
Site builders, administrators, editors
Module developers
Site templates, recipes and distribution developers