[MGNLUI-6204] JCR-browser export fails for dam-node, should allow options Created: 10/Sep/20 Updated: 01/Oct/20 Resolved: 01/Oct/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| 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
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Migrate apps to new UI framework | ||||||||||||||||
| Description |
Issue: Fails to export dam node with exceptionThe new JCR-browser app throws an excpetion, when a user tries to export a node from the dam workspace. (stack-trace) Since this worked on 6.2.2 with the "old" browser, the new browser also should support it. Note that dam nodes must be exported as XML! Missing option: export format always YAMLOn the old JCR-browser, when exporting a node without a binary, the user can decide whether he wants YAML or XML. |
| Comments |
| Comment by Roman Kovařík [ 01/Oct/20 ] |
|
This is a valid ticket for JCR browser app), this app either
|
| Comment by Simon Lutz [ 01/Oct/20 ] |
|
Closed as duplicate of |