[MGNLFORM-82] Forms should be able to render the first step without server side state Created: 13/Apr/11 Updated: 03/Apr/12 Resolved: 14/Apr/11 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.2 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Tobias Mattsson | Assignee: | Tobias Mattsson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Ondrej Chytil [ 14/Apr/11 ] |
|
Reopening for rollback changes done to empty webapp pom. Unwanted commit? |
| Comment by Tobias Mattsson [ 14/Apr/11 ] |
|
Yes, unintended. |
| Comment by Felix Rabe [ 09/Jun/11 ] |
|
The fix to this issue was reverted because it caused |