[MGNLDATA-144] Validation does not work for subtype dialogs Created: 01/Feb/12 Updated: 18/Feb/16 Resolved: 18/Feb/16 |
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Tobias Mattsson | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
Validation of a subtype dialog uses configuration for the top-level dialog. Steps to reproduce: When you open the dialog for creating a subtype it renders correctly, dont fill in a name, when saving it will require you to enter one because required=true in the parent. Also, when the dialog reloads, it now displays the parent dialog instead, this already filed as |
| Comments |
| Comment by Michael Mühlebach [ 18/Feb/16 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |