[MAGNOLIA-7314] XML Exporting not working Created: 10/May/18  Updated: 31/May/18  Resolved: 31/May/18

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.6.6
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2018-05-10 at 16.21.08.png     PNG File no-way-out.png    
Issue Links:
causality
duplicate
duplicates MAGNOLIA-7310 XML Exports open directly in browser ... Closed
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:

 Description   

Since Magnolia 5.5.6 when exporting content in XML format, it's open in the same browser's tab whereas when YAML is selected, exported file downloads as expected. (See attached picture)

Steps to reproduce in Magnolia 5.6.6:

  1. Enter admin central and go to configuration app
  2. Select one of the nodes there an press export
  3. Select XML format and press export

In Magnolia 5.6.5 it works ok.

After export XML (where we're in XML view of browser) of JCR browser app:

  1. press back button of the browser
  2. we get back to JCR browser app view with dialog overlay and also locked by this screen (screen shot)
  3. refresh the page does not help, cancel button doesn't work, close button of the dialog also not responding. User must logout, switch to another app or close the app and open it again to get out of this stage

Expected result: just download the XML file as it is.

Tested in chrome and firefox.



 Comments   
Comment by Mercedes Iruela [ 31/May/18 ]

Duplicates MAGNOLIA-7310

Generated at Mon Feb 12 04:22:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.