Feature: Multi Page Form Support (port to 3.x) #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
Note: This is a change that was merged into the develop branch (#259), but not carried over into the newer 3.x branch.
Changes how hasSubmission() is evaluated to allow multiple submit buttons to post the current form page (relevant in multi-step/page forms).
Why is it needed?
Multi step forms that span multiple pages are currently not possible and need a mechanism to persist data across pages.
Related issue(s)/PR(s)
There is a companion PR on the Formalicious repo (PR 18)
Example Form Template
To illustrate how this is set up, below is a template for a working form using the proposed feature. Note how the standard
submitVarproperty is still used as it always has been, while additional buttons for navigating backward or to a specific step are appended with_[postfix].