[MGNLFORM-257] Multistep with condition list shows all following pages in "breadcrumb" regardless of successor page Created: 19/Feb/15 Updated: 11/Nov/16 Resolved: 08/Dec/15 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | 2.2.10 |
| Fix Version/s: | 2.3.3 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Natascha Desmarais | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.75d | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Sprint: | Kromeriz 22 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Description |
|
Trying to emulate a form where your second choice is divided into 3 possible sub steps, but they all come back together to the same summary page before submission. The pages themselves are stored in a flat hierarchy. Screenshots and sample data attached. The sub steps before the summary page show the other sub steps as well even though they will not be reached and are set to "hidden in the navigation". However, the summary page then shows the correct state of the substeps. This leads to an inconsistent state of the "breadcrumb". Related to this, if you go back and make a different choice, it will be displayed in the final summary page as sub step as well (already reported in Unfortunately it is also not possible to circumvent this by hiding this information without having to provide an own template script for that component/area. |
| Comments |
| Comment by Natascha Desmarais [ 19/Feb/15 ] |
|
Attaching also an export of this example so this can be easily verified/tested. |
| Comment by Roman Kovařík [ 02/Dec/15 ] |
|
Solution:
|
| Comment by Evzen Fochr [ 10/Dec/15 ] |
|
please add form 2.3.3-SNAPSHOT to ce/pom.xml |