Josh Crawford

This will also tie into [form groups](https://github.com/verbb/formie/issues/662)

I'll consider this, but the server-side check will always probably need to be there, as for multi-page forms where the matching field is on another page, it's unreliable to rely...

Going to shelve this for when we tackle https://github.com/verbb/formie/issues/556

Not at the moment, sorry! I might suggest creating a Synced field so that all your email fields are linked, and the settings remain the same across multiple instances of...

Interesting idea, I like it! It makes sense to be able to conditionally opt-in or out of integrations, of which there's only very, very simply support with the Opt-In setting....

Added for the next release. To get this early, change your `verbb/formie` requirement in `composer.json` to: ``` "require": { "verbb/formie": "dev-craft-4 as 2.0.13", "...": "..." } ``` Then run `composer...

Added in [2.0.14](https://github.com/verbb/formie/releases/tag/2.0.14)

Similar to https://github.com/verbb/formie/issues/108

Formie will be submitting a POST request to the action endpoint `formie/submissions/submit` (see https://github.com/verbb/formie/blob/9aa5c262f547d3ad2b76000408e7e9be854bdda9/src/templates/_special/form-template/form.html#L45 and https://github.com/verbb/formie/blob/9aa5c262f547d3ad2b76000408e7e9be854bdda9/src/elements/Form.php#L1071) Craft will translate that endpoint to `https://your-site.com/actions/formie/submissions/submit`. I'm not exactly an expert with Netlify,...

You shouldn't have to do anything. The `actionInput()` we use in templates will generate an action URL endpoint resolving to the Craft backend. Whether that's on a seperate domain (in...