- Issue created by @pfrilling
- πΊπΈUnited States pfrilling Minster, OH
I added the config action that will add a captcha form element to a form if it does not yet exist.
- πΊπΈUnited States jrockowitz Brooklyn, NY
Maybe we need to evolve webform related config actions in a dedicated webform_config_action contrib module so that it evolves faster than the Webform module.
If the webform_config_action.module gets stable, and development slows down; we could merge it into the webform module.
- πΊπΈUnited States jrockowitz Brooklyn, NY
I am better understand the importance of the ticket via β¨ Add Config Action to enable captcha form elements Active .
We are going to have to step back and think about what config actions are required for webforms.
For example, we probably need a way to add any element to a webform and we can expose \Drupal\webform\Entity\Webform::setElementProperties as a config action method.
Attached is POC (untested) patch that might be a simpler approach for a Drupal CMS MVP.
Because config actions are required via Drupal CMS, I am going to mark this a Critical.
- π¦πΊAustralia pameeela
Sorry y'all, I missed the latest update on this one. I'd love to have this be an optional thing, but I don't think it's critical for our release, when weighed up against everything else (and, the form to capture inputs isn't actually working yet). I updated the other issue but I'd be fine with the form having the captcha element by default when it's added, as the consensus among folks seemed to be it was better to have it than not.
I really appreciate the urgency! But would love for everyone to have time and space to figure out config actions for webform, as @jrockowitz already raised. Later on, we can make it super slick as an optional add-on :)
- πΊπΈUnited States thejimbirch Cape Cod, Massachusetts
Adding Recipes initiative tag so we can track and document any config actions created here.