-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with formie and blitz #2020
Comments
This is a little tricky with Blitz, as if you have server rewrites setup, it's never going to even hit Craft/Formie to run this Twig code. I'm not sure if you have that enabled yet. Otherwise, this is going to behave as I'd expect with a static cache. If the entire page is cached, this Twig code isn't going to run every time. But as for the session data, that's not going to be cached, being a POST request, so it's likely to get out of sync. As you mentioned, with this issue we're going to need to come up with an all-encompassing way to handle statically-cached sites, including changing session-handling behaviour. |
Thanks for your feedback |
Describe the bug
Hi
We have found an issue with formie and blitz
I added the following code to my project to prevent blitz from caching user data:
{% do craft.formie.setCurrentSubmission(form, null) %}
If the user reloads the page to start over without completing his first submission and clicks on next, he ends up on the next page from his old submission.
(Check steps to reproduce)
Can you add this to #2001
Best regards
Steps to reproduce
{% do craft.formie.setCurrentSubmission(form, null) %}
Form settings
Craft CMS version
4.11.1
Plugin version
2.1.24
Multi-site?
No
Additional context
Blitz: 4.22.0
The text was updated successfully, but these errors were encountered: