[PAGES-296] M6 Pages app does not offer to export to XML by default (needs config change) Created: 28/Apr/20 Updated: 01/Dec/20 Resolved: 01/Dec/20 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | Pages app |
| Affects Version/s: | 6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 5h | ||
| Time Spent: | 0.25h | ||
| 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 |
|
Note: It would be preferred that these bugs are solved: https://jira.magnolia-cms.com/browse/MAGNOLIA-7579
If they is solved, then the current ticket can be marked obsolete. But if it is too hard, this current ticket is a wecome improvement. In M6 Pages app, clicking "Export" action immediately downloads a YAML formatted bootstrap file. It should allow to choose XML or YAML as a format as in M5. This is important because some Magnolia features do not work with YAML bootstrap files yet.
|
| Comments |
| Comment by Christopher Zimmermann [ 28/Apr/20 ] |
|
It would be worth checking if this is true in other M6 style apps as well, including those created by content types. |
| Comment by Christopher Zimmermann [ 16/Jun/20 ] |
|
See: https://jira.magnolia-cms.com/browse/MAGNOLIA-7735
|
| Comment by Christopher Chard [ 01/Sep/20 ] |
|
Hi Topher, |
| Comment by Christopher Zimmermann [ 01/Sep/20 ] |
|
A question for you - if the two related tickets were solved - would you still need the XML export to be available in Pages app? |
| Comment by Christopher Zimmermann [ 01/Sep/20 ] |
|
cchard Also by the way - it is also possible to configure on a per project basis what export options are available. So this could be a workaround for you. There is some information here: https://documentation.magnolia-cms.com/display/DOCS62/Importing+and+exporting+JCR+data+for+bootstrapping |
| Comment by Christopher Chard [ 01/Sep/20 ] |
|
Thank you for your quick response, Topher! We really just need the export-function for ad hoc migration / xml-file-analysis / backup / copy-to-other-stage purposes. It works fine with the JCR-Tools, but not everyone has access to them nor understands them. However, for our Powerusers and Testmanagers it is a handy feature that they would regularly use. The yaml-Export is great for readability, but not suited for all purposes. In SUPPORT-11498, Viet pointed me towards the possibility of adding it via decoration. I just wanted to be sure that it's not an upcoming feature anyway. To my understanding, you guys otherwise have no pressure to re-integrate it ootb, right? Cheers |
| Comment by Christopher Zimmermann [ 02/Sep/20 ] |
|
cchard I'm not aware of any other input on it. I think the YAML format is generally more usable. The two linked bug tickets were my only remaining reasons for this ticket. Once those are fixed, yes the plan would be to only provide the YAML option - but let customers reconfigure the XML as Viet mentioned. I can appreciate that customers may have tooling or processes based on the XML exports. You mentioned "automigration", would anything prevent you from doing that with the YAML exports? |
| Comment by Simon Lutz [ 01/Oct/20 ] |
|
This will be closed as obsolete once |