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

Inherited restrictions not correctly reported if a page is moved

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • None
    • 2.8.2
    • None

      If a page which has inherited restrictions is moved away from it's parent, it retains the inherited restrictions but no longer reports that it has these restrictions.

      • Create a page
      • Setup Viewing Restrictions on this page (e.g. restrict to viewing for a single user)
      • Create a new page under the original page. This will inherit the restrictions which can be confirmed by choosing to edit the page and examine it's restrictions.

        Inherited view restrictions apply to this page.

        Inherited view restrictions are set on pages higher up in the hierarchy. A user must be included in at least one user or group on each page in order to view this page.

      • Choose to edit the page and move it's Location to another area with no restrictions
      • Once again choose to edit the page and examine it's restrictions. None will be reported.
      • Confirm that the inherited restrictions still apply by trying to access the page with someone who is restricted from viewing the original page.

      The page will keep it's inherited restrictions although it is no longer in the original hierarchy. Depending upon your viewpoint this could be problem in itself (this is more a matter of opinion) but the core bug is that the page will not show it's inherited restrictions. Instead it will show that no restrictions are present, which is incorrect. To remove these 'hidden' restrictions you must change the same type of restriction (view or edit) and save the page (so to remove all restrictions two operations are needed).

              Unassigned Unassigned
              6252507fd2ac Ben Boffey
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: