-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
A common problem with the multi step forms is that the first page needs to be excluded from caching. This is caused by the fact that the page contains a unique id, the form state token, which identifies the state kept on the server side.
Subsequent steps can be cached since they carry the id as a request parameter and such requests aren't cached.
It is possible to make the first page cacheable by creating the server side state when the first page is submitted in contrast to when the first page is rendered as it is now.
- is causing
-
MGNLFORM-90 In multistep forms state is lost when going back and forward using the next step button
- Closed
- is cloned by
-
MGNLFORM-93 Forms should exclude themselves from being cached
- Closed
- is duplicated by
-
MGNLFORM-125 Don't require to disable cache unless it's a multi-step form
- Closed
- supersedes
-
MGNLSTK-764 Contact Form doesn't work in Magnolia 4.4.2
- Closed