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

Deleted Pages, Blogpost and Attachments Returning in Confluence Search Results

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 6.7.0
    • 5.8.15, 6.0.0-OD-2016.07.1-0002, 5.9.12, 5.10.7, 6.0.0-beta7, 1000.444.0, 6.2.3
    • Search - Indexing

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

      Summary

      Attachments which have been deleted from a Confluence Page are still searchable after a Content Index is performed

      Environment

      • Confluence Cloud version 6.0.0-OD-2016.07.2
      • Confluence server version 5.9.x and above

      Steps to Reproduce

      1. Add an attachment to a Confluence Page (does not need to be embedded on the page itself)
      2. Search for the Attachment using the Filename of the Attachment; it should display in the Search Results
      3. Delete the Attachment
      4. Search again for the Attachment; should not display in the Search Results
      5. Perform a task which triggers a Content Index (Move Pages, Create Space, etc) or as SysAdmin, manually trigger a Content Re-Index

      Expected Results

      Deleted attachment does not return in search results

      Actual Results

      • Deleted Attachment is shown in search results however when clicked displays a file not found error:
      • In some versions, deleted Attachments are able to be viewed like normal attachment
      • The attachment also reappeared in the Space Attachment list by going to Space Tools > Content Tools > Attachments

      Database shows that the Attachment has been deleted:

      confluence=> select contentid, contenttype, title, content_status from content where title like '%ExampleAttachment%';
       contentid | contenttype |          title          | content_status
      -----------+-------------+-------------------------+----------------
         5046279 | ATTACHMENT  | 1.ExampleAttachment.png | deleted
         5046280 | ATTACHMENT  | 2.ExampleAttachment.png | deleted
      (2 rows)

      Notes

      1. Rebuilding Cache does not seem to correct the issue
      2. Reindexing from scratch does not seem to correct the issue either

      Workaround

      1. Delete the attachment from the trash by going to Space Tool > Content Tools > Trash > choose the deleted attachments > Delete
      2. Purge the trash by going to Space Tool > Content Tools > Trash > purge

            [CONFSERVER-40833] Deleted Pages, Blogpost and Attachments Returning in Confluence Search Results

            What about Confluence Cloud customers, this is still an issue.

             

            Also, is there a way to delete the trash once or does it have to be done space by space?

            Nickey Wood added a comment - What about Confluence Cloud customers, this is still an issue.   Also, is there a way to delete the trash once or does it have to be done space by space?

            I would like to get on the deleted profile pictures? Are they still searchable? Is this fixed with the described solution in version 6.7?

            Katharina Alt added a comment - I would like to get on the deleted profile pictures? Are they still searchable? Is this fixed with the described solution in version 6.7?

            Hi cedric.weber@eberspaecher.com,

            Thank you for asking the question, as this lets us know which issues concern our customers which are using am Enterprise Release, and helps us assess whether these (non-Critical severity) issues could be a candidate for backporting.
            This issue is not targeted for backporting as it does not fall under the criteria for targeting the Enterprise Release (ref:  Introducing Enterprise releases for Confluence - Atlassian Community). Assessing this issue outside of the criteria detailed in the blog, this issue does not represent a reasonable risk/effort/value to backport to 6.6.

            The 'enterprise-backlog' label is used to indicate the team which worked on the issue, where 'enterprise' should not be confused with 'Enterprise Releases' and 'backlog' not to be confused with backporting.

            Regards
            Adam - Confluence PM

            Adam Barnes (Inactive) added a comment - Hi cedric.weber@eberspaecher.com , Thank you for asking the question, as this lets us know which issues concern our customers which are using am Enterprise Release, and helps us assess whether these (non-Critical severity) issues could be a candidate for backporting. This issue is not targeted for backporting as it does not fall under the criteria for targeting the Enterprise Release (ref:   Introducing Enterprise releases for Confluence - Atlassian Community ). Assessing this issue outside of the criteria detailed in the blog, this issue does not represent a reasonable risk/effort/value to backport to 6.6. The 'enterprise-backlog' label is used to indicate the team which worked on the issue, where 'enterprise' should not be confused with 'Enterprise Releases' and 'backlog' not to be confused with backporting. Regards Adam - Confluence PM

            Thanks for resolving this issue. But what about... the "Enterprise Release 6.6.x"? Still around in 6.6.3. This issue is even tagged with "enterprise-backlog". Hopefully coming soon to 6.6.4?

            Cedric Weber added a comment - Thanks for resolving this issue. But what about... the "Enterprise Release 6.6.x"? Still around in 6.6.3. This issue is even tagged with " enterprise-backlog ". Hopefully coming soon to 6.6.4?

            Thanks for resolving this issue. But what about deleted profile pictures? Are they still searchable?

            //SEIBERT/MEDIA added a comment - Thanks for resolving this issue. But what about deleted profile pictures? Are they still searchable?

            Minh Tran added a comment -

            A fix for this issue is now available for Confluence Server customers.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Minh Tran added a comment - A fix for this issue is now available for Confluence Server customers. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Thanks for your interest in this ticket. It is high on our priority list and we anticipate that it will be addressed In the near future.

            Adam Barnes (Inactive) added a comment - Thanks for your interest in this ticket. It is high on our priority list and we anticipate that it will be addressed In the near future.

            Seems like this issue also occurs for profile pictures which becomes an issue for some of our customers.

            As there's no workaround available for profile pictures a fix would be much appreciated.

            //SEIBERT/MEDIA/SYSTEMS added a comment - Seems like this issue also occurs for profile pictures which becomes an issue for some of our customers. As there's no workaround available for profile pictures a fix would be much appreciated.

            Jan added a comment -

            In my point of view this is a critical bug. Attachments which have been added to public pages by mistake and deleted afterwards are visible to public though the search. Just happened today and it took some time until we found the reason. +1

            Jan added a comment - In my point of view this is a critical bug. Attachments which have been added to public pages by mistake and deleted afterwards are visible to public though the search. Just happened today and it took some time until we found the reason. +1

            Any sign of a resolution here?

            CV Services Group added a comment - Any sign of a resolution here?

              huyle Huy Le (Inactive)
              scranford Shawn C
              Affected customers:
              95 This affects my team
              Watchers:
              80 Start watching this issue

                Created:
                Updated:
                Resolved: