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

Provide workaround for fixing broken unknown attachment placeholder in storage format

    • 280
    • 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.

      Atlassian Update - 10 June 2021

      We've released an app for Confluence that will begin to resolve a number of the missing attachment issues being seen by customers. The app attempts to automatically repair attachments, and provides some "quality of life" improvements when attachments cannot be automatically repaired.

      There are currently a number of limitations with the app and it is important that you are aware of these limitations. We have documented the functionality of the app at Unknown attachment error in Confluence Server and Data Center 7.12 and earlier and strongly encourage reading this page in full prior to installing the app.

      Our focus here was on getting a partial fix out to repair as many pages as possible and avoid pages entering an irreparable state when edited. We are capturing additional analytics to understand the impact of this issue and assess the best path forward to providing a broader fix.

      The app can be downloaded from reconcile-unknown-attachments-1.0.6.jar

      We are working to have a Data Center approved version of the app available in coming days, but this app should work for Data Center customers in the interim.

      Currently, unknown attachments issue stands has high User Impact and it has resulted in pages broken on customer sites. This has caused a lot of support and customer pain leading to admins manually fixing pages.

      As an admin, I would like to restore pages/shared-drafts which has unknown-placeholder in creeped into editor format.

      This ticket tracks the fix to address already broken data caused by https://jira.atlassian.com/browse/CONFSERVER-55928.
      This includes only attachments that are broken in storage format due to being replaced with an unknown-attachment placeholder:

      • Broken format in storage for broken pages by "Unknown Placeholder" (Covered by this ticket):
        <p>
         <ac:image>
          <ri:url ri:value="http://localhost:5990/confluence/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&amp;version=2" />
         </ac:image>
        </p>
        
      • "<ri content-entity> broken links" issue storage format (Covered by https://jira.atlassian.com/browse/CONFSERVER-63700):
        <p>
          <ac:image>
            <ri:attachment ri:filename="image2020-10-21_12-40-38.png">
              <ri:content-entity ri:content-id="138910055"/>
            </ri:attachment>
          </ac:image>
        </p>
        

            [CONFSERVER-63615] Provide workaround for fixing broken unknown attachment placeholder in storage format

            Conny Postma made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 782548 ]
            Niraj Bhawnani made changes -
            Description Original: {panel:title=Atlassian Update - 10 June 2021|borderStyle=solid|borderColor=#6554c0|titleBGColor=#6554c0|bgColor=#eae6ff|titleColor=#ffffff}
            We've released an app for Confluence that will begin to resolve a number of the missing attachment issues being seen by customers. The app attempts to automatically repair attachments, and provides some "quality of life" improvements when attachments cannot be automatically repaired.

            There are currently a number of limitations with the app and it is important that you are aware of these limitations. We have documented the functionality of the app at [Unknown attachment error in Confluence Server and Data Center 7.12 and earlier|https://confluence.atlassian.com/confkb/unknown-attachment-error-in-confluence-server-and-data-center-7-12-and-earlier-1063179837.html] and strongly encourage reading this page in full prior to installing the app.

            Our focus here was on getting a partial fix out to repair as many pages as possible and avoid pages entering an irreparable state when edited. We are capturing additional analytics to understand the impact of this issue and assess the best path forward to providing a broader fix.

            The app can be downloaded from [Reconcile Unknown Attachments \- Atlassian Marketplace|https://marketplace.atlassian.com/apps/1225406/reconcile-unknown-attachments?hosting=server&tab=overview]

            We are working to have a Data Center approved version of the app available in coming days, but this app should work for Data Center customers in the interim.
            {panel}
            Currently, unknown attachments issue stands has high User Impact and it has resulted in pages broken on customer sites. This has caused a lot of support and customer pain leading to admins manually fixing pages.

            As an admin, I would like to restore pages/shared-drafts which has unknown-placeholder in creeped into editor format.

            This ticket tracks the fix to address already broken data caused by https://jira.atlassian.com/browse/CONFSERVER-55928.
            This includes only attachments that are broken in storage format due to being replaced with an unknown-attachment placeholder:

            * Broken format in storage for broken pages by "Unknown Placeholder" (Covered by this ticket):
            {code:java}
            <p>
             <ac:image>
              <ri:url ri:value="http://localhost:5990/confluence/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&amp;version=2" />
             </ac:image>
            </p>
            {code}
            * "<ri content-entity> broken links" issue storage format (Covered by https://jira.atlassian.com/browse/CONFSERVER-63700):
            {code:java}
            <p>
              <ac:image>
                <ri:attachment ri:filename="image2020-10-21_12-40-38.png">
                  <ri:content-entity ri:content-id="138910055"/>
                </ri:attachment>
              </ac:image>
            </p>
            {code}
            New: {panel:title=Atlassian Update - 10 June 2021|borderStyle=solid|borderColor=#6554c0|titleBGColor=#6554c0|bgColor=#eae6ff}
            We've released an app for Confluence that will begin to resolve a number of the missing attachment issues being seen by customers. The app attempts to automatically repair attachments, and provides some "quality of life" improvements when attachments cannot be automatically repaired.

            There are currently a number of limitations with the app and it is important that you are aware of these limitations. We have documented the functionality of the app at [Unknown attachment error in Confluence Server and Data Center 7.12 and earlier|https://confluence.atlassian.com/confkb/unknown-attachment-error-in-confluence-server-and-data-center-7-12-and-earlier-1063179837.html] and strongly encourage reading this page in full prior to installing the app.

            Our focus here was on getting a partial fix out to repair as many pages as possible and avoid pages entering an irreparable state when edited. We are capturing additional analytics to understand the impact of this issue and assess the best path forward to providing a broader fix.

            The app can be downloaded from [^reconcile-unknown-attachments-1.0.6.jar]

            We are working to have a Data Center approved version of the app available in coming days, but this app should work for Data Center customers in the interim.
            {panel}
            Currently, unknown attachments issue stands has high User Impact and it has resulted in pages broken on customer sites. This has caused a lot of support and customer pain leading to admins manually fixing pages.

            As an admin, I would like to restore pages/shared-drafts which has unknown-placeholder in creeped into editor format.

            This ticket tracks the fix to address already broken data caused by [https://jira.atlassian.com/browse/CONFSERVER-55928].
            This includes only attachments that are broken in storage format due to being replaced with an unknown-attachment placeholder:
             * Broken format in storage for broken pages by "Unknown Placeholder" (Covered by this ticket):
            {code:java}
            <p>
             <ac:image>
              <ri:url ri:value="http://localhost:5990/confluence/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&amp;version=2" />
             </ac:image>
            </p>
            {code}

             * "<ri content-entity> broken links" issue storage format (Covered by [https://jira.atlassian.com/browse/CONFSERVER-63700):]
            {code:java}
            <p>
              <ac:image>
                <ri:attachment ri:filename="image2020-10-21_12-40-38.png">
                  <ri:content-entity ri:content-id="138910055"/>
                </ri:attachment>
              </ac:image>
            </p>
            {code}
            Niraj Bhawnani made changes -
            Attachment New: reconcile-unknown-attachments-1.0.6.jar [ 458643 ]
            Cathy S made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 892547 ]
            Iker Alonso made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 782548 ]

            Tobias added a comment -

            jponting, just a quick question about the solution. 
            I have checked some pages with the label "unrestored-unknown-attachment" and have numerous pages that are displayed correctly, so without error message "unknown attachment". What I don't understand is the step in the solution description where I am supposed to reselect the attachment if there is an error. pages that have this error have no attachments at all, so this solution is only partially correct. 
            also the question on my part. When can we uninstall the app, but which version is no longer expected to have the error?

             

            Tobias added a comment - jponting , just a quick question about the solution.  I have checked some pages with the label "unrestored-unknown-attachment" and have numerous pages that are displayed correctly, so without error message "unknown attachment". What I don't understand is the step in the solution description where I am supposed to reselect the attachment if there is an error. pages that have this error have no attachments at all, so this solution is only partially correct.  also the question on my part. When can we uninstall the app, but which version is no longer expected to have the error?  
            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 4092116 ] New: JAC Suggestion Workflow 3 [ 4339513 ]
            Wendy H made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 718558 ]
            Wendy H made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 718558 ]
            Oliver Shen made changes -
            Remote Link New: This issue links to "R7.13 P1. Baseline › Main Plugins - Frontend › issue-713-CONFSERVER-63615-bundle-unknown-attachments-plugin (server-syd-bamboo)" [ 631363 ]

              oshen@atlassian.com Oliver Shen
              ggautam Ganesh Gautam
              Votes:
              117 Vote for this issue
              Watchers:
              140 Start watching this issue

                Created:
                Updated:
                Resolved: