Modules extending ECA¶
ECA submodules¶
Providing ECA functionality¶
- ECA Access: Events and actions to control access on entities and fields - plugins
- ECA Base: Base events, conditions and actions - plugins
- ECA Cache: Actions to read, write or invalidate cache items - plugins
- ECA Config: Config events - plugins
- ECA Content: Content entity events, conditions and actions - plugins
- ECA Form: Form API events, conditions and actions - plugins
- ECA Log: Events and actions for Drupal log messages - plugins
- ECA Migrate: Migrate events - plugins
- ECA Misc: Miscellaneous events and conditions from Drupal core and the kernel - plugins
- ECA Queue: Events, conditions and actions for queued operations. - plugins
- ECA User: User events, conditions and actions - plugins
- ECA Views: Execute and export Views query results within ECA - plugins
- ECA Workflow: Content entity workflow actions - plugins
Others¶
- ECA UI: Provide access to ECA in Drupal's admin ui
- ECA Development: Provides Drush commands and code generators for developers
Drupal contrib modules¶
- ECA Context - plugins
- ECA Entity Share
- ECA Parameters - plugins
- ECA State Machine - plugins
- ECA Tamper - plugins
- ECA VBO - plugins
- ECA Webform - plugins
- Group Actions - plugins
Hopefully in development¶
- Address
- Drupal Audit Notification Subscription Event
- Drupal Remote Dashboard
- Entity
- External Authentication
- ImageMagick
- Feeds
- Flag
- LDAP
- SimpleNews
- Sophron
Known issues¶
Variety of workflow modules¶
There are currently 3 modules providing workflows, states and transitions:
- Workflows: provided by Drupal core
- Workflow: contrib module
- State machine
It's important to know, that all three provide very similar functionality, but have absolutely nothing to do with each other. This may be confusing, e.g. when reporting issues about ECA modelling around workflow, as long as it is not expressed explicitly, which workflow "system" is being used.
Even more confusion has been seen in action, when not only one but 2 or even all 3 of those modules are enabled. It's important to then pay extra attention to the mix of events, conditions and actions, so that the correct ones get combined in a model, otherwise strange results or even errors will be created.