Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog
Details
Form-Specific Email Templates
TBD
Form Monitoring Service
TBD
CSRF Token Auto-Fetch
The new auto-fetch mechanism for CSRF tokens for AJAX requests are sent from throughout Freeform, which are then added as
X-Craft-Csrf
headers to the requests. This new approach works in all scenarios and for cached templates out of the box, so there is no more need to fetch and replace CSRF tokens by yourself for cached pages.Now the new CSRF auto-fetch mechanism only enables when Craft’s
asyncCsrfInputs
is set totrue
. When it is set tofalse
a basic standard hidden input is generated into forms, just like before. When it is set totrue
the input is never added, and the token is fetched automatically upon request. (There is an exception if the form does not have AJAX enabled. Then the input is still added to the form).There is a new setting that lets the user pick from two choices: