[MGNLFORM-90] In multistep forms state is lost when going back and forward using the next step button Created: 16/May/11  Updated: 20/May/11  Resolved: 20/May/11

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.2.2
Fix Version/s: 1.2.3

Type: Bug Priority: Major
Reporter: Teresa Miyar Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLFORM-82 Forms should be able to render the fi... Closed
dependency
depends upon MGNLFORM-92 Rollback MGNLFORM-82 Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Comments   
Comment by Teresa Miyar [ 17/May/11 ]

The scenario was like this:

The server side state is in the session, identified by a formStateToken so the same user/session can have multiple forms active at the same time, in multiple tabs for instance. On the first step the token is in the page as a hidden input field on subsequent steps its a request parameters so they don't get cached. When the first step is added to the cache it will contain a token that was valid for the user that saw the page when it went into the cache. All users after that will get it from cache and try to use a token that is not valid for them

So, in the latest version 1.2.2 we changed it so that on the first step there's no formStateToken in the page at all, instead its created when the first step is submitted. It could be that this introduced a new bug.

Comment by Teresa Miyar [ 18/May/11 ]

There is another problem with this approach, when having one form to send to another form, second form thinks it has already been sent and if you have validations they are executed.

My scenario was:

had a form with a button, the acction of that form was a link to another form page. This new form had fields like name, address mandatory, first time i get to this new form i get error messages telling that mandatory fields are missing as if the form had been submitted.

Comment by Philipp Bärfuss [ 20/May/11 ]

Now after the revert of MGNLFORM-82 this issue doesn't exist anymore.

Generated at Mon Feb 12 05:36:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.