Summary

      Running Confluence 4.3.2 in Internet Explorer 8, there is no option to Open attachment.

      Steps to reproduce

      1. Use Confluence 4.3.2.
      2. Attach a document in any page. For example: test.docx
      3. Once attached, refresh the page.
      4. Click the attachment link and it will prompt a window to Save/Cancel. No options for Open.
      5. Use Confluence 4.3.1, repeat the steps above. There will be option to Open/Save/Cancel in the prompt window.

      Testing

      This scenario also happens in Internet Explorer 9 for version 4.3.2 but not 4.3.1.
      Testing on Firefox shows that the 'Open' function works fine for both 4.3.2 and 4.3.1.
      Please refer attachment for more information.

      Workaround

      • Use Firefox to run Confluence 4.3.2.
      • Save attachment before opening it.
      • Another workaround is described in this article, however this can be implemented at your own risk!

        1. confluence-4.3.1_with_IE8.png
          confluence-4.3.1_with_IE8.png
          112 kB
        2. confluence-4.3.1_with_IE9.png
          confluence-4.3.1_with_IE9.png
          85 kB
        3. confluence-4.3.2_with_IE8.png
          confluence-4.3.2_with_IE8.png
          114 kB
        4. confluence-4.3.2_with_IE9.png
          confluence-4.3.2_with_IE9.png
          79 kB

            [CONFSERVER-26994] No option to 'Open' attachment

            We also have many complaints of users due to the lack of this feature. We run confluence 4.3.3. is there a way to get the festure back that is fixed in confluence 4.3.5 without upgrading? E.g. Plugin upgrade? Thanks

            Michael Michael added a comment - We also have many complaints of users due to the lack of this feature. We run confluence 4.3.3. is there a way to get the festure back that is fixed in confluence 4.3.5 without upgrading? E.g. Plugin upgrade? Thanks

            David, any guesses as to when the next release of confluence (that should include this fix) is expected?

            Thanks

            Joe Shomphe added a comment - David, any guesses as to when the next release of confluence (that should include this fix) is expected? Thanks

            David Black added a comment - - edited

            This issue should be fixed in the next confluence release.

            David Black added a comment - - edited This issue should be fixed in the next confluence release.

            Guys, since the 27th of November the issue went to Technical Review. Someone is obviously working on this. It is now at a status of Quality Review which my interpretation is it will make it for one of the upcoming releases.

            I did get word on the 14th of November through a support member that we will see this issue resolved.

            Brett Ryan added a comment - Guys, since the 27th of November the issue went to Technical Review . Someone is obviously working on this. It is now at a status of Quality Review which my interpretation is it will make it for one of the upcoming releases. I did get word on the 14th of November through a support member that we will see this issue resolved.

            Tim added a comment -

            Did you know,

            • that there is browser called Internet Explorer?
            • that your customers are using Internet Explorer?
            • that you officially support Internet Explorer?

            so why are you not testing your stuff in Internet Explorer?

            Tim added a comment - Did you know, that there is browser called Internet Explorer? that your customers are using Internet Explorer? that you officially support Internet Explorer? so why are you not testing your stuff in Internet Explorer?

            I'm sorry to say, but this is such a change you don't want forced onto you. It should at least be easily configurable.

            The Header workaround works for us, but we would still like to see a better solution.

            Johan Larsson added a comment - I'm sorry to say, but this is such a change you don't want forced onto you. It should at least be easily configurable. The Header workaround works for us, but we would still like to see a better solution.

            troy added a comment -

            This has been a problem for us as well.
            It is not possible to ask each and every user to switch to another browser.I feel that Atlassian needs to give this issue much more priority than by just making a comment to "Fix it at your own risk".

            troy added a comment - This has been a problem for us as well. It is not possible to ask each and every user to switch to another browser.I feel that Atlassian needs to give this issue much more priority than by just making a comment to "Fix it at your own risk".

            BTW the open option is also there in chrome browser

            Linda Petty added a comment - BTW the open option is also there in chrome browser

            This is a big problem for us too. PDF links open OK so our users are going to have to change all the microsoft office attachments to PDFs. Installing an alternative browser across hundreds of PCs would be a bigger job for IT (our users cannot install browsers themselves). This ticket should definitely be escalated to MEDIUM and we need a timetable.

            Linda Petty added a comment - This is a big problem for us too. PDF links open OK so our users are going to have to change all the microsoft office attachments to PDFs. Installing an alternative browser across hundreds of PCs would be a bigger job for IT (our users cannot install browsers themselves). This ticket should definitely be escalated to MEDIUM and we need a timetable.

            I would like to echo the above comments. For our users this is both confusing and annoying.

            I would have expected that this type of regression would be resolved as a priority. I'm not certain how such an bug could be introduced, and then have no specific time-table for resolution.

            Jason Elwin added a comment - I would like to echo the above comments. For our users this is both confusing and annoying. I would have expected that this type of regression would be resolved as a priority. I'm not certain how such an bug could be introduced, and then have no specific time-table for resolution.

              dblack David Black
              cchan Chung Park Chan
              Affected customers:
              20 This affects my team
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: