-
Improvement
-
Resolution: Fixed
-
Major
-
1.3.1
-
None
-
None
For 1.2.3 version MGNLFORM-82 was reverted so it's still an issue now.
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.
- caused by
-
MGNLFORM-92 Rollback MGNLFORM-82
- Closed
- clones
-
MGNLFORM-82 Forms should be able to render the first step without server side state
- Closed
- depends upon
-
MAGNOLIA-3699 Cache Header Negotiation
- Closed
- is duplicated by
-
MGNLFORM-125 Don't require to disable cache unless it's a multi-step form
- Closed