Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-36632

Document Conversion Library Tries to Provide a Preview for Unsupported File Types which is confusing

    • 3
    • 11
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Summary

      Document Conversion Library tries to convert and preview unsupported file types. This results in unsupported files to display an error when we click on the attachment link in the Confluence page.

      Steps to reproduce

      1. Attach a *.zip file to a page
      2. Provide a link the attachment
      3. Clicking the link will result into an error
        We can't preview this file.
        You'll have to download the file to view it.
      4. Checking the Network requests, an error is found on the :path:/wiki/rest/documentConversion/0.1/conversion/convert/...
        415 Unsupported Media Type

      **Note: This includes other unsupported file types (i.e .har, .exe)

      Workaround

            [CONFSERVER-36632] Document Conversion Library Tries to Provide a Preview for Unsupported File Types which is confusing

            This affects our company as well with Confluence (LTS) Version 7.4.8 which is the most actual on to this date. Our users reported this also with xlsx and pptx files. 

            marko.jovanovic added a comment - This affects our company as well with Confluence (LTS) Version 7.4.8 which is the most actual on to this date. Our users reported this also with xlsx and pptx files. 

            This is a serious issue and makes document management inconvenient as it this is a major feature of Confluence.
            As there is no one assigned and there has not been a comment from Atlassian should users assume this is not on the backlog?

            James Brown added a comment - This is a serious issue and makes document management inconvenient as it this is a major feature of Confluence. As there is no one assigned and there has not been a comment from Atlassian should users assume this is not on the backlog?

            brandon.g.scott added a comment - - edited

            I get around this by creating a button that simply does a direct download (no preview). Using the UI Button macro provided for free to Confluence server as part of the Refined Toolkit for Confluence.

            1. Attach your document to the page via the attachment window. .i.e. don't include it as a visible part of the page.
            2. Right click and copy the link to the attachment
            3. Edit page and add a UI Button macro with the URL from the attachment

            Clicking the button on the page will direct download whatever file you linked.

            Still a workaround to a bug, but it gets the job done. 

            brandon.g.scott added a comment - - edited I get around this by creating a button that simply does a direct download (no preview). Using the UI Button macro provided for free to Confluence server as part of the Refined Toolkit for Confluence. Attach your document to the page via the attachment window. .i.e. don't include it as a visible part of the page. Right click and copy the link to the attachment Edit page and add a UI Button macro with the URL from the attachment Clicking the button on the page will direct download whatever file you linked. Still a workaround to a bug, but it gets the job done. 

            My users are still facing this issue in Confluence 7.4.5 (e.g. with JSON Attachments).

            Francisco Villar Romasanta added a comment - - edited My users are still facing this issue in Confluence 7.4.5 (e.g. with JSON Attachments).

            The workaround has been deleted form Bitbucket. We are having the probleme only with XLSX files. Any hints?

            Banco de España added a comment - The workaround has been deleted form Bitbucket. We are having the probleme only with XLSX files. Any hints?

            this has been reported for more than a year ago. How long time does it take to verify this bug?

            Tom Birch Hansen added a comment - this has been reported for more than a year ago. How long time does it take to verify this bug?

            this is a bug, not an improvement. With Atlasssian significantly increasing the support cost of the product, we should receive better support. It appears the consensus from the comments is in agreement. Please change from improvement to bug and provide a date for resolution. This is holding up our upgrade.

            eric fairhurst added a comment - this is a bug, not an improvement. With Atlasssian significantly increasing the support cost of the product, we should receive better support. It appears the consensus from the comments is in agreement. Please change from improvement to bug and provide a date for resolution. This is holding up our upgrade.

            As mentioned in Answers:
            It's nice to have new "features" but when @atlassian implements such features a Admin (like me) should be able to at least disable them without tempering the source code :/

            Christian Sprenger added a comment - As mentioned in Answers : It's nice to have new "features" but when @atlassian implements such features a Admin (like me) should be able to at least disable them without tempering the source code :/

            Atlassian, I am also facing the same problem after upgrading my instance from 5.6.6 to 5.7.1 where I am unable to preview the PDF files from the space.

            Please provide a workaround for the same.

            om parkash added a comment - Atlassian, I am also facing the same problem after upgrading my instance from 5.6.6 to 5.7.1 where I am unable to preview the PDF files from the space. Please provide a workaround for the same.

            Atlassian, this is a bug, not an improvement. If I provide a fancy feature that only works in certain cases and fails in an unfriendly way in other cases, it is a regression from the previous behavior in which the feature didn't exist at all. Therefore it is a bug. To get back to old status quo for the cases where the feature doesn't work, you need a bug fix, not an improvment.

            Intel CHD Jira Admin added a comment - Atlassian, this is a bug, not an improvement. If I provide a fancy feature that only works in certain cases and fails in an unfriendly way in other cases, it is a regression from the previous behavior in which the feature didn't exist at all. Therefore it is a bug. To get back to old status quo for the cases where the feature doesn't work, you need a bug fix, not an improvment .

              Unassigned Unassigned
              namir Nursihah Amir (Inactive)
              Votes:
              58 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated: