Uploaded image for project: 'Community Forums Development'
  1. Community Forums Development
  2. FORUMS-1118

While enabled, Community Forums breaks the Confluence ancestor table when child pages are edited

    Details

    • Type: Bug
    • Status: Done (View Workflow)
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: 2.27.4
    • Fix Version/s: 2.27.6
    • Labels:
      None
    • Sprint:
      Q2-6, Q2-7
    • Story Points:
      5
    • Critical Points:
      0

      Description

      Steps to Reproduce

      • Navigate to Logging & Profiling and enable the following class at an INFO Level: com.atlassian.confluence.pages.ancestors
      • Tail the atlassian-confluence.log file
      • Create a Confluence page
        • Apply View and Editing restrictions to this page
      • Create a child of this page and publish it
      • Load the child page in edit mode
        • Make a change to the page and publish the page (Sometimes this step needs to be repeated)
      • Run the Repair Ancestor Table job.
      • Observe the atlassian-confluence.log file
      Expected Outcome

      The job will run and display the following message:

      repairAncestors Ancestors have been repaired. Found and fixed 0 broken pages. It took 0 sec for 2 spaces, average space processing time 0 sec.
      
      Actual Outcome

      The job will run and the following error message will be displayed:

      repairAncestors Ancestors have been repaired. Found and fixed 1 broken pages. It took x sec for x spaces, average space processing time x sec.
      

      Intermittent?

      False

      Affected Versions

      Plugin Confluence
      2.27.4 7.8

        Attachments

          Activity

            People

            Assignee:
            afaisal Ahmad Faisal
            Reporter:
            lwonnacott Lee Wonnacott
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: