[MGNLUI-6248] No Replacement for OpenCreateDialogAction Created: 25/Sep/20 Updated: 25/Sep/20 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | 6.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Jennings | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Description |
|
There is no usable way to create and populate a new node within a content app. In v5 we offered the action "OpenCreateDialogAction" which opened a dialog which, when saved, would create a new node and populate it. This can still be seen in Magnolia 6 in the Security app. When creating a new user, the dialog is opened and no node is created until clicking submitting the form. Similar behaviour can be created with a chained action but this creates an untitled node and then opens the dialog. Dismissing the dialog leaves behind an unpopulated, untitled node. The CreatePageAction class from magnolia-pages-app solves this problem with hardcoded references to nodetype and the use of the registries to find the dialog. |