Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.6.5
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Basel 147
-
2
Description
When you click the Export button in a content app or from the JCR tools app, the XML opens directly in the browser, replacing the admincentral - instead of downloading the file.
We were previously using Vaadin's default behavior to create a content-deposition header with proper encoding, but it does not add the "attachment" key word so the browser tries to open it instead of downloading it. We must actually manually set this header instead of using Vaadin's code in order to add the "attachment" keyword to the header and force the browser to download the file.
Â
Checklists
Attachments
Issue Links
- caused by
-
MGNLUI-4326 Remove setting content-deposition manually to properly encode special characters in filename
-
- Closed
-
- is duplicated by
-
MAGNOLIA-7312 Export as xml opens the file in the browser instead of downloading
-
- Closed
-
-
MAGNOLIA-7336 Content-Disposition missing "attachment" when exporting JCR content
-
- Closed
-
-
MAGNOLIA-7314 XML Exporting not working
-
- Closed
-
- is related to
-
MAGNOLIA-6536 Can't export JCR nodes on iPad
-
- Open
-
-
MGNLCE-267 Create UI test for export action
-
- Open
-