- Issue created by @gge
- 🇩🇪Germany jurgenhaas Gottmadingen
Webforms are not using Drupal's form API, that's why the form events in eca_form are never dispatched when working with a webform.
The eca_webform modules comes with some webform specific event. Maybe the Alter submission form event is working in this scenario? You should then also add some message actions into your model so that you can test if the event is being dispatched and also after the action plugin to see if that action got executed successfully as well.
- 🇷🇴Romania gge
Webforms are not using Drupal's form API, that's why the form events in eca_form are never dispatched when working with a webform.
My initial thought was the same but ECA 2 works very well with webforms, just like with entity forms. All form events (build, processing, afterbuild), conditions, actions (defaut values, access to fields, requiring fields etc.), tokens, rendering views, adding ajax handlers to fields and manipulate them, changing submit button label, etc... It can even manipulate address → fields inside webforms.
It's a wonderful and unexpected combination for those who want/need to use something else instead of nodes.The only thing (untill now) that doesn't work for me is to manipulate the default value of Date field type. A workaround could be the Date/Time field that come with webform. ECA manipulate this type of field very well so I decided to use it instead of date (and hide the time input).
Thank you very much for this integration!