Josh Crawford

I'm pretty sure we made that change some time ago with the default stencil, as the stencil sets this to the [`replyTo`](https://github.com/verbb/formie/blob/2d961324d861f124c3e8c48db812552904d68428/src/migrations/stencils/contact-form.json#L22) property. Maybe this is an older install that...

You can manually edit the YAML file in your starter project to either `from: null` or `from: ''` if it's not attached to a Craft install that you can go...

> I then attempted to encapsulate the dynamic query within an arrow function to delay its execution: That'll be the preferred approach I believe, but we do need handling on...

> the closure itself was being stored instead of executed Where did you see this, in project config? On my end, it seems to be storing the array correctly, not...

Testing in that fashion won't really work, as that's correct you'll just be printing out the literal closure. But yes, that's indeed a great point. While this will always be...

FYI, just pushed a fix for that content stored in project config. As I said, calling the value in `comments.php` is going to just produce the Closure, but that's why...

Should be a release scheduled at the end of the week.

Updated in [2.0.17](https://github.com/verbb/comments/releases/tag/2.0.17)

Yeah, with server rewrites, I don't see how this is possible, as the request never even hits Craft for Knock Knock to handle things. It's essentially serving up a literal...

You'd have to go through an set all submission's content to be `true` for that agree field. Something like: ``` ./craft resave/formie-submissions --set myCustomField --to true ```