[MAGNOLIA-7336] Content-Disposition missing "attachment" when exporting JCR content Created: 14/Jun/18  Updated: 15/Jun/18  Resolved: 15/Jun/18

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

Type: Bug Priority: Major
Reporter: Will Scheidegger Assignee: Unassigned
Resolution: Duplicate Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tested on

  • Safari (Mac)
  • Chrome (Mac + Linux)
  • Firefox (Mac)

Attachments: PNG File Screen Shot 2018-06-14 at 10.17.01.png     PNG File Screen Shot 2018-06-14 at 10.17.59.png    
Issue Links:
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   

When exporting content as XML from Magnolia (JCR export) the content used to be downloaded into an XML file. Since Magnolia 5.6.? however, the browser is displaying the XML which is unexpected in its best case.

The problem originates in a missing "attachment" parameter in the Content-Disposition header.

Magnolia 5.4.6:

Magnolia 5.6.5:

As you can see, in Magnolia 5.6.5, the "attachment" parameter in the Content-Disposition header is missing.

Steps to reproduce

  • Go to https://demoauthor.magnolia-cms.com
  • Open the pages app
  • Select a page
  • Choose "Export"
  • Select "XML" as format
  • => expected result: page is downloaded as XML file
  • => experienced result: page is displayed in the browser


 Comments   
Comment by Will Scheidegger [ 14/Jun/18 ]

I would go as far as even calling this a blocker, as it not only makes exporting larger amounts of data virtually impossible, if you should succeed and the browser displays the xml, you then save it and return to Magnolia using the back button, you'll end up with the screen with the export dialog still displaying... but unresponsive. The whole pages app is unresponsive. The only way to close the export dialog is to log out and log back in!

Comment by Mercedes Iruela [ 15/Jun/18 ]

Hi Will,

thanks for reporting issues in Magnolia. I am closing this issue as duplicate because it was already reported in Magnolia (MAGNOLIA-7310 ). As you can read in our documentation, it is affecting Magnolia 5.6.6. and will be fixed in the next release: XML exports open directly in the browser instead of offering a download.

Our apologies for the inconveniences.

Regards,

Mercedes

Comment by Will Scheidegger [ 15/Jun/18 ]

Thanks for the feedback and sorry for creating a duplicate issue. I searched for content-disposition but did not get any hits... because the filter "unresolved" was added without me noticing it. Looking forward to the new release then!

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