[MGNLUI-6509] Item added via detail SubApp is not selected in browser after saving Created: 14/Jan/21 Updated: 12/Mar/21 Resolved: 30/Jan/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2 |
| Fix Version/s: | 6.2.7 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Šimon Demočko | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.35d | ||
| Original Estimate: | Not Specified | ||
| 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
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | UI framework implementation | ||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | UI FW 20 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
Steps to reproduce
Expected resultsThe created item is selected in the browser view. Actual resultsThe folder in which the item was added stays selected (or the invisible root if the item is in the root directly). Development notesOne way to solve this would be to access the UI component hierarchy by solving |
| Comments |
| Comment by Roman Kovařík [ 22/Jan/21 ] |
|
For documentation: No need to define default actions for detail subApps:
subApps:
detail:
# actions:
# commit:
# $type: commitAction
# cancel:
# $type: closeAction
form:
properties: !override
- name: jcrName
Moreover the default commit action is now equals to following configuration:
commit:
class: info.magnolia.ui.contentapp.detail.action.SaveDetailSubAppActionDefinition
browserName: browser
This action saves, closes the detail subapp and selects the edited item in browser (useful when creating new items). The default browser name is "browser". |
| Comment by Roman Kovařík [ 04/Mar/21 ] |
|
Hi, seems to be the case on the previous version as well https://demo.magnolia-cms.com/.magnolia/admincentral#app:dam:jcrBrowser;/stories-demo/found-in-switzerland/ Plus the new asset is not selected (which should be fixed by this ticket). Can you confirm? |
| Comment by Roman Kovařík [ 05/Mar/21 ] |
|
This ticket is really only about selecting, the only scrolling ticket was |
| Comment by Simon Lutz [ 05/Mar/21 ] |
|
I have created |